Gameye

Choosing your server locations

Active Steering

When using regions for session creation instead of specific locations Gameye automatically steers the match to the best possible location, provider and compute instance type (bare metal, cloud, edge).

For example, during the daytime, much of the load can be spread across bare metal servers while in the evenings or during special event cloud capacity can be ramped up quickly to deal with a peak increase in concurrent sessions.

Automatic routing around network disruptions

In the case of a network disruption, the provider or datacenter at which the disruption is detected will be drained taken out of the equation in the selection process for placing new sessions. When a large amount of capacity is drained at once, extra servers are automatically brought online at other healthy providers.

Mitigate single provider capacity issues

When a location inside a region is out of capacity (bare metal or cloud) it will automatically be ignored in the selection process and sessions are created on the next best location.

Region list

You can use the following list of regions or locations when spawning new sessions.

Region

Locations

eu-west

amsterdam
frankfurt
london
dublin

eu-east

warsaw
moscow

eu-south

madrid*

na-east

washington_dc*

na-central

dallas
chicago

na-west

san_jose*

sa-east

sao_paulo(*)**

asia-east

singapore
hong_kong

oce-east

sydney(*)**

* Multiple different providers (bare metal and cloud) can be used within the same location.
** This location needs to be activated on a per-account basis.

Updated 3 months ago


Choosing your server locations


Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.