Connection check
About 45 seconds. Keep this tab in the foreground and pause large downloads while it runs.
Connection check
About 45 seconds. Keep this tab in the foreground and pause large downloads while it runs.
This verdict describes your connection to our edge. It is not your in-game ping.
- Typical latency
- — ms
- 95th percentile
- — ms
- Worst sample
- — ms
- Jitter (mean)
- — ms
- Jitter (95th percentile)
- — ms
- Timeout samples
- — %
- Increase under load
- — ms
- Download during test
- — Mbps
- Connected to edge
- —
- Samples
- —
What to do next
Everything is calculated in your browser. Nothing about your connection is stored on our side.
How to read your result
| Result | What it means | What to do |
|---|---|---|
| Your connection is unstable — fix this side first | Latency swings, frames go missing, or latency jumps when the connection is busy. | Fix your side first: cable, 5 GHz, stop background uploads, enable SQM/QoS. Do not buy anything yet. |
| Your connection is stable, but slow | Consistent, no timeouts — so the local link is not the problem. | Most likely distance or the route your ISP takes. Check the game server region before buying a route optimiser. |
| Your connection looks healthy | Low, steady latency that survives load. | You do not need a latency tool. If one game still feels bad, the cause is elsewhere. |
Frequently asked
Is this the same as my in-game ping?
No. The test measures the round trip between your browser and our edge. Your in-game ping also includes the path from our edge to the game server, which no web page can see. Treat the result as a health check on your own connection.
Why is there a WebSocket phase?
It acts like a game server tick loop: 20 small frames per second for 30 seconds. That exposes stability problems that occasional HTTP requests miss.
Do you store my results?
No. The probe endpoints echo and return nothing; all statistics are computed in your browser. Privacy