Few things are as frustrating in an online game as packet loss. Your character rubber-bands back to where you were a second ago, other players teleport across the map, and shots that clearly hit simply do not register. Your ping can look perfectly normal throughout, which confuses many players: they see a good number and conclude nothing is wrong. Something is wrong, but it is a different kind of wrong, needing different fixes.
This guide explains what packet loss is, how it differs from high ping, how to test for it, and the fixes in order, from the ones you control to the ones only your provider can solve.
What packet loss actually is
Online games send a constant stream of small packets between your PC and the server: your position, your actions, and the returning world state. Packet loss is when some never arrive. The game guesses what happened in the gap, and when the next packet contradicts the guess, your character snaps back. That snap is rubber-banding, the classic symptom.
A little loss is invisible, since games tolerate an occasional dropped packet. Sustained loss above two to three percent produces visible rubber-banding, delayed actions, and missed hits. Loss can happen anywhere on the route: your cable or Wi-Fi, your router, or your provider's network. Where it happens decides who can fix it, which is why testing before fixing matters.
Packet loss is not high ping
Ping and packet loss describe two different properties of a connection. Ping, or latency, is how long a packet takes to travel to the server and back; packet loss is how many packets never complete the trip. You can have low ping with heavy packet loss, and high ping with zero loss. They feel different too: high ping is a constant delay on everything, packet loss is sudden jumps, freezes, and vanishing actions.
The usual ping fixes do not necessarily fix loss, so if your symptoms are rubber-banding and teleporting rather than a steady delay, test for loss first. If you have already worked on latency, our guide to lowering ping in online games covers that side.
Test for packet loss properly
Do not rely on a single speed test, which measures bandwidth rather than loss and runs for only a few seconds. Packet loss is often intermittent, so a useful test sends many packets over a sustained period. Windows has two built-in tools that do that, and you need no extra software.
Quick test with ping: open Command Prompt and run ping -n 100 8.8.8.8, which sends one hundred packets and reports how many were lost. Run it while the problem is happening if you can: loss that only appears under load will not show in a quiet test. Zero lost means a clean connection to that target; above a couple of percent confirms the problem.
Locate the loss with pathping: a ping test tells you loss exists, but not where. For that, run pathping 8.8.8.8 in Command Prompt. It traces the route, pings each hop, and reports loss per hop; this takes several minutes, so let it finish. Read the pattern: loss starting at one hop and continuing at every hop after it points to that hop. Loss that appears at one hop but disappears later is usually that hop deprioritising ping traffic, not real loss.
Test more than once and at different times of day: evening-only loss, when your neighbourhood is busy, tells a different story from round-the-clock loss.
Read your results before changing anything
Your results divide the problem into three cases:
- Loss starts at your router, the first hop: the problem is inside your home: your cable, Wi-Fi, or router. This is the case you can fix yourself, and the most common one.
- Loss starts part-way along the route: the problem is in your provider's network or beyond. Home fixes will not help much, but the test output is valuable evidence for your provider.
- Loss appears only on the final hop, the game server: the problem may be the server or the route into it. Try a different region or game to confirm.
Save your test output: when contacting your provider, a pathping result showing exactly where loss begins beats any description of rubber-banding.
Fixes you control: cable, Wi-Fi, and your own network
Work through these in order, testing after each change:
- Switch to a wired connection. This is the single most effective home fix: Wi-Fi suffers interference from neighbours, walls, appliances, and distance.
- Check the cable itself. A damaged or low-quality cable can drop packets, so try a different one, especially if yours came free with a router years ago.
- Restart your modem and router. Power them off for about thirty seconds, then back on, to clear stale states and force a fresh connection. Do it once, properly.
- Improve your Wi-Fi if you must stay wireless. Move closer to the router, use the 5 GHz band if offered, and keep it away from thick walls and metal objects. Pause streaming and downloads on other devices during play.
- Close bandwidth-hungry software on your PC. Cloud backups, background updates, and video calls can saturate your upload, a classic cause of game packet loss. Our guide to speeding up Steam downloads also covers limiting launcher bandwidth.
- Update your network drivers and router firmware. Outdated drivers can mishandle packets under load, and firmware updates often fix stability bugs. Get drivers from your PC maker's site, firmware from your router maker's site.
Router settings and provider-side fixes
Check two router settings first: Quality of Service (QoS), which prioritises your gaming PC when busy, and bufferbloat controls; without smart queue management, limit upload usage during play.
When loss starts beyond your home, contact your provider with your test output: destination, the hop where loss begins, loss percentage, and times of day, and ask about congestion or a fault on that route. If the provider insists the line is clean, test from a different device: loss that follows the connection, not the device, is strong evidence the problem is theirs.
A gaming VPN sometimes helps provider-routing loss by bypassing a congested hop via the VPN provider's network. But it adds overhead and can make things worse, so keep it only if the numbers genuinely improve. It will never fix loss on your own Wi-Fi or cable.
What will not fix packet loss
It is easy to waste time on fixes for a different problem. Changing DNS will not fix packet loss: DNS only affects name resolution before a connection starts, not whether packets arrive during it. Upgrading your speed will not fix loss either, unless saturation is the cause, because loss is about reliability, not bandwidth. Reinstalling the game will not fix it, since the problem is in transit, not in files on your disk.
If loss shows only to one game server, switch region and test again: consistent, slightly delayed input beats input that randomly vanishes. Packet loss feels random, which tempts random fixes. Resist that. Test first, find the hop where loss begins, and fix that hop. Most players find the problem on their own side of the router, fixed by a cable, a restarted router, or a quieter network.
