United States / LAX
Los Angeles
Users on the US west coast and around the Pacific.
GLWS · Datacentres
Browse our locations and the questions worth asking about connectivity, power, physical security and recovery. A city is a starting point, so measure real performance before you commit.
35 locations across 6 continents.
Search by city or country, or filter by region.
No matching items. Try another search or category.
United States / LAX
Users on the US west coast and around the Pacific.
United States / SJC
Development teams and apps serving the US west coast.
United States / SEA
Pacific Northwest users, or a replica away from Los Angeles and San Jose.
United States / SLC
Inland western US users and compute-heavy workloads.
United States / CHI
Apps that need to reach users across the whole US.
United States / DFW
South-central US users and apps spread across several servers.
United States / NYC
North-eastern US users and traffic across the Atlantic.
United States / EWR
A second north-eastern US option for regional deployments.
United States / ATL
South-eastern US users and regional application traffic.
United States / TPA
Florida users and a second south-eastern US option.
United States / MIA
South Florida users and apps with regional dependencies.
United States / IAD
East-coast apps and services near Northern Virginia.
Canada / YUL
Canadian users and projects with Canadian location requirements.
Canada / YYZ
Ontario users and a second Canadian option.
United Kingdom / LON
UK users and apps built around a British audience.
Netherlands / AMS
Apps serving Europe from the Netherlands.
Ireland / DUB
Irish users, or a second European location.
France / SXB
French users and apps focused on continental Europe.
Germany / FRA
German users and continental European traffic.
Singapore / SIN
South-east Asian users and an Asia Pacific presence.
United Arab Emirates / DXB
Middle East users and traffic heading to Africa and South Asia.
Italy / MIL
Italian users and southern European traffic.
France / PAR
French users and western European traffic.
Brazil / GRU
Brazilian users and Latin American traffic.
Japan / TYO
Japanese users and East Asian traffic.
Japan / OSA
Western Japan users and a second Japanese location.
Switzerland / ZRH
Swiss users and projects that need a Swiss location.
New Zealand / AKL
New Zealand users and a presence in Oceania.
Australia / SYD
Australian users and Oceania traffic.
Hong Kong / HKG
Hong Kong and southern China users, and traffic across Southeast Asia.
Spain / MAD
Spanish users and Iberian traffic.
India / BOM
Indian users and South Asian traffic.
South Korea / ICN
South Korean users.
South Africa / JNB
South African users and southern African traffic.
Sweden / ARN
Swedish users and Nordic traffic.
Three things to weigh up.
Pick the region closest to most of your users, then test real response times from their networks.
A database, API or storage service elsewhere can slow down a nearby server. Look at the whole request path.
Keep backups somewhere other than your live data, and practise restoring them.
Quick answers about our locations.
No. The map marks cities where you can choose to host. It does not show facility ownership, installed equipment or available capacity.
Start with your audience and your application's dependencies. Then compare real measurements, data requirements and recovery arrangements.
Yes. Your choice is saved with your configuration. Some regional products limit which cities you can choose.
No. Real routing, your audience's networks and your application decide response time.