Skip to content
Gameping

Jitter and Packet Loss — The Silent Lag Killers

Ping is not the only villain. Jitter and packet loss cause most of the lag you feel. Here is how to measure and fix them.

Jitter and Packet Loss — The Silent Lag Killers

If your ping shows 30ms but the game still feels laggy, the villain is usually jitter or packet loss. Both metrics can matter more than raw ping. This article covers what they are, why they hurt, and how you fix them.

What Is Jitter?

Jitter is the variance of your ping over time. Steady 40ms means 0 jitter. A ping bouncing 30, 60, 45, 70, 35 has high jitter.

Technical definition: the average absolute difference between consecutive ping samples. Under 5ms is perfect. 5-15ms is acceptable. Above 15ms is a problem. Above 30ms wrecks the game.

Stable 60ms is better than jittery 40ms. Stable ping lets the server predict your input and interpolate. Jittery ping breaks the prediction.

Why Jitter Hurts So Much

Game servers expect input at regular intervals. On a 128 tick server that is every 7.8ms. Irregular arrival breaks the server's assumptions.

In-game symptoms:

  • Character rubberbands, snapping backwards.
  • You shoot, opponent does not die.
  • Skillshot animation starts but the projectile never spawns.
  • Movement looks choppy on your screen.
  • Voice chat drops out.

A 40ms link with 25ms jitter feels worse than a steady 100ms link. Pro players check jitter before they check ping.

What Is Packet Loss?

Packet loss is when packets never reach the destination. 0% is perfect. 1% is tolerable. 2% or more breaks the game.

A lost packet means: you fired the shot but the server never heard about it. In TCP the packet gets retransmitted. Games use UDP because speed matters most. In UDP a lost packet stays lost.

Signs of Packet Loss

Watch for these:

  • Weapon fires but does no damage.
  • Ability triggers but nothing happens.
  • You teleport 5 meters instantly.
  • "Reconnecting" message pops up.
  • Server connection drops.

If any of these show up, ping alone is not enough. Measure packet loss.

How to Measure Jitter

Windows terminal, 20 samples:

ping -n 20 google.com

The important number is not the average. It is the difference between minimum and maximum. A 30ms gap means high jitter.

Gameping shows jitter alongside median ping. Every region gets 15 samples, standard deviation gets calculated, you see a clean number.

How to Measure Packet Loss

Terminal:

ping -n 100 google.com

Look for the "Lost = X" line. 0 is perfect. 1-2 is rare jitter. 5+ is a real problem.

For deeper diagnosis use PathPing on Windows or MTR on Linux/Mac. Both measure loss per hop, showing whether the problem is in your router, your ISP, or somewhere further out.

Common Causes

The top 5 sources of jitter and loss:

  1. Wi-Fi. Wireless produces variable latency by design. Ethernet solves 90% of cases.
  2. ISP congestion. Peak hours (20:00-24:00) load up shared infrastructure. Even fiber gets hit.
  3. Aging router. Buffer overflows drop packets under load.
  4. Background traffic. Torrents, YouTube, cloud backup eat bandwidth.
  5. Bad cable. A cracked RJ45 connector drops packets at random.

These five explain roughly 85% of player-side issues. Our 12 tips for lowest ping covers fixes for each.

How to Fix It

In order:

  1. Switch to Ethernet. Wi-Fi jitter usually vanishes.
  2. Reboot the router. Clears buffers.
  3. Enable QoS. Gaming mode prioritizes game packets.
  4. Kill background downloads. Steam, Windows Update, cloud sync — all off.
  5. Replace the cable. Cat6 is cheap and swap takes 30 seconds.
  6. Change DNS to 1.1.1.1. Some ISP DNS servers time out.

If jitter persists, your ISP peering is the suspect. A VPN or ExitLag can help there. On healthy ISPs neither is needed.

Ping vs Jitter vs Packet Loss — Priority

Player priority order:

  1. Packet loss must be zero. Even 1% causes deaths.
  2. Jitter under 15ms. Anything higher makes the game unpredictable.
  3. Ping as low as possible. But 40 vs 60 matters less than 5ms vs 25ms jitter.

Fix in that order: loss first, jitter second, ping last.

Real Example

A Valorant player complains: "50ms ping but I cannot play." Test results:

  • Median ping 52ms.
  • Jitter 28ms.
  • Packet loss 1.8%.

Ping looks fine. Jitter and loss are ugly. Fix order: cable swap (jitter down to 12ms), Steam update paused (loss to 0%). Game felt smooth again.

Summary

Jitter and packet loss shape game feel more than raw ping. Steady 60ms always beats jittery 30ms. Your ping tool should show all three metrics. When you test, look at median ping, jitter and packet loss together.

Head to the home page and run a full test. Then follow the ping-lowering playbook to fix what you find.