Diagnosing Packet Loss on a Home Network: Causes, Tests, and Fixes
Packet loss is when data your devices send never arrives and has to be sent again. A little is normal; more than a trickle shows up as choppy calls, rubber-banding in games, buffering video, and web pages that stall for no obvious reason. This guide walks through what causes packet loss on a home network, how to test for it methodically, and how to fix each root cause.
What packet loss is — and how it feels
Networks move data in small chunks called packets. When a packet is dropped in transit, the sender usually has to notice, wait, and retransmit it. That retransmission costs time, and the stall is what you actually experience. Because loss and latency are related but distinct, it helps to be clear on the vocabulary in throughput, latency, and jitter before you start; loss is its own axis of network quality.
Typical symptoms of packet loss include:
- Voice and video calls that cut out, robotize, or freeze for a beat
- Games that lag, teleport, or disconnect even though your ping looks fine
- Video that buffers repeatedly despite plenty of bandwidth
- Downloads that run slower than your plan and occasionally stall
- Web pages that hang partway and then suddenly complete
A key distinction: high latency makes everything uniformly slow, while packet loss makes things intermittently broken. If your connection is fast but erratic, loss is a prime suspect.
What causes packet loss at home
Most home packet loss comes from a handful of causes, and knowing them narrows your testing.
- Wi-Fi interference and weak signal. Overlapping neighbors, microwaves, thick walls, and distance all corrupt wireless frames, which then have to be resent. This is the single most common source in a typical home.
- A bad cable or connector. A kinked, crushed, or cheaply terminated Ethernet cable drops packets, especially at higher speeds. A marginal cable may negotiate 1 Gbps but throw errors under load.
- A failing NIC, switch port, or router. Aging hardware, an overheating switch, or a flaky port silently corrupts traffic.
- An overloaded link. When a connection is saturated, packets get dropped once buffers overflow. This overlaps with bufferbloat — the same congestion that spikes latency eventually drops packets too.
- A duplex mismatch. If one end of a link is set to full duplex and the other to half (usually from a hardcoded speed setting), you get collisions and loss that worsen with traffic.
- Problems upstream of your house. A bad line to the ISP, a failing modem, or congestion in their network can drop packets before you ever touch them.
Note: A few tenths of a percent of loss to a distant internet server is often harmless. Consistent loss to your own router, or more than roughly 1–2% to anywhere, is worth chasing down.
How to test for packet loss
1. Ping with a fixed count
Start local. Ping your router (its LAN IP, often something like 192.168.1.1) with a large count and see if any packets are lost:
- Windows:
ping -n 200 192.168.1.1 - macOS/Linux:
ping -c 200 192.168.1.1
Zero loss to your own router means your local wired path is clean. Loss here points squarely at your LAN — cable, port, NIC, or Wi-Fi. Then repeat the test to a public server such as 8.8.8.8 to check the path to the internet.
2. Trace the path with mtr or pathping
A single ping tells you whether you are losing packets, not where. Tools that test every hop along the route reveal the location:
- Windows:
pathping 8.8.8.8(give it a couple of minutes to gather statistics) - macOS/Linux:
mtr 8.8.8.8ormtr --report 8.8.8.8
Read the per-hop loss carefully. If loss first appears at a middle hop but the final destination shows none, that middle router is likely just deprioritizing pings — not a real problem. Loss that starts at a hop and continues all the way to the destination is the real thing. If the first hop (your router) already shows loss, the problem is inside your house.
3. Isolate wired versus wireless
This one test resolves a huge share of cases. Plug a laptop directly into the router with a known-good Ethernet cable and repeat the ping test. If wired is clean and Wi-Fi is lossy, your problem is wireless — signal, interference, or channel congestion. If wired also loses packets, it is a cable, port, or hardware issue. The trade-offs between the two are covered in Ethernet vs Wi-Fi speed.
Tip: Test one variable at a time. Change the cable, or the port, or the band — not all three at once — or you will fix the problem without ever learning what it was.
4. Swap and test components
Once you have localized loss to the LAN, substitute known-good parts one at a time: a different cable, a different switch port, a different device. If moving a device to another port clears the loss, the original port or its cable was the culprit.
Fixing packet loss by cause
The table below maps what you observe to the most likely cause and the first fix to try.
| Symptom / observation | Likely cause | Fix to try first |
|---|---|---|
| Loss on Wi-Fi only, worse farther from router | Weak signal / interference | Move closer, change channel/band, reposition router |
| Loss on Wi-Fi at certain times of day | Neighbor/channel congestion | Switch to 5 GHz or a clearer channel |
| Loss on one wired device only | Bad cable, connector, or port | Swap cable, try another switch/router port |
| Loss on a wired link only under heavy load | Marginal cable or duplex mismatch | Replace with a quality cable; set both ends to auto-negotiate |
| Loss across all devices, wired and wireless | Failing router/switch or upstream/ISP issue | Reboot/replace router; test straight off the modem; call ISP |
| Loss only when the connection is saturated | Congestion / bufferbloat | Enable SQM, reduce concurrent heavy traffic |
| Loss that started after changing a device setting | Hardcoded speed/duplex | Return NIC and switch port to auto-negotiate |
Wi-Fi fixes in detail
Because wireless is the most common source, start there when loss is Wi-Fi-only. Move the router out of a cabinet and away from metal and appliances, pick a less crowded channel, and prefer the 5 GHz band for nearby devices. Distance and walls matter more than raw router power. A full walkthrough lives in router placement and channels.
Cable and hardware fixes
For wired loss, the cable is the cheapest thing to rule out, so replace it first with a properly rated one — and if you are unsure which rating you need, see Ethernet cable categories. Then try a different port. Watch for a switch or router that is warm to the touch or has been running for years; heat and age cause intermittent, hard-to-reproduce loss. Reseat connectors firmly; a partially clicked-in RJ45 is a classic offender.
Congestion and duplex fixes
If loss only appears when the link is busy, treat it as congestion: enable smart queue management and stagger big transfers. If someone previously hardcoded a NIC or switch port to a fixed speed and duplex, set both ends back to auto-negotiate — a mismatch there produces loss that grows with traffic and is easy to overlook.
Warning: Before blaming your ISP, always test wired straight off the modem or router with everything else disconnected. It is easy to spend an hour chasing an internal fault that turns out to be one bad cable — or vice versa.
When it is the ISP
If pathping or mtr shows loss beginning at the first hop outside your network and continuing to the destination — and your internal wired tests are clean — the problem is upstream. Capture a few pathping reports at different times, note the times and the affected hops, and give that to your ISP. Concrete per-hop data gets a line technician dispatched far faster than "my internet is slow."
Packet loss rewards patience and a one-change-at-a-time approach. Localize it first — router, LAN, or beyond — then fix the single cause you have proven, and re-test to confirm the loss is gone rather than merely moved. Nine times out of ten at home, the answer is a cable, a Wi-Fi channel, or a tired piece of hardware.