What Is a Good Ping for Gaming?

What ping actually measures

Ping is a common shorthand for round-trip time: how long it takes a small piece of data to travel from your device to a server and back again, measured in milliseconds. In gaming, that server is usually the one hosting your match, and ping describes roughly how quickly your actions — moving, aiming, pressing a button — can be reflected in the game world, and how quickly you see what other players are doing.

Ping / round-trip time

The time for a signal to travel from your device to a destination and back, in milliseconds. A ping of 30 ms means a round trip takes about a thirtieth of a second — fast enough that most people cannot consciously perceive the delay.

Norynt reports this as idle latency: the response time of your connection when nothing else is competing for it. It is a close, though not identical, cousin of the ping figure shown inside a game, which is measured to that specific game's server rather than to a general test point. The two numbers will usually be in the same range but rarely identical.

It helps to think of ping as two one-way trips added together, because that is what it actually is: the time for your input to reach the server, plus the time for the server's response to reach you. Neither half is usually reported on its own, but the total is what determines how far the game world has moved on by the time you see the result of an action you took a moment earlier.

Why distance to the server usually dominates

Physical distance is one of the biggest factors in ping, because signals take time to travel even at close to the speed of light through cable and fibre. In practice, data on real networks travels noticeably slower than the theoretical speed of light in a vacuum, because it passes through many pieces of equipment along the way, each adding a small amount of processing delay, and because it rarely follows a straight line between two points.

As a rough guide, every additional 1,000 kilometres of distance tends to add somewhere in the region of 10–15 ms to a round trip once real-world routing and equipment are accounted for. A player near a game's server might see a ping of 10–20 ms, while a player on another continent connecting to the same server might see 150 ms or more, purely from the distance involved — no amount of local network improvement closes that gap, because the delay is built into the geography of the connection, not into any single piece of equipment along the way.

That distance penalty is largely fixed, but it is also worth noticing what it is not: it is not a sign of a fault, and no amount of retesting will make it smaller. A player in Sydney connecting to a server in Frankfurt will not see that figure improve by upgrading their router, changing provider, or switching to Ethernet, because the delay comes from the length of the path itself. Recognising this early avoids chasing a fix that was never available in the first place, and redirects effort toward the one change that does help — picking a closer server where the game allows it.

This is why choosing a server region closer to you, where a game allows it, is often the single biggest lever available, and why it usually matters more than upgrading a router or an internet plan. A household with an unremarkable connection playing on a nearby server will typically see a lower, steadier ping than a household with an excellent connection playing on a server three time zones away.

How much that ping matters also depends heavily on the type of game. Fast-paced competitive shooters and fighting games reward split-second reactions, so even small amounts of extra delay can be the difference between landing a hit and missing one. Strategy games, simulation games, and most turn-based or slower-paced titles are far more forgiving, since the pace of play leaves plenty of room for a connection's delay to go unnoticed.

Jitter and latency spikes matter as much as the average

A steady ping of 40 ms is usually a better experience than a ping that averages 25 ms but occasionally spikes to 150 ms. Games generally cope well with a consistent delay, because they can be built to anticipate it, but a sudden spike is much harder to smooth over and is often felt directly as a stutter, a missed input, or an opponent appearing to teleport.

Jitter — the variation in ping from one moment to the next — is Norynt's way of capturing this instability, separately from the average latency figure. A connection with low average ping but high jitter can feel worse in practice than a connection with a slightly higher but very steady ping, which is why both figures are worth checking rather than one alone.

Loaded latency is closely related: it describes how much your ping rises while your connection is also busy doing something else, such as a download running in the background. For gaming, a connection that stays low and steady under load matters more than one that is merely fast when nothing else is happening.

Why background uploads wreck responsiveness even at high speeds

A common source of confusion is a household with a fast plan that still games badly. The plan might advertise several hundred megabits per second down, yet the moment someone starts a cloud backup, uploads a large video, or a security camera begins syncing footage, ping while gaming climbs sharply. The download speed has not changed at all — the problem sits entirely on the upstream side, which most home plans provide in far smaller quantity than downstream.

Game traffic itself is small and upload-light — a steady trickle of tiny packets reporting your position and actions — but it shares the same upstream link as everything else leaving your home. If a backup fills that link, the equipment carrying it typically queues packets rather than dropping them outright, and a queue does not care which packet is more urgent unless something is specifically managing it. Your game's small, latency-sensitive packet ends up waiting behind a much larger file simply because it arrived after it.

This is why a connection can show an excellent idle ping in a quiet moment and a much worse ping the instant a second device starts uploading anything substantial. It also explains why players sometimes notice their own connection getting worse specifically when someone else in the house starts a video call, since the outgoing side of a call is a continuous upload for as long as it runs. Pausing that traffic, or enabling smart queue management on a router so urgent packets are not stuck behind bulk uploads, addresses this directly, while upgrading the plan's advertised speed alone typically does not.

How much capacity gaming actually needs

It surprises many people that online gaming itself needs relatively little download and upload capacity — usually well under a single megabit per second while actively playing, since the game is mostly exchanging small, frequent updates rather than large files. A connection that struggles with online games is far more often limited by latency, jitter or an unstable Wi-Fi link than by raw speed.

The exception is everything around the game rather than the game itself: downloading updates, installing new titles, or streaming your gameplay to an audience all need considerably more capacity, and can also compete for bandwidth with the match you are actually trying to play, which is a separate problem from ping.

The packet loss limitation

One factor that matters enormously for competitive gaming is packet loss — data that goes missing in transit and has to be detected and, in some cases, resent or simply lost. Even a small amount of packet loss can cause visible stutters, rubber-banding, or brief disconnections in a fast-paced game, sometimes more disruptive than a moderately high ping.

Norynt does not measure packet loss directly. This means a favourable ping, jitter and loaded-latency result is a genuinely good sign, but it cannot fully confirm that a connection is ready for competitive play, because packet loss is a separate condition that these measurements do not capture on their own.

In practice, this means treating a good Norynt result as strong supporting evidence rather than a complete guarantee. If a game continues to feel unstable despite good latency and jitter figures, packet loss occurring somewhere on the path is a reasonable hypothesis worth investigating through the game's own network diagnostics or your router's statistics.

It also helps to separate a genuinely bad connection from a bad-feeling one. A slightly higher but rock-steady ping of 60 ms rarely bothers competitive players once they adjust to it, because the delay is predictable and the game can be played around it. Occasional packet loss on an otherwise excellent connection, by contrast, produces the kind of jarring, unpredictable moment — a shot that should have landed, a character that briefly freezes then snaps forward — that players tend to describe as feeling far worse than the numbers alone would suggest.