Why Your Ping Is High and Games Lag

Rubber-banding, hit registration problems and sudden spikes are usually not bandwidth. Here is what actually causes them, how to measure which one you have, and what genuinely helps.

You have a fast connection. The speed test says so. And you are still rubber-banding across the map, losing fights you clearly won on your screen, and watching the ping counter spike into the hundreds for no visible reason.

If the speed test really does come back fast, bandwidth is not your problem. A competitive shooter uses a few hundred kilobits per second — less than a music stream. What games need is consistency: small packets arriving reliably and on time, every time. That is a completely different property from throughput, and it is the one nothing in a speed test measures.

The exception is worth naming, because it is not rare. Bandwidth matters when there is genuinely not enough to go round: a slow rural line, a congested mobile or satellite link, or a modest connection with several people on it while a console downloads an update in the background. Upload is where this bites first, since upstream capacity is usually a fraction of downstream and games need it in both directions.

Even then the mechanism is usually queueing rather than capacity — the link fills, packets queue, and latency climbs long before throughput actually runs out. That is bufferbloat, and it is why a faster plan often changes nothing while a queue-management setting fixes it outright. Capacity is the real constraint only when you are saturating the line more or less constantly, at which point the fix is more of it.

Fast internet, still lagging?

Test the things a speed test misses. The connection test reports packet loss, jitter and latency separately, in both directions — the three numbers that explain nearly every lag complaint.

Run the connection test →

What is causing your gaming lag?

Different symptoms come from different faults. Matching yours to the right one saves a lot of pointless setting changes.

1. Distance — the one you cannot fix

Latency has a floor set by physics. Light travels through fibre at roughly 200,000 km/s, so distance puts a hard lower bound on latency — and real routes add extra distance and equipment delay on top. A round trip from London to Virginia will not beat roughly 75 ms. A distant server cannot be made low-ping by buying a faster internet plan.

If your ping to a nearby server is 20 ms and to a distant one 180 ms, nothing is broken. Choosing a geographically closer — or better-routed — server is usually the most effective way to reduce distance-related latency, which is why server selection matters more than any hardware upgrade. Closer is not always better routed, and an MTR will show you which.

What does not help: more bandwidth, a "gaming" router, or a gaming VPN — with one narrow exception covered below.

2. Packet loss — the rubber-banding one

Many multiplayer games send position updates over UDP because waiting for a retransmission is worse than losing an already-outdated update — though games also use TCP and other protocols for some traffic, such as chat, matchmaking and downloads. For the gameplay stream, a lost packet is usually simply gone. When updates go missing, the client and server disagree about where things are. The server corrects you, and you snap backwards.

That correction is exactly what rubber-banding is. Teleporting enemies, shots that clearly connected registering as misses, and being killed after reaching cover are all the same underlying problem seen from different angles.

Games tolerate a little loss and interpolate through it. There is no universal percentage at which every game becomes unplayable — the impact depends on the game, the timing, how loss is distributed and how the engine handles missing updates. As a practical guideline, persistent loss around 1% or above is worth investigating. Bursty loss is far worse than the same percentage spread evenly — forty consecutive missing updates is a visible teleport, while the same total scattered thinly can be imperceptible, which is why bursty loss can disrupt play well below 1%.

Diagnosing it is the subject of what causes packet loss, but the short version for gamers: test wired before anything else.

3. Jitter — the one nobody talks about

Jitter is variation in latency between consecutive packets, and it explains one of the most frustrating experiences in online gaming: a connection that looks fine on paper and feels wrong to play on.

Stable connection          average 30 ms
  30  31  29  30  31  30  29  ms

Jittery connection         average 30 ms
   8  55  12  70  15  48  11  ms

The average is identical, but the second connection is far less predictable. The first is steady and your aim works. The second makes hit registration feel arbitrary, because the server is receiving your inputs at wildly varying delays and reconciling them against other players whose timing is steady.

This is why "my ping is fine but the game feels off" is a real observation rather than imagination. Ping counters show an average and hide the variation entirely.

As a practical guideline, lower is better: under about 5 ms is excellent, 5–15 ms is generally workable, and repeated spikes above roughly 20–30 ms become noticeable in fast-paced games. Treat these as guidelines rather than hard thresholds.

4. Bufferbloat — the "someone started a download" one

If your game is fine until a housemate opens Netflix or a console starts updating, bufferbloat or queueing under load is a strong suspect — though congestion further upstream and traffic shaping can produce the same shape.

Oversized buffers in consumer routers queue packets rather than dropping them when the link is busy, so latency climbs from 20 ms to 300 ms and stays there until the transfer finishes. Your bandwidth is not exhausted — your queue is.

It is measurable in a minute and genuinely fixable at your end, which makes it the highest-value thing on this page. The bufferbloat guide covers testing and the fix in detail.

The ten-minute gaming network test

Five steps. Each one changes a single variable, which is what makes the result mean something.

1. Baseline. Run the connection test over Ethernet with nothing else running. Note packet loss, jitter and latency. This is your connection at its best.

2. Under load. Start a large upload and run it again. If latency multiplies, you have bufferbloat.

3. Wi-Fi comparison. Run it once more over Wi-Fi. If loss or jitter appears that was not there on the cable, wireless is your problem.

4. Repeat during a bad period. A test taken when everything feels fine tells you little. The comparison between good and bad is the evidence.

5. Check the path to something in the region your game servers live:

Windows          tracert 1.1.1.1
macOS / Linux    mtr 1.1.1.1

Or use the MTR tool, which probes continuously and catches intermittent faults a single traceroute misses. Persistent loss that begins at a hop and continues through every hop after it is the stronger evidence of a problem affecting the path at or before that point. Loss at a single intermediate hop that disappears at later hops usually means that router is rate-limiting or deprioritising probe replies rather than dropping transit traffic — a common misreading.

What actually helps

In descending order of effect, which is roughly the reverse of what gets recommended in forums.

Use Ethernet. Not advice anyone wants, and still the easiest way to eliminate Wi-Fi as a source of jitter and intermittent loss. Wi-Fi adds jitter and loss even when signal strength looks perfect, because the medium is shared and retransmission happens invisibly below the application. If a cable is genuinely impossible, use 5 GHz, sit close to the access point, and accept a ceiling on how good it can get.

Fix bufferbloat. Enable SQM on your router if it supports it. This is the fix that most often turns an unplayable evening connection into a fine one, and it costs nothing.

Pick the closest server. Manually, where the game allows it. Automatic selection frequently optimises for population rather than latency.

Stop background traffic. Cloud backups, game updates downloading in the background, another device streaming 4K. Pausing these during play is crude but effective.

Check for interference. If you must use Wi-Fi, move to a clear channel on 5 GHz. Neighbouring networks on 2.4 GHz are a common cause of periodic spikes that correlate with nothing you are doing.

What does not help

Being direct about this, because these are heavily marketed.

More bandwidth, if you already have enough. Going from 100 Mbps to 1 Gbps changes nothing about latency, loss or jitter, and a game needs a fraction of either — which makes this the most commonly sold non-solution in the category. The upgrade is worth it only if you are actually running out: constantly saturated, several heavy users, or an upload so small that one backup starves everything. If the line is idle when the game feels bad, capacity is not what you are short of.

"Gaming" routers. The label is mostly marketing. What matters is whether the firmware supports proper queue management — a cheap router running OpenWrt with fq_codel will outperform an expensive one without it. Buy for SQM support, not for styling.

Gaming VPNs, usually. A VPN adds a hop and normally increases latency. The narrow exception is when your ISP routes badly to a particular destination and the VPN happens to take a better path — real, but uncommon, and worth testing before paying for it. Measure with and without rather than assuming.

Most "network optimiser" software. Registry tweaks and TCP tuning utilities have negligible effect on modern systems, and latency-sensitive gameplay traffic generally does not run over TCP in the first place.

Closing background applications, beyond ones actually using the network. A chat client uses no meaningful bandwidth. The problem is transfers, not process count.

Telling network lag from FPS lag

These get confused constantly, and they need entirely different fixes. Stuttering caused by GPU or CPU limits feels similar to network lag but has nothing to do with your connection.

The quickest separation: turn on your game's frame-rate counter and its network graph together. If the frame rate dips when it stutters, it is your machine. If the frame rate holds steady and the ping graph spikes, it is the network.

When it is not your connection

Some things look like network problems and are not.

Server-side issues. If everyone in the match is complaining simultaneously, the game server is the problem. Nothing at your end will help.

The return path. Routing is asymmetric, and your outbound path can be clean while the route back is congested. A traceroute run from your machine cannot directly show the return path, so investigating that direction means testing from or toward the remote side. It explains a proportion of "my connection is fine but this one server is unplayable" cases.

ISP peering. If one particular game is bad while everything else is fine, the problem may be at the interconnect between your ISP and that game's hosting provider. An MTR to the game server during a bad period, compared with a good one, will usually show where. If it is consistent, it is worth reporting with evidence.

Frequently asked questions

Why is my ping so high when my internet is fast?

Speed and latency are unrelated measurements. Bandwidth is how much data moves at once; ping is how long a round trip takes, and it is governed by distance, routing and queueing. A gigabit connection to a server on another continent will still have high ping.

What is a good ping for gaming?

There is no universal "good ping" number — these are practical guidelines rather than pass/fail boundaries. Under 30 ms is excellent, 30–60 ms is good and competitive play is comfortable, 60–100 ms is playable for most genres, and above 100 ms puts you at a real disadvantage in anything reaction-based. Consistency matters as much as the number — steady 60 ms beats an average of 40 ms that swings between 10 and 90.

Why do I rubber-band even with low ping?

Packet loss is the most common cause: position updates go missing, the server corrects you, and you snap backwards. Severe jitter, server-side problems and game-specific synchronisation issues can produce the same symptom, so it is not exclusively loss. What it is generally not is distance — low average ping with rubber-banding points at loss or timing rather than how far away the server is.

Does a wired connection really reduce ping?

It reduces latency slightly, but the larger benefit is consistency. Wi-Fi introduces jitter and intermittent loss even with a strong signal, because the medium is shared and retransmissions happen below the application. The improvement in how the game feels is usually much bigger than the change in the ping number.

Will a gaming VPN reduce my ping?

Usually it increases it, since traffic takes a longer path through the provider. The exception is when your ISP routes poorly to a specific destination and the VPN's path is better. It is worth measuring with and without before subscribing — treat any guaranteed improvement as marketing.

Why does my ping spike when someone else uses the internet?

Bufferbloat. Oversized buffers queue packets when the link saturates, so latency climbs sharply the moment anyone starts a large transfer. Enabling Smart Queue Management on your router usually fixes it — see the bufferbloat guide.

Can packet loss be caused by my own PC?

Yes. A failing network adapter, an outdated driver, a damaged cable or aggressive power management on the adapter can all cause loss before traffic ever leaves your machine. Checking interface error counters — netstat -e on Windows — will show whether errors are accumulating locally.

Is 1% packet loss bad for gaming?

It is around the level where many people begin noticing, but distribution matters more than the number: 1% spread evenly is often imperceptible, while 1% arriving in bursts produces visible teleporting. Sustained loss above a couple of percent will affect competitive play in most titles, though the exact point varies by game.