What Is Packet Loss? Causes, Detection, and Fixes

What Is Packet Loss?

Packet loss occurs when one or more data packets traveling across a network fail to reach their destination. The internet transmits all data — web pages, video streams, game state, voice calls — as discrete packets. If any of these packets are dropped in transit, the receiving end either receives incomplete data or must request retransmission.

Packet loss is expressed as a percentage. A loss rate of 1% means one in every 100 packets doesn't arrive. While that sounds minor, the effects on real-time applications are disproportionate:

• Web browsing — minor 1–2% loss is mostly invisible; TCP retransmits automatically
• Video streaming — buffering masks most packet loss, but high loss causes visible quality degradation
• Online gaming — even 1–2% loss causes rubberbanding, lag spikes, and disconnects
• VoIP / video calls — 1% loss causes audio gaps; 5%+ makes calls unusable

Use a ping test to detect packet loss — most ping tools report what percentage of packets received no response.

What Causes Packet Loss?

Packet loss has several distinct causes, each pointing to different solutions:

• Network congestion — the most common cause. When a router or link receives more traffic than it can handle, it drops packets from its queue. This is intentional behavior designed to signal TCP to slow down (the basis of TCP congestion control).
• Faulty hardware — damaged network cables, failing network cards, defective switch ports, or a deteriorating modem can cause electrical errors that corrupt or drop packets. Check your modem's event log for "T3" and "T4" timeout errors.
• WiFi interference and signal degradation — wireless packets that fail checksum validation are silently dropped. This is a major cause of packet loss on WiFi, especially on 2.4 GHz in dense environments.
• Software bugs and misconfigured firewalls — firewall rules that accidentally drop legitimate traffic, or buggy NIC drivers, can cause application-layer packet loss.
• ISP infrastructure issues — failing equipment in your ISP's network, peering disputes, or overloaded transit links cause loss that you have no control over.
• Rate limiting — some ISPs throttle or even drop packets from specific applications (peer-to-peer, streaming) as a traffic management policy.

How to Detect Packet Loss

Several tools let you measure and locate packet loss:

Ping with loss statistics:

# Windows: send 50 packets
ping -n 50 google.com

# Linux/Mac: send 50 packets
ping -c 50 google.com

# Look for: "X packets transmitted, Y received, Z% packet loss"

MTR for continuous monitoring and per-hop loss:

mtr --report --report-cycles 100 google.com

MTR is the gold standard for packet loss diagnosis. It shows loss at each individual hop, letting you pinpoint whether loss originates on your local network, within your ISP, at a peering point, or near the destination.

Pathping (Windows):

pathping -n -q 50 google.com

Remember: loss that appears at one hop but not subsequent hops usually means ICMP rate limiting, not real loss. Real loss appears at the problem hop and all hops beyond it. Combine results with a traceroute to get the full picture.

Fixing Packet Loss on Your Local Network

If you've confirmed loss is occurring on your local network (first 1–3 hops of traceroute), work through these solutions:

• Replace or reseat network cables — Cat5e and Cat6 cables can develop internal breaks that aren't visible externally. Try a new cable between your computer and router.
• Switch from WiFi to Ethernet — eliminates all wireless-related loss instantly. This is the definitive test to isolate whether your loss is wireless-related.
• Update network adapter drivers — outdated or buggy NIC drivers are a surprisingly common cause of loss on Windows. Download drivers directly from the manufacturer's website, not Windows Update.
• Check modem signal levels — log into your cable modem's admin interface (usually at 192.168.100.1) and check downstream power levels and signal-to-noise ratios. Levels outside the acceptable range cause uncorrectable errors and packet loss.
• Replace aging hardware — home routers and modems typically degrade after 3–5 years. A failing device may work intermittently but drop packets under load.

Fixing ISP-Level Packet Loss

When loss is traced to hops within your ISP's network, you have fewer direct controls but several escalation options:

First, collect evidence. Run MTR reports with 100+ cycles at different times of day (especially during peak evening hours). Save the output with timestamps. Run tests against multiple destinations (Google, Cloudflare, your game server) to confirm the pattern.

Contact your ISP's technical support line (not online chat for faster escalation) and present the MTR data. Specifically, request a "line fault inspection" and ask them to check your modem's upstream signal quality. Ask for a DOCSIS signal test if you're on cable, or a DSL Sync/Attenuation report if you're on DSL/fiber-to-node.

Persistent loss at ISP peering points (the hops where your ISP hands off traffic to the broader internet) may be outside your ISP's control — especially if only certain destinations are affected. In this case, switching to a different ISP or using a VPN that routes around the congested peering point may be your best option.

Check your current IP and run the speed test repeatedly to see if loss correlates with bandwidth saturation — a sign of a congested ISP link rather than a physical fault.

Frequently Asked Questions