Packet Loss Test: What It Means and How to Fix It
What packet loss actually means, what percentage is normal vs a real problem, the most common causes, and a step-by-step way to test for it and fix it.
What packet loss actually means, what percentage is normal vs a real problem, the most common causes, and a step-by-step way to test for it and fix it.
If your video calls freeze, your voice cuts out mid-sentence, or your character rubber-bands in an online game, packet loss is one of the most likely causes — and it's easy to confuse with high ping or low bandwidth. This guide explains what it actually is, what percentage is normal, and how to track it down.
Run a free speed test in ~30 seconds, then come back and keep reading.
Use these internal tools to check your connection:
Every time you send or receive data online, it's broken into small pieces called packets. Packet loss is the percentage of those packets that never arrive — dropped somewhere along the path between your device and the server, and never retransmitted in time to matter for real-time traffic.
It's different from the other two connection-quality metrics you may already know:
| Metric | What It Measures | Effect When Bad |
|---|---|---|
| Ping / Latency | Round-trip delay | Feels "laggy" |
| Jitter | Variation in that delay | Choppy audio/video, uneven game movement |
| Packet loss | % of data that never arrives at all | Stutter, freezing, dropped calls, missing game state |
A connection can have excellent download speed and low ping, and still have real packet loss — they're measuring different failure modes.
| Rating | Packet Loss | What You'll Notice |
|---|---|---|
| Excellent | 0% – 0.1% | Unnoticeable |
| Good | 0.1% – 0.5% | Fine for browsing, streaming, most calls |
| Fair | 0.5% – 1% | Occasional stutter in calls or fast-paced games |
| Poor | 1% – 2% | Regular stutter, choppy audio, visible game lag |
| Critical | > 2–3% | Calls frequently drop, games become unplayable |
These thresholds match the packet-loss column in our ping/jitter/latency guide — use whichever one applies to your use case (competitive gaming and video calls tolerate far less than general browsing).
Unlike download/upload speed, packet loss isn't usually reported by a single quick speed test — it needs a sustained sample over time:
A one-off ping can look fine even on a connection with real intermittent loss — the problem often only shows up over 30+ seconds or during specific conditions (peak hours, uploading, Wi-Fi interference). Run our Ping Test more than once, at different times, if you suspect intermittent loss rather than a one-time blip.
| Cause | Typical Pattern |
|---|---|
| Wi-Fi interference / weak signal | Loss on Wi-Fi, none on Ethernet from the same router |
| Network congestion (peak hours) | Worse in the evening, fine at night/early morning |
| Faulty cable, connector, or splitter | Loss present even on Ethernet, often constant |
| Overloaded or outdated router | Loss increases under heavy simultaneous use |
| VPN | Loss appears/increases only when VPN is active |
| ISP routing/peering issue | Loss present on Ethernet, consistent across devices, doesn't change with your own setup |
| Priority | Action | Fixes |
|---|---|---|
| 1 | Switch to Ethernet | Wi-Fi interference-related loss |
| 2 | Restart router/modem | Temporary overload or memory issues |
| 3 | Check/replace cables and connectors | Physical-layer loss |
| 4 | Move closer to the router / change Wi-Fi channel | Weak signal or channel congestion |
| 5 | Disable VPN | Tunnel-related loss |
| 6 | Reduce number of connected devices during critical use | Router overload |
| 7 | Contact your ISP with test evidence | Loss confirmed on Ethernet, persists across troubleshooting |
If loss persists on a wired connection after these steps, it's very likely upstream of your home — that's the point to escalate to your ISP with specific test results (time of day, duration, percentage) rather than continuing to troubleshoot your own equipment.
Run a free speed test — takes about 30 seconds.