Regions and locations
By default, we have ten regions you can use. Speak with your account manager to check whether you have access to them all.
Here are the codes that we use to refer to each region:
Region | Locations |
eu-west | e.g. London, Paris, Amsterdam & Frankfurt |
eu-east | e.g. Warsaw |
na-east | e.g. Washington DC, Ashburn, Manassas, Miami & New York |
na-central | e.g. Dallas & Chicago |
na-west | e.g. San Jose, Los Angeles, Seattle & Santa Clara |
sa-east | e.g. Sao Paulo |
asia-east | e.g. Singapore & Hong Kong |
asia-northeast | e.g. Tokyo & Seoul |
oce-east | e.g. Sydney |
india | Mumbai |
Locations can vary within a region as we constantly look for the best sites and providers. If you'd like to know what specific locations are available, check with our support team.
If there's a location you want that's not on this list, let us know and we will do what we can to accommodate your needs. The regional breakdown can also depend on the matchmaker you choose to use, please inform the support team of any nuances that may not match what we have above as there might be things that can be done to aid your custom scenarios
A region is just a collection of different geographical locations. But each location might have different (or multiple) providers. By default, we automatically pick the best location inside a region to create your session based on availability.
For example, if you pick eu-west we launch sessions in Amsterdam, London, Paris or Frankfurt instead depending on what is available. But we wouldn't scale across regions. So, in this example, we wouldn't launch in Hong Kong. This makes sure that the session is going to be a good experience for the player while letting us scale to meet your demand.
And, if there's a problem, we can switch off individual locations or providers. This stops us from trying to spin up more sessions in a location that might be having problems, like a denial of service (DDoS) attack. Instead, we can deploy sessions on healthy providers or locations.
