What Is a Good Ping? The Numbers That Actually Matter
Every gaming guide, speed test result, and ISP advertisement throws around ping numbers — but rarely explains what they mean in practice. Under 20ms is "excellent," under 100ms is "acceptable." But acceptable for what? Here's exactly what different ping ranges mean for the things you actually do online.
For competitive gaming, aim for under 30ms. For casual gaming and video calls, under 60ms is comfortable. Under 100ms is fine for everything except fast-paced competitive play. Above 150ms you'll start noticing delays in any interactive application. But remember: ping alone doesn't tell the full story — a stable 60ms connection beats a jittery 15ms one almost every time.
What Ping Actually Measures
Ping — more precisely, round-trip latency — is the time it takes for a data packet to travel from your device to a server and back. It's measured in milliseconds (ms). When you see "20ms ping," it means 20 milliseconds elapsed between your device sending a packet and receiving the response.
Ping is determined primarily by two things: physical distance to the server, and routing efficiency through the networks in between. Light travels through fiber optic cable at about two-thirds the speed of light — roughly 200,000 km per second. That puts a hard physical floor on latency: you simply cannot get faster than the time it takes for photons to make the round trip.
In practice, routing overhead, processing delays at each hop, and the difference between fiber and copper runs mean your actual ping is always somewhat higher than the theoretical minimum for the distance involved.
Ping tells you the average delay. Jitter tells you how consistent that delay is. For real-time applications, jitter is often more important than ping — a stable 50ms connection feels smoother than a 10ms connection that spikes to 80ms irregularly. Always check both when evaluating connection quality.
The Ping Scale: What Each Range Means
Essentially zero perceptible delay in any application. You're either very close to the server geographically, on a direct fiber run, or the server has a CDN edge node near you. Most users on Cloudflare's global network will see values in this range. Not meaningfully better than 20ms for any real use case.
The target range for competitive gaming. At this level, input lag is imperceptible and no lag compensation or interpolation artifacts are visible. Pro players often have 5–20ms to their regional game servers. If you're in this range and gaming still feels off, jitter is your problem — not ping.
Comfortable for all but the most competitive play. Casual and ranked gaming is smooth, video calls are natural, VoIP is clear. The vast majority of players in this range will never notice ping as a limiting factor. The difference between 30ms and 60ms is about 30ms of additional input lag — unnoticeable in all but the fastest reflex situations.
Fine for casual gaming, all streaming, video calls, and browsing. Competitive players may notice slight sluggishness in the most reaction-dependent games (FPS, fighting games). Game servers are typically built to handle up to 100ms with lag compensation that makes the experience feel reasonably smooth. VoIP is acceptable but slight conversation pauses may be noticeable.
Noticeable in interactive applications. Fast-paced games feel sluggish and unresponsive. Voice calls have a slight echo effect (you hear your own voice delayed back). Still perfectly usable for turn-based games, streaming, browsing, and email. Above 200ms, the delay becomes apparent even in casual conversation. Above 400ms, VoIP is practically unusable.
Good Ping Targets by Use Case
The "good ping" threshold varies significantly depending on what you're doing. Here's what each application actually needs:
Cloud gaming services like GeForce Now and Xbox Cloud Gaming are uniquely sensitive to ping because all rendering happens on a remote server — your input travels to the server, is processed, and the resulting video frame travels back to you. The total visual latency is roughly ping × 2 + encoding/decoding time. Even 40ms ping results in 80ms+ total input-to-display latency, which many players find noticeable.
Why You Can't Always Get Low Ping
Ping to distant servers is governed by physics. Light in fiber travels at roughly 200,000 km/s — about 5ms per 1,000 km one-way, so a minimum round-trip time of 10ms per 1,000 km of direct fiber distance. Real routing adds roughly 30–50% on top of that due to non-straight paths, processing delays, and the mix of fiber and copper in networks.
| Route | Approximate Distance | Theoretical Min RT | Typical Real Ping |
|---|---|---|---|
| London → Frankfurt | ~650 km | ~6ms | 8–15ms |
| New York → Chicago | ~1,200 km | ~12ms | 15–25ms |
| New York → Los Angeles | ~4,500 km | ~45ms | 60–80ms |
| London → New York | ~5,600 km | ~56ms | 70–90ms |
| Los Angeles → Tokyo | ~8,800 km | ~88ms | 110–150ms |
| London → Sydney | ~16,900 km | ~170ms | 240–280ms |
The practical implication: if you're in Europe playing on a North American server, you will have 80–100ms ping no matter how good your connection is. This isn't a technical problem you can solve — it's the speed of light. Always select a server region geographically close to you.
When Ping Doesn't Tell the Full Story
Ping is an average. It's entirely possible to have a 15ms average ping and a terrible gaming experience if your jitter is 30ms — meaning your latency swings between 0ms and 45ms unpredictably. The game engine tries to compensate for stable latency through lag compensation, but inconsistent latency defeats those algorithms.
This is why "my ping is fine but the game feels broken" is such a common complaint. The ping is fine — the jitter isn't. Most in-game ping displays show only the average, hiding the variance that's actually causing the problem.
The rule of thumb: a stable 50ms ping is better than an unstable 15ms ping for any real-time application. Once you've confirmed your ping is in a reasonable range for your server region, shift focus to jitter as the more actionable metric.
How to Improve Your Ping
Unlike jitter — which is largely within your control — ping is mostly determined by factors outside your home:
- Choose the nearest server region — In games and cloud services, always select the region geographically closest to you. This is the single biggest lever available.
- Use Ethernet instead of Wi-Fi — Wi-Fi adds 2–15ms of latency on top of your base ping, plus jitter. Ethernet brings your local-network overhead to under 1ms.
- Check your ISP's routing — Some ISPs route traffic inefficiently, adding 20–40ms of unnecessary latency through suboptimal peering. A different ISP with better peering to your target servers can make a meaningful difference.
- Gaming VPNs for specific routes — Some VPN providers (Wtfast, Exitlag) have direct peering to popular game servers and can actually reduce latency compared to your ISP's default routing. Results vary significantly by location and game.
- Wired connection from ISP junction — If your ISP provides a modem/router combo, using your own router connected directly to the modem (rather than over a second Wi-Fi hop) eliminates double-NAT overhead.
Check your actual ping and jitter right now — see exactly where you stand.
// MEASURE MY PINGSummary
A "good" ping depends entirely on what you're doing. For competitive gaming, under 30ms is the target. For everything else — casual gaming, video calls, VoIP, streaming — under 80ms is comfortable and under 100ms is acceptable. Ping above 150ms becomes noticeable in conversation, and above 300ms VoIP becomes difficult.
The most important takeaway: once your ping is reasonable for your server region, it's usually not the problem. Jitter — the consistency of your latency — is what makes a connection feel smooth or broken. If your ping looks fine but your gaming or calls feel off, measure your jitter next. That's almost always where the real issue lies.