What's a Good Ping? Understanding Network Latency

“Latency” and “ping” get used constantly, especially around gaming and video calls, but the actual numbers rarely get explained. Here’s what they mean, what’s normal, and what actually affects them.

What latency actually measures

Latency is the round-trip time for data to travel from your device to a server and back - measured in milliseconds (ms). It’s a measure of delay, not speed: a connection can have plenty of bandwidth (fast downloads) and still have high latency (a noticeable lag before anything happens), because they’re caused by different things.

Rough guide to what the numbers mean in practice:

Under 50ms - excellent. Video calls and competitive gaming feel instant.
50-150ms - good for most everyday use, including video calls; noticeable but not disruptive for fast-paced gaming.
150-300ms - usable for browsing and streaming, but video calls start to feel slightly delayed, and real-time gaming becomes frustrating.
300ms+ - a delay most people will notice in almost anything interactive.

What actually causes latency

Mostly, physical distance and the number of network hops in between:

Distance to the server. Data can’t travel faster than the speed of light through fiber, so a server on the other side of the planet will always have a latency floor a nearby one doesn’t.
Number of network hops. Every router your traffic passes through adds a small delay. A congested or poorly peered route can add far more hops than a direct one, even over a similar distance.
Your local connection. WiFi congestion, an overloaded router, or a poor mobile signal all add latency before your traffic even leaves your building.
Server-side load. A slow or overloaded server adds to round-trip time regardless of how good your network path is.

Checking your own latency

Our Global Latency Checker measures your browser’s round-trip connection time to several real regions around the world, so you can see where your connection is naturally fast and where it isn’t. If you’re in India and see a low number to Mumbai but a much higher one to São Paulo, that’s expected - it reflects real physical distance, not a problem with your connection.

Important distinction: high latency to a distant region isn’t the same thing as a site being down or blocked at the DNS level. A slow-but-working connection and a genuinely broken one look different if you check properly - latency tells you about speed and distance, not availability. If a specific site won’t load at all rather than just loading slowly, that calls for a different check, not a latency test.

When latency is worth worrying about

For ordinary browsing, latency differences of even a couple hundred milliseconds are barely noticeable. It matters most for things that need fast back-and-forth: video calls, real-time multiplayer gaming, and remote desktop or SSH sessions. If those feel laggy, checking your latency to relevant regions is a reasonable first step before assuming something’s broken.