Ping test
Sends 40 small packets from your browser to our test node in Chicago (US) and times each round trip. You get round-trip time, jitter and packet health in about five seconds.
"Test under load" adds short download and upload bursts to show bufferbloat.
Latency trace
Teal is idle, amber is under load, red marks a packet with no reply.
Distribution
How often each round-trip time occurred.
The distribution appears after the first test.
Diagnostics from Chicago (US)
These tests run from our test node in Chicago (US), not from your browser. Use them to check whether a host is reachable and how far it is from a US Midwest network. Private and internal addresses can't be tested.
Reading your result
Ping (latency)
The time for a packet to reach the server and come back. Under 30 ms feels instant in games and calls. Over 100 ms you start to notice delay. Distance sets a floor: light in fiber adds about 1 ms of round trip for every 100 km.
Jitter
How much latency changes from one packet to the next, using the RFC 3550 method that voice and video apps use. Below 5 ms is steady. High jitter causes choppy calls even when the average ping looks fine.
Packet loss
Packets that got no reply within two seconds. Any loss on a wired connection points to a problem. On Wi-Fi, try again closer to the router before blaming your provider.
Bufferbloat
When your connection is busy, an oversized router buffer can hold packets back and push ping up by hundreds of milliseconds. The grade compares ping during short transfers with idle ping. Turning on SQM or "smart queue" in your router usually fixes a C or worse.