GAMING
Most of the milliseconds you lose in a match are spent on the packet’s journey. Picking a nearer exit shortens that journey — and our measurements are on the front page.
WireGuard adds about forty bytes to a packet and finishes its handshake in a single round trip. You don’t pay the extra rounds older protocols charge on every connection, and the difference shows most on small frequent packets — which is exactly what a game produces.
Joining a match on a Frankfurt server, you don’t get to choose how many hops your packet takes. Move the exit into that region and the route is often more direct than your home connection’s default — and when it isn’t, the app’s measurement tells you so.
What drops in the evening is usually not speed but steadiness: the average ping holds while the spikes multiply. We size capacity against those spikes, because what ruins a match isn’t 60 ms — it’s a sudden 300.
Consoles have no app; install it on your router and every device on the network gets the same exit.
It does add a hop. But your provider’s default route isn’t always the shortest one: moving the exit closer to the game server can shorten the total path. When it doesn’t, the app’s measurement shows you — and you’ll know not to connect.
PlayStation, Xbox and Switch can’t run the app. Install it on your router instead and every device on that network, console included, uses the same exit.
The one closest to the game server’s region. The app lists measured latency; the lowest number is usually the right answer.
Don’t take our number for it — connect and watch the in-game counter.
