What Is Packet Loss, How Much Is Too Much, and How to Fix It
Contents
Your speed test looks fine, yet in a game other players teleport around and on calls your voice turns robotic. That pattern points to packet loss: part of the data simply never arrives. Unlike a slow connection, it does not show up as low Mbps, so it is easy to miss. Here is what it is, how to measure it, and how to find out whether the problem is in your home or with your provider.
What Packet Loss Is
Everything you send and receive online is split into small pieces called packets. Packet loss is the share of those packets that leave one end but never reach the other, shown as a percentage. Intel puts it simply: packet loss is the loss of data being exchanged between your computer and a game server.
What happens next depends on the application. Downloads and web pages ask for the missing packets again, so the data arrives complete, just slower. Games, voice and video calls cannot wait for resends — a packet that is late is useless — so the gap shows up directly: characters jump back to an earlier position (rubber-banding), shots do not register, audio breaks up and video freezes. Intel notes that lost packets must be re-sent, which causes lag spikes similar to high ping.
Packet loss often travels together with high or unstable ping; see what is a good ping for latency and jitter.
How Much Packet Loss Is Too Much
The network monitoring company PingPlotter uses these thresholds:
| Packet loss | What it means |
|---|---|
| 0% | What a healthy connection should show |
| Up to 2% over 10 minutes | Acceptable on average |
| 5% or more, consistently over 10 minutes | There is likely a problem |
In practice, fast online games and calls notice even 1–2% if the loss comes in bursts. A test that shows one lost packet out of a hundred, once, is not a problem; steady loss every time you test is.
How to Test for Packet Loss
Windows: open Command Prompt and run a long ping:
ping -n 100 8.8.8.8
At the end, Windows prints Packets: Sent = 100, Received = 98, Lost = 2 (2% loss). Intel suggests the same approach with a public server.
Mac and Linux: in Terminal, run ping -c 100 8.8.8.8. The summary line shows the packet loss percentage.
In games: many games show a packet-loss indicator or percentage in the network statistics overlay. This measures loss to that game’s server, which is the number that matters for that game.
You can also use our ping test for a quick check of latency from your browser. Run tests at a quiet time and again in the evening when the network is busy — loss that appears only at peak hours points to congestion.
Find Where the Loss Happens
Packet loss can come from your device, your Wi-Fi, your router, your provider’s network or the remote server. Narrow it down step by step:
- Ping your router. Run the same command to your router’s address, for example
ping -n 100 192.168.1.1(find yours via your default gateway). Loss here means the problem is inside your home — almost always Wi-Fi or a cable. - Compare Wi-Fi and a cable. If loss to the router disappears on Ethernet, the cause is Wi-Fi: distance, walls or interference.
- Ping a public address. If the router answers cleanly but 8.8.8.8 shows loss, the loss is beyond your router — at the modem, the line or your provider.
- Trace the path. Tools like
pathpingon Windows,mtron Mac and Linux, or traceroute show at which hop the loss begins. Loss that starts at one hop and continues to the end is real; loss at a single middle hop that disappears afterward is usually that router deprioritizing pings, not a problem.
How to Fix Packet Loss
Most packet loss at home comes from a few causes. Work from the most likely:
- Use a cable for gaming and calls. Wi-Fi drops and resends packets far more than Ethernet. See Ethernet vs Wi-Fi.
- Improve the Wi-Fi link if a cable is not possible: move closer to the router, use 5 GHz, pick a better channel. See also how to boost Wi-Fi signal.
- Check cables and ports. Intel lists a faulty Ethernet port or cable among the causes; try another port on the router and another cable. See Ethernet cable not working.
- Restart the modem and router. It clears overloaded memory and stuck connections; see how often you should reboot your router.
- Stop congestion. Large uploads and downloads on other devices fill the line and cause drops. Pause them, or enable QoS so games and calls go first.
- Update router firmware. Outdated firmware is another cause on Intel’s list; see how to update router firmware.
- Call your provider if loss appears already at the first hop past your router, or on every device even over a cable. Ask them to check the line and signal levels; on cable internet, also check that your modem is current — see DOCSIS 3.1 vs 3.0.
If loss appears only in one game, check that game’s server status first — Intel notes that server-side problems can only be fixed by the game’s developers.
Frequently asked questions
What causes packet loss?
Weak or congested Wi-Fi, faulty cables or ports, an overloaded router, outdated firmware, a busy connection, or problems in the provider’s network or at the game server.
Is 1% packet loss bad?
It is noticeable in fast online games if it is constant. A healthy connection should show 0%; PingPlotter considers up to 2% over 10 minutes acceptable and 5% or more a likely problem.
Can Wi-Fi cause packet loss?
Yes, it is the most common cause at home. Test with a cable: if the loss disappears, the problem is your wireless link.
Does packet loss affect download speed?
Yes, but less visibly. Downloads resend missing packets, so the file arrives complete but the transfer slows down. Games and calls suffer more because they cannot wait for resends.
How do I check packet loss on my router?
Ping the router’s address 100 times from a computer. Any loss to the router itself points to Wi-Fi or a cable problem inside your home.
Sources
- How to Fix Packet Loss — Intel
- What Are Good Latency & Ping Speeds? — PingPlotter