How to Fix WiFi Packet Loss: Causes, Tests, and Solutions

WiFi packet loss causes the frustrating symptoms gamers and video callers know well: rubber-banding, choppy audio, frozen video frames, and lag spikes that appear even when your speed test looks perfectly fine. The reason is that speed and packet loss are two entirely different measurements — you can have 500 Mbps of bandwidth and still drop 5% of your packets, which completely tanks real-time applications.

This guide explains what packet loss is, how to measure it accurately, and how to fix each of the most common causes.

What Is WiFi Packet Loss?

Data sent over a network is broken into small chunks called packets. Each packet travels from sender to receiver and is reassembled at the destination. Packet loss happens when one or more of those packets never arrives. The receiving device either requests a retransmission — which adds latency — or simply discards the incomplete data, causing corruption or gaps in the stream.

Use these thresholds to evaluate your results:

• 0%: Ideal — all packets arrive intact
• Under 0.5%: Good for gaming and video calls
• 1–2.5%: Acceptable for video streaming; noticeable degradation in gaming and VoIP
• 5% and above: High packet loss — significant disruption across all real-time applications

How to Test for Packet Loss

Ping Test

The fastest way to test for packet loss is a ping test to a known reliable server. On Windows, open Command Prompt and run:

ping -n 100 8.8.8.8

On macOS or Linux, open Terminal and run:

ping -c 100 8.8.8.8

This sends 100 packets to Google’s DNS server. At the end, the output reports the percentage of packets lost. Any loss above 0% on a wired connection, or above 1% on WiFi, warrants investigation.

Traceroute: Pinpointing the Source

A traceroute reveals where in the network path packets are being dropped — the single most important diagnostic step. On Windows, run tracert 8.8.8.8. On macOS/Linux, run traceroute 8.8.8.8. If packet loss appears only at the first hop (your router’s IP address), the problem is local. If it appears several hops later, the issue is in your ISP’s infrastructure or further upstream.

Common Causes and How to Fix Them

1. WiFi Interference

Wireless interference is the most common cause of packet loss on home networks. The 2.4 GHz band is shared with microwaves, baby monitors, Bluetooth devices, and neighboring WiFi networks. When interference corrupts packets in transit, they are dropped and must be retransmitted — which shows up as packet loss and added latency.

Fix: Switch to the 5 GHz band, which has far less interference and many more available channels. If you must use 2.4 GHz, manually set the channel to 1, 6, or 11 — the only non-overlapping options. For a complete breakdown of interference sources and how to eliminate them, see our guide on WiFi interference sources.

2. Weak Signal or Distance from the Router

A device operating at the edge of WiFi range experiences high retransmission rates that register as packet loss. Signal quality, not just signal strength, determines reliable packet delivery. A device showing −70 dBm RSSI or worse will almost certainly drop packets under load, even if it shows “connected” status.

Fix: Move your device closer to the router, or add a mesh node or access point to provide reliable coverage throughout the problem area. Our router placement guide covers the positioning principles that maximize signal quality.

3. Network Congestion and Bufferbloat

When your router’s packet queue fills up — due to a slow ISP connection or too many simultaneous heavy transfers — it must drop incoming packets. This congestion-driven packet loss is called bufferbloat and is especially common on older or budget routers with inadequate queue management.

Fix: Enable QoS (Quality of Service) in your router’s admin panel to prioritize real-time traffic (gaming, video calls) over bulk transfers (cloud backups, software downloads). For severe bufferbloat, follow our guide on how to fix bufferbloat, which covers Smart Queue Management (SQM) for routers that support it.

4. Outdated Router Firmware

Router firmware bugs have caused packet loss issues across many hardware generations. Manufacturers release updates that address memory leaks, radio driver bugs, and packet queuing problems. If your router has never been updated, you may be running firmware with known performance issues.

Fix: Log into your router’s admin panel (typically at 192.168.1.1 or 192.168.0.1) and check for firmware updates under the Administration or Advanced section. Enable automatic updates if available. Our full walkthrough on how to update router firmware covers every major router brand.

5. Failing or Damaged Hardware

A faulty Ethernet cable, a degraded network card, or a router with a failing radio can all produce persistent packet loss that no software fix will resolve. This cause is easy to rule out by testing across different hardware components.

Fix: Start by swapping the Ethernet cable between your modem and router — even short cables can degrade and cause loss. Then test the same connection on a different device. If only one device experiences packet loss, the problem is likely that device’s network adapter; update its driver or test with an inexpensive USB network adapter.

6. ISP-Side Packet Loss

If your traceroute shows loss appearing at the second or third hop — beyond your router, inside your ISP’s infrastructure — the problem is outside your local network. ISP-side packet loss can stem from congestion on shared cable infrastructure, a faulty node, or ongoing maintenance work.

Fix: Document the packet loss with timestamped traceroute screenshots and contact your ISP with the output. Specify the hop number where loss begins. Many ISPs won’t proactively address congestion unless customers report it with supporting data; a technician visit or line quality test can confirm whether there is a physical issue on your drop.

Quick Fix Checklist

Work through these steps in order before escalating to your ISP:

1. Switch from 2.4 GHz to 5 GHz, or connect via Ethernet
2. Restart your router and modem (unplug for 30 seconds)
3. Update your router’s firmware
4. Enable QoS to prioritize real-time traffic
5. Run a traceroute to identify where loss is occurring
6. If loss appears after your ISP’s first hop, contact your provider with the traceroute output

Fixing packet loss almost always eliminates the lag and rubber-banding that a speed test alone won’t reveal — because for gaming, video calls, and live streaming, consistent packet delivery matters far more than raw throughput. If your ping is good but you’re still experiencing lag, see our guide on how to reduce WiFi latency for the next layer of optimizations.