Rubber-banding, warping and sudden lag spikes — even on a low ping — are usually packet loss, not raw latency. Here's what causes it and how to track it down.
Quick answer
Packet loss is data that never arrives, and it causes rubber-banding and lag spikes even with a low ping. The usual causes are Wi-Fi interference, an overloaded home connection, a faulty cable or router, or congestion on your ISP's route. Test with a continuous ping or WinMTR to see where the loss starts, then fix that hop — starting with a wired connection.
Packet loss vs ping
Ping is how long a packet takes; packet loss is packets never arriving. You can have a great ping and still rubber-band badly if even 2–5% of packets vanish — the game keeps having to correct your position.
Common causes
- Wi‑Fi — interference and weak signal are the #1 cause; cable beats Wi‑Fi every time for gaming.
- Overloaded connection — downloads/streams saturating your upload.
- A bad hop — a congested or faulty router somewhere along the route.
- Faulty cable or hardware — an old Ethernet cable or failing router port.
- ISP congestion — especially at peak evening hours.
How to test for it
A continuous ping shows drops; WinMTR (Windows) or mtr (Linux) shows loss at each hop, so you can see where it starts:
# Linux/macOS — live per-hop loss
mtr server-ip
# Windows — download WinMTR, enter the server IP, let it run a few minutesLoss that appears at one middle hop but clears by the last hop is usually just a router de-prioritising pings — harmless. Loss that starts at a hop and continues all the way to the destination is the real problem.
How to fix it on your end
- Switch from Wi‑Fi to a wired Ethernet connection.
- Stop big downloads/streams while playing.
- Swap the Ethernet cable and try a different router port.
- Restart your router; update its firmware.
- If loss is only at the final hops, it's the route/ISP — report it with a WinMTR.
When it's the route, not you
If WinMTR shows loss only near the server and your local hops are clean, the problem is routing — which a well-peered host avoids. Send the WinMTR to the server's host so they can investigate the path.
Low ping but warping? It's packet loss. Go wired first — it fixes most of it instantly.
Packet loss caused by your own router or network equipment
Beyond Wi-Fi and ISP congestion, aging router hardware can drop packets under load — overheating, a failing capacitor, or firmware that hasn't been updated in years. Isolate this by pinging your own router/gateway IP (usually 192.168.1.1) while playing: if that shows loss too, the problem never leaves your house, and no amount of ISP or server troubleshooting will fix it.
How to prevent packet loss before it ruins a match
- Prioritise game traffic with QoS on your router, if it supports it.
- Keep firmware updated on both the router and your network adapter.
- Avoid extra mesh Wi-Fi hops for competitive play — wire the gaming PC or console directly where possible.
- Reboot your router on a schedule (weekly) if it tends to degrade the longer it stays up.
Related networking guides
If packets aren't arriving at all rather than just dropping intermittently, see "Connection timed out" joining a game server. For a broader look at lag sources, read how to reduce game server lag and ping and game server lag: CPU or network?. For background on ping itself, see what is ping and how to lower it.