GLWS · Datacentres

Place your workload.
Know your geography.

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.

Find a location.

Search by city or country, or filter by region.

Choosing a location.

Three things to weigh up.

Your audience

Pick the region closest to most of your users, then test real response times from their networks.

Your dependencies

A database, API or storage service elsewhere can slow down a nearby server. Look at the whole request path.

Your recovery plan

Keep backups somewhere other than your live data, and practise restoring them.

Common questions.

Quick answers about our locations.

Does the map show facilities you own?

No. The map marks cities where you can choose to host. It does not show facility ownership, installed equipment or available capacity.

Which region should I choose?

Start with your audience and your application's dependencies. Then compare real measurements, data requirements and recovery arrangements.

Can I pick a city in the configurator?

Yes. Your choice is saved with your configuration. Some regional products limit which cities you can choose.

Does a location guarantee low latency?

No. Real routing, your audience's networks and your application decide response time.