Relay locations and regions
Explore the available Relay regions, and learn how to select the best one for your players.
Read time 1 minuteLast updated 2 months ago
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 session.
The following table has the Relay regions available across the globe:
Americas, Europe
Identifier | Location |
|---|---|
| South Carolina |
| Iowa |
| Oregon |
| Sao Paulo |
| Finland |
| Poland |
| Netherlands |
Asia, Australia
Identifier | Location |
|---|---|
| Singapore |
| Tokyo |
| Mumbai |
| Sydney |
How region selection works
Typically, you don't need to specify a region in an allocation request:
- The Multiplayer Services SDK defaults to using Quality of Service (QoS) measurements to select a region.
- You can use with
WithRelayNetworkto configure a region by name.RelayNetworkOptions
- You can use
- If you omit the region from the HTTP request, the service uses the origin network address as a heuristic to pick a region.
POST /v1/allocate - If none of the previous are possible, the service defaults to .
us-central1
Passing an explicit region identifier overrides this behavior. It's recommended you programmatically check this value against the region listing response and not hardcode any values.
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; refer to the previous tables for mappings.