What Packet Loss Does to Your Games

Packet loss happens when data packets travelling between you and the server never arrive and have to be resent — or are simply gone. Unlike high ping, which delays everything evenly, packet loss creates gaps: players teleport ("rubber-banding"), shots you clearly landed do nothing, voice chat turns robotic, and in bad cases the game disconnects entirely. The frustrating part is that your speed test can look perfect while loss is wrecking your matches, because raw bandwidth and packet delivery are different things. The good news: packet loss almost always has a findable location, and once you know where packets are dying, the fix is usually straightforward.

What Loss Percentages Actually Mean

0% to 0.5%: effectively clean. Occasional single drops are normal on any network and game netcode absorbs them invisibly.
0.5% to 1%: mostly fine for casual play, but fast shooters may show the occasional missed hit or micro-stutter.
1% to 3%: clearly noticeable. Rubber-banding, delayed ability activations, and choppy player movement become regular.
3% to 5%: competitive play is compromised — expect frequent desync and hit registration failures.
Above 5%: typically unplayable in real time. Many games will show a connection warning icon or drop you from the match.

These are typical ranges, not hard limits — a game with aggressive lag compensation tolerates more loss than a fighting game with rollback netcode tuned for near-zero loss.

Step 1: Find Where the Loss Happens

Packet loss occurs in one of three zones: inside your home network, on your ISP's infrastructure, or at the game server. Isolate it before changing anything:

Test your own router first. On Windows, run ping -n 50 192.168.1.1 (or your router's address). Any loss here means the problem is inside your home — usually Wi-Fi or cabling.
Test past your router. Run ping -n 50 1.1.1.1. Loss here but not to the router points at your modem, the line into your home, or your ISP.
Trace the full path. Use pathping on Windows or mtr on Mac/Linux to see which hop starts dropping packets. Loss that begins mid-route and continues to the end is real; loss at a single middle hop that disappears afterwards is usually just that router deprioritizing diagnostic pings.
Check the browser view. A quick online packet loss test or our ping and jitter test gives you a fast before/after baseline while you apply fixes — keeping in mind browser tests measure HTTPS round-trips to nearby endpoints, a real-world proxy rather than in-game packets.

Fixing Loss Inside Your Home

If step 1 showed loss to your own router, work through these in order:

Get off Wi-Fi to confirm. Plug in an Ethernet cable and re-test. If loss vanishes, the issue is wireless interference or weak signal — see our Wi-Fi vs Ethernet comparison for permanent options.
Inspect the cable. A kinked, chewed, or decade-old Cat5 cable can pass a speed test yet corrupt packets under load. Swap in a known-good Cat5e/Cat6 cable — they cost very little.
Update the NIC driver. Outdated or buggy network adapter drivers are a classic silent cause on PCs, especially Realtek and Killer adapters. Get the driver from the manufacturer, not just Windows Update.
Update router firmware and reboot it. Memory leaks in long-running consumer routers cause creeping loss; a firmware update plus a restart clears both.
Reduce Wi-Fi contention. Move to the 5 GHz band, change channels away from neighbors, and keep the router away from microwaves and Bluetooth-heavy areas.

Fixing Loss on the ISP Side

If loss starts at or beyond your modem, you need your ISP — and evidence gets you past first-level support. Collect a pathping or mtr log, note the times of day it occurs, and confirm it happens on a wired connection with all other devices offline. Then tell support exactly that: "I see X% packet loss starting at hop 2 on a wired connection, verified with pathping, at these times." Ask them to check the line's signal levels and error counters. On cable connections, degraded coax, water in an outdoor junction box, or a failing modem are common culprits; a technician visit often resolves what no amount of rebooting will.

When the Game Server Is the Problem

If your connection tests clean but one specific game stutters, the loss is likely on the server's side or on the route to that region. Check the game's server status page, try a different server region, and compare with friends in your area. There is nothing to fix locally — but confirming it saves you hours of pointless router tweaking.

Keeping It Fixed

Once clean, prevent regressions: keep bulk downloads paused while gaming, enable QoS or Smart Queue Management on your router so uploads cannot starve game traffic, and re-run a quick loss test whenever rubber-banding returns. Packet loss that comes back at the same hour every evening usually means peak-time congestion — a different problem with its own fixes.