Game server ping, jitter and packet loss test
| Region | Ping | Jitter | Loss | For games |
|---|---|---|---|---|
| US East (Virginia) | – | – | – | – |
| US East (Ohio) | – | – | – | – |
| US West (California) | – | – | – | – |
| US West (Oregon) | – | – | – | – |
| South America (São Paulo) | – | – | – | – |
| Europe (London) | – | – | – | – |
| Europe (Frankfurt) | – | – | – | – |
| Europe (Stockholm) | – | – | – | – |
| India (Mumbai) | – | – | – | – |
| Asia (Singapore) | – | – | – | – |
| Australia (Sydney) | – | – | – | – |
| Japan (Tokyo) | – | – | – | – |
| Korea (Seoul) | – | – | – | – |
Times are web requests from your browser to cloud data centres. In-game ping uses UDP and is usually a little lower.
FAQ
What does the test measure?
It times small web requests from your browser to a cloud data centre in each region. Ping is the average reply time, jitter is how much it changes, and loss is the share of requests with no reply.
Is this the same as in-game ping?
It is close, not equal. A browser cannot send the UDP packets games use or reach a game server's own address, so expect in-game ping to be a little lower.
What is a good result?
Under 50 ms ping with jitter under 10 ms and no loss is great for any game. Over 150 ms, jitter over 40 ms or any steady loss causes rubber-banding.
Why is my jitter high?
Wi-Fi, a busy home network and downloads running in the background are the usual causes. Test again on a cable and with other devices idle.
Which servers does it contact?
A public health-check address in each Amazon Web Services region. No personal data is sent, only an empty request.
Is it free?
Yes. There is no sign-up, no watermark and no daily limit.