What Is Packet Loss and How Can You Fix It?
Your internet connection doesn't send data in one continuous stream. It chops everything — a Netflix episode, a Zoom call, a headshot in Valorant — into thousands of tiny chunks called packets. So what is packet loss? It's what happens when some of those packets never arrive. They get dropped somewhere between your device and the server, and the receiving end either has to ask for them again or push on without them.
Even a tiny amount matters. A 500 Mbps connection with 2% packet loss can feel worse than a 50 Mbps connection with 0%. Voices turn robotic, games rubber-band, video freezes — while your bandwidth numbers look perfectly fine.
This guide covers how packet loss shows up, what's acceptable (spoiler: under 1%), the most common causes, and a numbered fix list that resolves the majority of cases at home. You'll also learn exactly when the problem is your ISP's fault — and what evidence to bring when you call.
What Is Packet Loss, Exactly?
Every action online — loading a page, streaming 4K, firing a shot in an online match — gets split into packets, usually around 1,500 bytes each. Each packet carries a slice of your data plus a header with the destination address and a sequence number, so the receiving server can reassemble everything in order. A single second of a video call can involve hundreds of packets.
Packet loss is the percentage of those packets that get dropped in transit. If you send 1,000 packets and 990 arrive, you have 1% packet loss. Drops can happen anywhere along the route: your Wi-Fi link, your router, your ISP's network, or a congested server on the far end.
Why loss feels different depending on the app
Most web traffic uses TCP, which detects missing packets and retransmits them. You don't see errors — you see slowness, because every retransmit costs a full round trip. Real-time apps like games and voice calls mostly use UDP, which doesn't wait for retransmits. A lost packet is simply gone, and the app has to guess: the game predicts where players moved, the call fills gaps with garbled audio. That's why ping, latency and jitter matter so much more for real-time apps than raw bandwidth does.
How Packet Loss Shows Up: The Telltale Symptoms
Packet loss has a distinct signature. If you see several of these together, loss is the likely culprit rather than slow bandwidth:
- Rubber-banding in games — you run forward, then snap back to where you were a second ago
- Robotic, underwater or clipped audio on Zoom, Teams or Discord calls
- Video calls where the other person's face freezes while their audio continues
- Downloads that crawl or stall even though a speed test shows plenty of Mbps
- Web pages that half-load, then hang on images or scripts
- Frequent disconnects from game servers or VPNs
Packet loss in games
Packet loss in games is uniquely painful because game servers run on tight tick rates — often 20 to 128 updates per second. Lose a few updates in a row and the server's view of you diverges from your screen: shots don't register, enemies teleport, and you rubber-band. Many games show a loss indicator in their network stats overlay (Fortnite, Valorant, CS2 and Overwatch 2 all have one). Even 2% loss can be the difference between playable and rage-quit, which is why serious players work to reduce ping and lag and eliminate loss before touching anything else.
Packet loss on video calls
Voice codecs can conceal a stray lost packet, but sustained loss above roughly 2% produces that classic robotic sound. Zoom's own bandwidth requirements are modest — about 3.8 Mbps for 1080p — so if your calls break up on a 100 Mbps plan, loss or jitter is almost always the reason, not speed. Our guide to internet speed for video calls and remote work breaks down what actually matters for meetings.
How Much Packet Loss Is Acceptable?
The short answer: anything under 1% is generally considered acceptable packet loss for everyday use, and 0% should be your target on a wired home connection. Real-time apps are stricter — for competitive gaming and important calls, you want 0.5% or less. Here's how different levels actually feel:
| Packet loss | What you'll notice | Verdict |
|---|---|---|
| 0% | Nothing — everything works as intended | Perfect (target for wired) |
| 0.1–1% | Rare hiccups; TCP hides most of it | Acceptable for most uses |
| 1–2.5% | Occasional stutter in games, brief audio artifacts | Borderline — investigate |
| 2.5–5% | Rubber-banding, robotic audio, frozen video | Problem — fix it now |
| Over 5% | Real-time apps barely usable, frequent disconnects | Severe — likely hardware or ISP fault |
One caveat: a single loss reading means little. Wi-Fi can drop a burst of packets when a microwave runs, then behave for an hour. Always measure over at least 50–100 pings, and at different times of day, before drawing conclusions.
The Most Common Causes of Packet Loss
Nearly all home packet loss traces back to one of six causes. In rough order of likelihood:
1. Wi-Fi interference and weak signal
The number-one cause of packet loss at home. Walls, distance, microwave ovens, baby monitors, Bluetooth devices and your neighbors' networks all corrupt Wi-Fi frames, which get dropped. If loss disappears when you plug in a cable, your radio link is the problem — our Wi-Fi vs Ethernet comparison shows how big that gap can be.
2. Network congestion
When a link carries more traffic than it can handle, routers queue packets — and when queues overflow, they drop the excess by design. This happens on your own network (four people streaming while you game) and on your ISP's network during the 7–11 p.m. peak. Congestion-driven loss follows a schedule; hardware faults don't.
3. Faulty cables and connectors
A kinked Ethernet cable, corroded coax connector or chewed outdoor line corrupts data at the physical layer. Corrupted frames fail their checksum and get discarded — pure packet loss. Old Cat5 cable running near power lines is a classic offender.
4. Overloaded or aging hardware
Routers are small computers. A cheap or 6-year-old model can max out its CPU under load and silently drop packets, especially with many devices connected. Overheating makes it worse — routers stuffed in closed cabinets are repeat offenders.
5. Outdated drivers and firmware
A buggy network adapter (NIC) driver or old router firmware can mishandle packets under load. Firmware updates also patch security holes, so keeping your router current protects you twice over.
6. ISP or backbone problems
Damaged street cabling, saturated nodes (common on cable internet), or faults deeper in the network cause loss you can't fix yourself. The giveaway: loss persists on a wired connection, with your own gear ruled out, across multiple servers.
How to Test Packet Loss
Wondering how to test packet loss without special tools? Your computer already has everything you need. Start with a baseline: run a free speed test with SpeedIQ to check your download, upload, ping and jitter — high jitter alongside your symptoms is a strong hint that packets are being dropped or delayed. Then measure loss directly:
- Open Terminal (Mac) or Command Prompt (Windows).
- Ping a reliable server 100 times: on Windows type `ping -n 100 8.8.8.8`, on Mac/Linux type `ping -c 100 8.8.8.8`.
- Read the summary line — it reports loss directly, e.g. "100 packets transmitted, 98 received, 2% packet loss."
- Now ping your own router the same way (usually 192.168.1.1 or 192.168.0.1). Loss here means the problem is inside your home — almost always Wi-Fi.
- For a hop-by-hop view, run `pathping 8.8.8.8` on Windows or use an MTR tool on Mac. The first hop showing sustained loss tells you where the drops begin.
- Repeat the test wired, then on Wi-Fi, and at different times of day. Log the results — you'll want them if you end up calling your ISP.
Gamers get a shortcut: enable your game's network overlay and watch the loss counter during a match. It measures the exact route to the game server, which is the path you actually care about.
The Packet Loss Fix List: 10 Steps in Order
Work through these in order — each step is a packet loss fix for a specific cause, sequenced from most to least likely. Re-run your ping test after each one so you know exactly what solved it.
- Restart your router and modem. Unplug both for 60 seconds. This clears memory leaks and overflowing buffers — it genuinely fixes a surprising share of cases.
- Plug in Ethernet. If loss drops to 0% on a cable, you've confirmed a Wi-Fi problem and can stop chasing ghosts. Use the cable permanently for gaming and work calls if you can.
- Check and reseat every cable. Look for kinks, crushed runs under furniture, loose coax connectors and bent Ethernet clips. Replace anything older than Cat5e or visibly damaged — a new cable costs less than a takeout meal.
- Move closer or move the router. Get the router out of the cabinet, up high, and central. Every wall between you and it raises the error rate.
- Switch Wi-Fi bands and channels. Use 5 GHz (or 6 GHz on Wi-Fi 6E/7) instead of the crowded 2.4 GHz band, and pick a quiet channel in your router settings if it doesn't auto-select.
- Update router firmware and NIC drivers. Grab firmware from the router's admin page and network drivers from your PC or adapter maker's site. This fixes bugs and closes security holes in one move.
- Kill the bandwidth hogs. Pause cloud backups, torrents and 4K streams on other devices, or enable QoS on your router to prioritize game and call traffic so bursts of congestion stop overflowing the queue.
- Toggle your VPN. VPNs add hops that can introduce loss — test without one. Occasionally the reverse is true: if your ISP has a bad route to a game server, a VPN can route around it.
- Check for overheating and overload. If the router is hot to the touch or chokes when 15+ devices connect, give it airflow — and if it's more than 5 years old, replacement is often the real fix.
- Test at off-peak hours. If loss vanishes at 7 a.m. but returns every evening, you're looking at congestion — either upgrade your plan, or hand the evidence to your ISP.
Still seeing loss after all ten? The problem is beyond your equipment. Time to escalate. And if slow speeds accompany the loss, cross-check our guide to why your internet is slow — the causes overlap more than you'd think.
When to Call Your ISP (and What to Say)
Call your provider when you can show sustained loss above 1% on a wired connection, at multiple times of day, with your router rebooted and cables checked. That combination rules out everything on your side.
Bring specifics: your ping logs ("2–4% loss to 8.8.8.8 over 100 pings, wired, tested at 9 a.m. and 9 p.m."), a pathping or MTR readout showing which hop the loss starts at, and SpeedIQ results showing your ping and jitter history. Concrete numbers get you past the reboot-your-router script and escalated to a line test or technician visit. If your ISP won't act on documented, persistent problems, the FCC's consumer complaint center is the formal next step for US users.
Bandwidth is how much data your connection can move. Packet loss is how much of it actually arrives. A fast connection that drops packets isn't fast — it's just expensive.
The Bottom Line: What Is Packet Loss and Why It's Worth Fixing
So, what is packet loss? It's the silent connection killer — the percentage of your data that never arrives, forcing retransmits that slow downloads and gaps that wreck games and calls. Keep it under 1% (ideally 0% on a wire), and remember that the usual suspects are Wi-Fi interference, congestion, bad cables and tired routers, in roughly that order.
Diagnose before you fix: ping your router, then the internet, wired and wireless, and let the numbers point at the culprit. Most fixes cost nothing but ten minutes. Start with a baseline right now — test your connection free with SpeedIQ to see your ping and jitter in seconds, then work the fix list until your ping summary reads "0% packet loss." For the broader picture of what your numbers mean, our ultimate guide to internet speed testing covers everything else worth measuring.
Frequently asked questions
What is packet loss in simple terms?
Everything you do online is split into small chunks of data called packets. Packet loss means some of those packets never reach their destination — they're dropped by Wi-Fi interference, congested equipment or faulty cables. The result is lag spikes in games, robotic audio on calls and slow downloads, even when your internet plan is fast.
What is an acceptable packet loss percentage?
Under 1% is acceptable for general browsing and streaming, and 0% should be the norm on a wired connection. For online gaming and video calls, aim for 0.5% or less — real-time apps can't retransmit lost data, so even small amounts cause rubber-banding and garbled audio. Anything above 2.5% needs fixing.
Can I have packet loss with fast internet?
Yes, and it's common. Bandwidth and packet loss are independent: a 500 Mbps plan can suffer 3% loss from a bad cable or Wi-Fi interference, while a 50 Mbps DSL line runs at 0%. That's why a connection can pass a download speed test yet still stutter in games and break up on Zoom calls.
How do I test for packet loss on Windows or Mac?
Open Command Prompt or Terminal and ping a server 100 times: "ping -n 100 8.8.8.8" on Windows, "ping -c 100 8.8.8.8" on Mac. The summary line shows your loss percentage. Ping your router's address too — loss there means a home Wi-Fi problem. Use pathping or MTR to find which network hop drops the packets.
Why do I get packet loss only in games?
Games use UDP, which never retransmits lost packets, so loss that web browsing quietly absorbs becomes visible rubber-banding and hit-registration problems. The route to your game server also differs from the route a speed test uses — a congested hop along that specific path can cause in-game loss. Check your game's network overlay to confirm.
Does Wi-Fi cause packet loss?
Wi-Fi is the most common cause of packet loss at home. Distance, walls, microwave ovens and overlapping neighbor networks corrupt wireless frames, which get discarded. Test the same ping over Ethernet: if loss drops to 0% on the cable, your wireless link is the problem. Switching to 5 GHz or moving the router usually helps.
Can a VPN fix packet loss?
Sometimes. If your ISP routes traffic to a specific server through a congested or faulty path, a VPN can force a cleaner route and reduce loss. More often, though, a VPN adds an extra hop and slight overhead that makes loss worse. Test with the VPN on and off over 100 pings and keep whichever performs better.
Is packet loss my ISP's fault?
It is if loss persists on a wired connection after you've rebooted your router, checked cables and ruled out your own equipment. Congestion in your provider's network — especially on cable internet during evening hours — and damaged street wiring are ISP-side faults. Bring logged ping results from several days when you call; documented numbers get faster escalation.
