Relay locations and regions
As a developer using Relay, you can allow players to select a Relay server from a list of available regions. By selecting the closest Relay server, the player can minimize the potential latency and guarantee the smoothest possible experience for their game session.
The following table has the Relay regions available across the globe:
Americas, Europe
Identifier | Location |
---|---|
us-east1 | South Carolina |
us-central1 | Iowa |
us-west1 | Oregon |
southamerica-east1 | Sao Paulo |
europe-north1 | Finland |
europe-central2 | Poland |
europe-west4 | Netherlands |
Asia, Australia
Identifier | Location |
---|---|
asia-southeast1 | Singapore |
asia-northeast1 | Tokyo |
asia-south1 | Mumbai |
australia-southeast1 | Sydney |
How region selection works
Normally, you do not need to specify a region in an allocation request:
- the Multiplayer Services SDK defaults to using Quality of Service (QoS) measurements are used to select a region
- if you omit the region from the
POST /v1/allocate
HTTP request, the service uses the origin network address as a heuristic to pick a region - if none of the above is possible, the service defaults to
us-central1
Passing an explicit region identifier overrides this behavior. It is recommended you programmatically check this value against the region listing response and not hardcode any values.
You can retrieve a list of all available regions with the Allocations API GET /v1/regions endpoint.
Fallback for retired regions
Retired regions are not visible in the regions listing endpoint. Explicit requests to retired regions are automatically redirected to a replacement region; see tables above for mappings.