A Ping Test Result Is Four Numbers, Not One

Most people run a ping test, glance at a single figure, and close the tab. But a good test sends many packets and reports the minimum, maximum, and average round-trip time plus jitter — and the relationship between those numbers tells you far more than any one of them alone. Two connections can share a 35ms average while one is rock solid and the other is falling apart. Here's how to read the whole report.

Minimum: The Best Your Route Can Do

The minimum is the fastest round trip recorded during the test — the closest thing to the physical floor of your route. It's dominated by distance and infrastructure: light in fiber covers roughly 200 km per millisecond one-way — and a round trip covers that distance twice — so a server 1,500 km away can never answer in 5ms. If your minimum is already high, no router tweak will fix it; the only levers are choosing a closer server or a better route. Treat the minimum as your connection's potential.

The average is what people quote, and it's a fair summary when the connection is stable. Its blind spot is that it hides variation: a test that returns 20, 21, 20, 95, 22ms averages around 36ms, which looks fine — yet that single 95ms outlier is exactly the kind of hiccup that drops a frame or clips a word. Never judge a connection by the average alone; always check it against the minimum and maximum.

Maximum and the Min-Max Spread

The maximum is the worst round trip in the sample, and the gap between minimum and maximum is the most underrated diagnostic in the report:

Spread under ~10ms: excellent. Your route is consistent and whatever the average says is trustworthy.
Spread of 10-30ms: normal for Wi-Fi or busy hours. Usually harmless, worth watching.
Spread over ~50ms: something is queueing or interfering — commonly Wi-Fi retransmissions, a saturated line, or congestion. The average is now hiding real problems.

A 25ms average with a 24-90ms range is a worse connection than a 45ms average with a 43-49ms range, even though the first "wins" on the headline number. Real-time apps live at the bad end of the range: every packet that arrives late is a moment the game or call has to paper over, no matter how flattering the average looks.

Jitter: The Spread, Summarized

Jitter condenses that variation into one figure: how much the round-trip time changes between consecutive measurements. Under 5ms is excellent, under 10ms is good, and anything over 20ms will be felt in real-time apps regardless of your average ping. Jitter is the stability score of your connection — our jitter vs ping guide goes deeper on why variance often hurts more than stable delay.

Why Each Region Shows Different Numbers

A browser test like CheckPing measures HTTPS round-trip times to cloud endpoints in multiple regions — a real-world proxy for latency, not the ICMP ping command or an in-game counter. That's why the per-region breakdown matters: your nearest region reflects your connection's health, while distant regions mostly reflect geography. A high number to a continent away is physics, not a fault. Compare regions against each other and against your own past results, not against someone else's screenshot.

When to Retest Before Drawing Conclusions

One test is a snapshot. Before acting on a result, retest when:

The max or jitter looks bad once: a single background process (a cloud sync burst, an update check) can poison one run. Two or three runs separate a fluke from a pattern.
You changed something: switched to Ethernet, moved the router, enabled QoS — always compare a fresh test to your baseline.
The time of day changed: evening results routinely differ from afternoon ones on shared networks.

Once you can read the numbers, the next question is what counts as good for your use case — for gaming thresholds by genre, see our guide to what makes a good ping for gaming.

How to Read Ping Test Results: Min, Max, Average and Jitter Explained