What Is Packet Loss? Causes and Impact Explained

Every time you browse a website, stream a video, or join a video call, your device breaks data into small chunks called packets and sends them across a network. Packet loss occurs when one or more of these packets don't reach their destination. The data simply vanishes in transit, often dropped by an overloaded router, corrupted by interference, or lost to congestion along the way.

In small amounts, packet loss is a background nuisance. At higher levels, it severely degrades network performance: voice calls break up, video calls freeze, online games become unplayable, and basic web browsing starts timing out. Understanding what causes it, how to detect it, and how to fix it is essential for a reliable internet connection.

How Networks Use Packets

When you load a webpage, your operating system doesn't send the entire page as a single blob of data. It splits the request and response into packets, typically 1,500 bytes each on Ethernet networks. Each packet carries a source address, destination address, sequence number, and a checksum for error detection. At the other end, the receiving device reassembles these packets in order using their sequence numbers.

If a packet is lost, what happens next depends on the protocol:

• TCP (used for web browsing, file transfers, email) detects the missing packet and requests a retransmission. This guarantees data integrity but adds latency; the connection stalls waiting for the missing piece.
• UDP (used for video calls, gaming, live streaming, VoIP) does not retransmit. Lost packets are simply gone. The application has to cope, often by interpolating missing audio frames or skipping corrupted video frames.

This is why packet loss hits real-time applications like calls and gaming far harder than file downloads.

What Causes Packet Loss?

1. Network Congestion

The most common cause. When a router or switch receives more traffic than it can forward, its buffers fill up and it starts dropping packets. This happens during peak usage hours on ISP networks, in office environments with too many devices sharing bandwidth, or on any link that's consistently running near capacity.

2. Faulty or Degraded Hardware

A failing network interface card (NIC), a worn-out Ethernet cable, a damaged SFP module, or a defective switch port can all cause intermittent packet drops. Hardware faults often produce loss that's inconsistent, appearing and disappearing without obvious pattern.

3. Wireless Interference

Wi-Fi is inherently lossy. Competing networks on the same channel, microwave ovens, Bluetooth devices, physical obstructions, and distance from the access point all increase the wireless error rate. Wi-Fi handles this at the link layer by retransmitting, but this adds latency and reduces effective throughput. At high interference levels, retransmissions fail entirely and packets are dropped.

4. Software and Driver Issues

Outdated NIC drivers, misconfigured network buffers, and operating system bugs can cause the network stack to drop packets before they ever leave the machine. This is often overlooked because users assume the problem is upstream.

5. Rate Limiting and Policing

ISPs and network administrators sometimes enforce traffic policies that deliberately discard packets exceeding a defined rate. If you're on a throttled plan or a business connection with strict QoS policies, you may see packet loss at specific traffic thresholds.

6. Routing Problems

BGP misconfigurations, routing loops, and black holes in ISP or backbone networks can cause packets to be forwarded in circles until their TTL (Time To Live) expires and they're discarded. This type of loss often affects traffic to specific destinations rather than all connections uniformly.

7. Firewall and Security Appliances

Stateful firewalls under heavy load, intrusion detection systems, and deep packet inspection appliances can drop packets when their processing capacity is exceeded. This is common in enterprise environments.

Common Symptoms by Operating System

Windows

• Video calls and Teams/Zoom sessions that freeze or drop audio
• Multiplayer games showing high ping spikes and rubber-banding
• "Limited connectivity" warnings despite an active connection
• Download speeds far below the rated connection speed
• ping showing intermittent timeouts: Request timed out
• Slow or failing Windows Update downloads that resume and stall repeatedly

macOS

• FaceTime and video calls with choppy audio or frozen video
• Wi-Fi indicator showing full bars but pages loading slowly or failing
• System Preferences → Network showing the connection as active while browsing fails
• Streaming services buffering at resolutions well below the expected quality
• SSH sessions dropping unexpectedly or hanging

Linux

• ping output with non-sequential sequence numbers or gaps between replies
• dmesg showing NIC errors: NETDEV WATCHDOG, TX timeout, or dropped RX frames
• ip -s link showing non-zero RX/TX drop or errors counters
• Intermittent TCP connection resets in application logs
• SSH multiplexing sessions showing unexpected latency spikes

Android / iOS

• Video calls on mobile data failing while signal bars appear strong
• Apps timing out on 4G/5G with adequate signal strength
• Streaming audio cutting out briefly then resuming
• Slow handoff between Wi-Fi and cellular leaving connections in a broken state

How to Detect Packet Loss

Ping

The fastest basic test. Send ICMP echo requests and watch for timeouts:

Any lines showing Request timeout or no response indicate loss. Measure loss percentage: (lost / sent) × 100.

MTR (My Traceroute)

MTR combines ping and traceroute to show per-hop loss across the entire path to a destination. It identifies exactly where in the route packets start disappearing.

A hop showing high loss but all subsequent hops showing zero loss usually means that router deprioritizes ICMP, not a real problem. Loss that persists from a hop all the way to the destination is real.

iPerf3

For UDP packet loss specifically — the kind that matters for real-time applications:

The output reports lost datagrams and loss percentage directly.

OpenPacketLoss™

Browser-based WebRTC UDP packet loss testing. Unlike ICMP-based tools, this tests actual UDP transport using the same protocol stack as video calls and real-time applications, giving a more accurate picture of what your calls and games actually experience.

OS-Level Counters

Linux:

macOS:

Windows:

How to Fix Packet Loss

Step 1: Isolate the Layer

Determine whether loss is happening on your local network, your ISP's network, or somewhere further upstream. MTR output makes this clear. Local loss (first 1–2 hops) points to your hardware or ISP connection. Loss further out is an ISP or routing issue.

Step 2: Replace Physical Infrastructure

Swap Ethernet cables. Use Cat6 or better. Replace patch cables with known-good spares. Check for bent pins on RJ45 connectors. A bad cable is an embarrassingly common cause of intermittent packet loss.

Step 3: Move to Wired

If you're on Wi-Fi, connect via Ethernet and retest. A significant improvement confirms wireless interference or signal quality as the cause. If Ethernet isn't feasible, change your Wi-Fi channel to a less congested one (use a Wi-Fi analyzer app to find it) or upgrade to a 5GHz or 6GHz band.

Step 4: Update Drivers and Firmware

Update your NIC driver, Wi-Fi adapter driver, and router firmware. On Linux, check dmesg for driver-level error messages pointing to specific hardware faults.

Step 5: Reduce Congestion

On your local network, enable QoS on your router to prioritize real-time traffic (VoIP, video calls). On a congested WAN link, the only real fix is upgrading your plan or switching ISPs.

Step 6: Contact Your ISP

If loss is traceable to the first external hop and persists across multiple test targets, open a support ticket with your ISP and include MTR output. Document loss over time; consistent evidence of loss at the ISP's equipment is usually necessary to escalate to a line fault investigation.

Step 7: Check for Overloaded Appliances

In enterprise environments, review firewall CPU and memory utilization. A firewall dropping packets under load needs either hardware upgrades or connection table tuning.

What Is an Acceptable Packet Loss Rate?

For reference, TCP throughput degrades non-linearly with packet loss. At 1% loss, throughput can drop to 10–20% of available bandwidth due to retransmission overhead and TCP's congestion control backing off.

Related Articles

Test Your Connection Now

The most accurate way to measure packet loss for real-time applications is to test with UDP — the same protocol used by video calls, VoIP, and online games. Use OpenPacketLoss™ to run a WebRTC-based UDP packet loss test directly in your browser, with no software to install.