What packet loss actually is
Everything your game sends across the internet travels as small chunks of data called packets. Each carries a tiny piece of the picture: your position, your movement, a shot you fired, the position of an opponent. Your device sends a constant stream of them to the game server, and the server sends a constant stream back. Packet loss is the percentage that never complete the journey.
The two problems players constantly confuse are latency and loss, and they behave very differently. Latency is delay: every packet arrives, but each takes longer than it should, so the game world is consistently a fraction of a second behind reality. Loss is absence: most packets arrive on time, but some vanish entirely, so the game world has gaps in it. Those gaps produce the strange behaviour loss is known for, an enemy who teleports, a shot that clearly hit but never registered, your own character snapping back to where they were a moment ago.
A third measure is worth knowing: jitter, the variation in arrival times. Loss and jitter often appear together because both are symptoms of a connection under stress, but they are not the same fault, and the fixes here are aimed at loss specifically. If your ping is simply high all the time, with nothing going missing, work through how to reduce high ping in online games instead.
Why does even a small percentage matter so much? Because games are interactive in a way video streaming is not. A streaming service can buffer several seconds ahead and quietly re-request anything missing; a live game cannot buffer the future. When a packet carrying your movement vanishes, the server and your game have to guess, correct or wait, and you feel every correction as a stutter, freeze or snap-back. Even 1–2% loss is plainly visible in a fast game, and 5% can make a match unplayable.
How packet loss feels in games
Loss has a recognisable signature. The most common signs are:
- Rubberbanding: you move forward, then snap back to an earlier position, because the server never received some of your movement packets and corrects you to the last position it knows.
- Shots that do not register: you fire at an opponent and nothing happens, because the packets describing the shot were among the missing.
- Teleporting players: opponents jump from place to place instead of moving smoothly, because the updates describing their movement arrived in bursts after gaps.
- Freezes and hitches: the whole game pauses for a fraction of a second, then fast-forwards to catch up.
Many games can show you loss directly. A number of popular titles display connection warning icons or optional network statistics, a loss percentage on an in-game display is the most honest measurement you have, because it measures the real path to the real server while you actually play. Turn it on for a few matches: if loss appears there, the problem is confirmed before you change a single setting.
| Packet loss | What you typically feel | Verdict |
|---|---|---|
| 0% | Nothing, this is the target | Healthy connection |
| Around 1% | Occasional small hitches, rare mis-registered actions | Noticeable in fast, competitive games |
| 2–5% | Regular stutter, rubberbanding, shots going missing | Worth fixing properly using the causes below |
| Over 5% | Frequent freezes, teleporting, possible disconnections | Serious fault somewhere on the path |
How to test for packet loss properly
A single quick test will not tell you much, because loss is often intermittent, it comes and goes with load, interference and time of day. Test properly and you will learn not just whether you have loss, but where it probably lives.
- Start in the game. Play for ten minutes with the game's network display enabled, if it has one, and note the loss figure at its worst, not its best, and note the time of day too.
- Run a sustained ping test. On a PC, a continuous ping to a reliable public address, left running for a few minutes, reports exactly how many replies never came back, that missing percentage is loss on your path to that address. Run at least a hundred packets; a handful tells you little. Our guide on how to test your ping before playing online games covers the tools for each device.
- Test wired and wireless separately. Run the same test over Wi-Fi, then with an Ethernet cable plugged in, the single most informative comparison in this guide, as the next section explains.
- Repeat at different times. Loss that appears only in the evening points towards congestion; loss that is always there points towards equipment or a line fault. Remember, too, that a general test measures the path to a nearby test server, not your game server, treat in-game figures as the final word on your matches.
The causes of packet loss, in the order to check them
1. Wi-Fi: the most common culprit
Wireless is the weakest link in most gaming setups. Your signal competes with walls, floors, neighbouring networks on the same channels, and interference from everyday appliances. Any of these can corrupt or drop packets even while your device reports a strong signal, signal strength and packet survival are not the same thing. If you play over Wi-Fi and you have loss, Wi-Fi is where the investigation starts.
2. Cables and connections
Wired connections lose packets too when the physical link is damaged. A cheap or ageing Ethernet cable with a cracked connector, a cable crushed under furniture, or a plug not fully seated can all produce intermittent loss that looks mysterious until someone checks the cable. Swap the cable before blaming anything more complicated, it costs almost nothing and eliminates an entire category of fault.
3. The router under strain
Your router is a small computer forwarding every packet for every device in the house. An old router, one running outdated firmware, one overheating in a closed cupboard, or one juggling dozens of devices can drop packets because it cannot keep up, or because it has degraded over weeks of uptime. Loss that worsens the longer the router has been running, and improves after a restart, points here.
4. Your provider's line and local network
Beyond your front door, the signal travels over your provider's local infrastructure, street cabinets, shared local lines, ageing connections at the property. A degrading line introduces loss that no home equipment change can touch. The evidence is loss that persists over a known-good cable, with a restarted router, at quiet times of day. That is worth a call to your provider, with your test results written down: times, percentages, and the fact that the loss survives a wired test.
5. Congestion on the route
Sometimes every part of the path is healthy, but a busy junction between networks drops packets at peak times because it is overloaded. This loss has a timetable: clean in the morning, dirty in the evening, clean again late at night. It is the hardest cause to prove and the one home fixes cannot reach, but also, as the routing section below explains, the one a different route can sometimes avoid.
6. The game server itself
A server under extreme load can drop or delay packets for everyone connected to it. The giveaway is that the whole lobby suffers at once, other players complain in chat, the problem exists in one game or region only, and your tests to everywhere else come back clean. There is nothing on your side to fix; trying a different server region, if the game allows it, is the only lever you have.
The wired test: the dividing line of this whole guide
If you do only one thing from this article, do this. Plug your PC or console directly into the router with an Ethernet cable, even a long one draped across the room for one evening, and test exactly as you normally would. What happens next splits the problem cleanly in two:
- Loss disappears or nearly disappears. Your fault lives in the wireless leg of your home network. The lasting fixes are to stay wired if you can, move the router or your setup closer together, or improve the wireless arrangement, our comparison of Wi-Fi vs Ethernet for gaming goes through the trade-offs honestly.
- Loss is unchanged. Your wireless setup is innocent. The fault is in the cable run (try a different cable to be thorough), the router, your provider's line, or the route, and each now deserves your attention in that order.
One evening with a cable tells you which half of the journey your fault lives in.
The fixes, in the order to try them
- Restart the router properly. Power it off, wait thirty seconds, power it on, and give it a few minutes to settle. This clears accumulated faults and is the honest first step for any loss that appeared gradually.
- Update the router's firmware. Manufacturers quietly fix forwarding and stability faults in updates, yet many routers run years-old software.
- Fix the wireless leg or bypass it. Move closer to the router, reduce walls between you and it, try the other Wi-Fi band if your router offers two, and stay on Ethernet permanently if the wired test improved things dramatically.
- Replace suspect cables. Swap any Ethernet cable that is damaged, kinked or of unknown origin for a known-good one.
- Reduce the load during play. Large downloads, cloud backups and other people's streaming all pressure the router and your line. Pause them for a session and retest; if loss falls away, you have found a contributing cause. If your connection feels unstable in several different ways at once rather than showing one clean fault, the methodical isolation approach in our guide to troubleshooting unstable game connections will help you separate them.
- Retest at quiet hours. If loss exists only at peak times despite everything above, treat it as congestion, at your provider or on the route, and read the routing section below.
- Escalate to your provider with evidence. Loss that survives a wired test with a swapped cable and a restarted router, recorded with dates and percentages, is a line problem until proven otherwise. Providers respond better to numbers than to "my games lag".
When a routing tool may help, and when it cannot
A routing tool can only influence the middle of the journey, the path your traffic takes across the wider internet between your provider and the game server. That middle is where packets get dropped at congested junctions between networks, and it is the one territory a routing tool can genuinely change.
If packets are being dropped at a congested junction, or on an indirect route through overloaded infrastructure, a different route can avoid the dropping point entirely. This is what a game routing tool such as GearUP Booster is built for: GearUP describes its system, which it calls Adaptive Intelligent Routing, as directing game traffic through its own network paths rather than accepting the default route, with the stated aim of reducing high ping, packet loss and jitter on that leg of the journey. The flow is simple: open the app, select your game, select a server or node, start the boost, and play, then judge it by your in-game loss display, with the tool on and off, in the same game at the same time of day.
Be equally clear about what it cannot do. It cannot recover packets your Wi-Fi already dropped in your living room. It cannot repair a damaged cable, an exhausted router or a faulty line to your house. And it cannot save packets a struggling game server drops for the whole lobby. If your loss arrives in sudden spikes rather than as a steady percentage, some causes differ, and that guide is the better companion to this one. Judge any tool honestly: if your measured loss falls consistently across several sessions with it active, it is helping your connection; if the numbers do not move, the fault is somewhere it cannot reach.
Frequently asked questions
How much packet loss is acceptable for gaming?+
Zero is the target, and a healthy connection usually achieves it. Around 1% is noticeable in fast competitive games; 2–5% causes regular stutter and rubberbanding; anything above that suggests a genuine fault worth tracking down rather than tolerating.
Can I have packet loss with a low ping?+
Yes, and this confuses many players. Ping measures the packets that arrive; loss counts the ones that never do. A connection can deliver most packets quickly while dropping enough to ruin a match, the ping number alone never tells the whole story.
My loss only happens in the evening. What does that mean?+
A timetable like that usually means congestion: your household is busiest then, your provider's local network is busiest then, or junctions on the route are busiest then. Run the wired test in the evening, if loss survives it, the congestion sits beyond your home, with your provider or on the route.
Will a new router fix packet loss?+
Only if the old router is the cause. If your loss improves after a restart or worsens with router uptime, a replacement is reasonable. If the loss is on your provider's line, a new router changes nothing, test first, spend second.
Can a booster fix packet loss?+
It can help in one specific situation: when packets are dropped on the route between your provider and the game server, a different route may avoid the dropping point. It cannot fix loss caused by your Wi-Fi, cables, router or provider's line. Measure your loss with the tool on and off before deciding.
Packet loss feels mysterious because it is invisible, until you test for it. Run the wired test, and you will know which half of the journey your missing packets are dying in. Fix the cause your tests point to, in order, and judge every change, including any routing tool, by whether the loss percentage you measured honestly falls.
