How to Fix Packet Loss
Packet loss means a percentage of data packets sent across your connection never arrive at their destination. Even 1–2% packet loss causes severe problems for real-time applications: voice on calls becomes choppy, video freezes, and games stutter. This guide covers how to find and fix the source.
What packet loss actually causes
| Packet loss % | Effect on gaming | Effect on video calls | Effect on downloads |
|---|---|---|---|
| 0% | Perfect | Perfect | Full speed |
| 0.1–0.5% | Occasional stutter | Slight audio artefacts | Minor speed reduction |
| 1–2% | Noticeable lag, rubber-banding | Choppy audio and video | Moderate speed reduction |
| 3–5% | Severe lag, game barely playable | Frequent freezes | Significant TCP retransmissions |
| Above 5% | Unplayable | Call drops or unusable | Very slow; connection may fail |
Step 1: Locate where the packet loss is occurring
Packet loss can occur at any point between your device and the destination server. You need to isolate which hop is responsible:
- Run a traceroute with continuous ping. On Windows:
pathping 8.8.8.8or use WinMTR. On macOS/Linux:mtr 8.8.8.8. These tools show packet loss at each hop separately. - Interpret the results: Packet loss only at an intermediate hop, with zero loss at the final destination, is typically router ICMP rate limiting (not a real problem). Packet loss that appears at a hop and persists to the destination indicates actual loss.
- Identify the hop: If the first hop (your router) shows packet loss, the problem is between your device and router. If it's the second or third hop (your ISP's infrastructure), that's an ISP line problem.
Step 2: Diagnose by connection type
If packet loss is on Wi-Fi
Run the same test while connected via Ethernet. If packet loss disappears on Ethernet, the problem is Wi-Fi-related:
- Radio interference from 2.4 GHz band - switch to 5 GHz
- Weak signal - Move closer to the router or add a mesh node
- Overloaded Wi-Fi channel from neighbouring networks - Change channel to a less congested one
- Wi-Fi driver issue on your device - Update Wi-Fi driver
If packet loss persists on Ethernet
Connect your computer directly to the modem, bypassing the router entirely. If packet loss stops, your router is the problem - Update firmware, check for overheating, or consider replacement. If packet loss persists when connected directly to the modem, the problem is the ISP line. Modem vs router - What each device does →
ISP line packet loss
On cable connections, line noise causes corrupted packets which the modem discards. On DSL, line attenuation and noise cause the same. Contact your ISP with your traceroute/MTR results showing loss at their first hop. They can run a remote line quality test and check signal levels at your premises. Request an engineer visit if remote tests show abnormal levels.
Causes specific to cable (DOCSIS) connections
Cable internet is shared infrastructure - Your coaxial cable connects to a node shared with many neighbours. Causes of packet loss on cable:
- Cable/splitter quality: Cheap or corroded splitters between your cable entry point and modem introduce noise. Remove unnecessary splitters; replace any corroded ones
- Cable condition: Damaged or ageing coaxial cable, especially at outdoor connections, introduces noise. Inspect accessible cable runs
- Node congestion: During peak hours, a heavily loaded cable node can cause packet loss. This is an ISP infrastructure issue, not fixable at home - See ISP congestion guide
- Modem upstream power: Check your modem's admin page for upstream power level and signal-to-noise ratio. Upstream power should be between 38–48 dBmV; SNR above 33 dB. Values outside these ranges indicate line problems
Packet loss from the game server side
Not all packet loss is on your connection. Game servers can also be overloaded or have intermittent issues. To distinguish between connection-side and server-side loss:
- Test with a different game server or region - If loss disappears with a different server, the issue is on the server side or the routing to that specific server
- Check the game's status page or community forums - Widespread reports of packet loss to a specific server indicate a server-side issue
- Use the game's built-in network diagnostics if available (many FPS games show packet loss in the HUD)
Fixing packet loss: priority order
- Switch from Wi-Fi to Ethernet - Eliminates Wi-Fi packet loss entirely
- Update router firmware - Fixes software-related packet drop issues
- Remove unnecessary cable splitters on your coaxial line (cable internet)
- Move router to a central, open location with ventilation
- Contact ISP with MTR results showing loss at their infrastructure
- Request a line test and engineer visit if ISP-side loss is confirmed
See also: What is packet loss? FAQ →
How to fix packet loss
- Locate where loss occurs. Run a continuous traceroute tool such as MTR or pathping to a reliable target to see which hop is dropping packets.
- Rule out Wi-Fi. Repeat the test on Ethernet; if the loss disappears, address the wireless cause with a band change, better placement, or a driver update.
- Isolate the router. Connect the computer directly to the modem, bypassing the router; if loss stops, update the router firmware or replace the router.
- Inspect the cabling. On cable connections remove unnecessary splitters and check coaxial or phone lines for damage and corrosion that introduce noise.
- Escalate to your ISP. If loss persists straight from the modem, send your traceroute results to your ISP and request a line test and an engineer visit.
Frequently Asked Questions
Is a small amount of packet loss normal?
Occasional, momentary loss well under 0.5 percent is common and rarely noticeable for browsing or downloads, because TCP simply resends the missing data. Real-time traffic like voice and gaming is far more sensitive, where even 1 to 2 percent causes audible choppiness and rubber-banding. Persistent loss above roughly 1 percent to the destination is worth investigating.
Why does a traceroute show loss in the middle but not at the end?
Many routers deprioritize or rate-limit the ICMP replies that traceroute relies on, so an intermediate hop can display loss while still forwarding your real traffic perfectly. Loss that appears at one hop and then continues all the way to the final destination is the pattern that indicates a genuine problem. Judge by the destination, not by a single middle hop.
Can packet loss reduce my download speed even without dropping a call?
Yes, because TCP treats loss as a congestion signal and slows its sending rate each time a packet is lost, then ramps back up gradually. Even a low, steady loss rate can cap throughput well below your line speed through repeated retransmissions and backoff. This is why a connection with intermittent loss can feel slow despite a healthy plan.
Does packet loss get worse in bad weather?
On outdoor cable, DSL, and fixed-wireless connections it can, because moisture, temperature swings, and corroded outdoor fittings raise line noise that corrupts packets. Loss that reliably tracks rain or time of day points to a physical line fault rather than your home equipment. Note the pattern and give it to your ISP so they can run a line test.