Vilnius Server

About the Vilnius location

Vilnius covers the northeastern corner of the network. While on standby it stays provisioned for the Baltics, Scandinavia and Eastern Europe, giving players there a shorter path than backhauling to Amsterdam.

Activated, Vilnius brings Baltic, Scandinavian and Eastern European traffic onto a local point of presence — Lithuania, Latvia, Estonia, Finland, Sweden and the eastern EU get shorter round trips than the haul back to Amsterdam. It mirrors the base deployment, so shifting traffic changes routing, not behavior.

Location choice is about distance, not features: every node serves the identical API version and schema, so a game client can switch endpoints without code changes. Point your SDK at the nearest location for the lowest round-trip time, or keep the default hostname and let the network route — standby locations activate on demand during regional traffic spikes or primary-site maintenance.

All endpoints expose the same REST API surface — game players, rooms, matchmaking, leaderboards, game data and moderation — so SDK and game clients work unchanged whichever location terminates the request. See the API reference for the endpoint list.