What counts as wireless packet loss?
Packet loss on a Wi-Fi network can originate in two places: the wireless link itself (frames dropped between client and AP due to RF conditions) or the wired network and WAN beyond the AP (packets dropped at a switch, router, or ISP). Distinguishing these is important because the fixes are completely different. A client-to-gateway ping tests both; a client-to-AP ping (if your AP supports it) isolates the wireless hop. Most people notice packet loss as choppy video calls, dropped VoIP calls, or slow page loads.
Cause 1: High retry rate due to weak signal or interference
802.11 is a half-duplex medium — if a frame doesn't arrive correctly (wrong CRC, collision), the AP retransmits it. High retry rates are the wireless equivalent of packet loss for everything upstream of the retry mechanism, but they consume airtime while doing so, which adds latency and reduces effective throughput. High retry rates are caused by weak client signal (low SNR, distant client), RF interference disrupting frame reception, or high channel utilization causing contention. Check per-AP retry rates in your monitoring platform. Anything above 15–20% is worth investigating.
Cause 2: Channel congestion and airtime exhaustion
When a 2.4 GHz or 5 GHz channel is saturated, frames queue to transmit and some are dropped when buffers overflow. The result is packet loss that appears intermittently, correlates with high utilization periods, and affects multiple clients at once. Monitoring channel utilization over time reveals whether packet loss spikes correlate with peak-utilization periods. The fix is typically to move clients to a less congested channel or band, or to split client load across more APs.
Cause 3: Sticky client roaming failures
A sticky client that is stubbornly associated with a distant AP at a low MCS rate experiences high retries and can cause missed frames that look like packet loss. Band-steering and 802.11k/v/r (roaming assistance) help, but some clients ignore roaming hints. If you see a specific client with persistent packet loss and low SNR on a distant AP, the device may need to be physically moved or the AP coverage design may need revisiting.
Cause 4: WAN packet loss from the ISP or firewall
WAN packet loss is often mistaken for Wi-Fi packet loss. If you see packet loss on a client's internet connection but gateway ping is clean, the problem is upstream of your network. Monitor your WAN link's packet loss to a known reliable endpoint (like 8.8.8.8 and 1.1.1.1) with frequent probes over time — TekFidelityIQ's Edge Connector performs exactly this check on a configurable schedule. Sustained WAN packet loss above 1% warrants contacting your ISP.
How to fix Wi-Fi packet loss
The fix depends on the root cause. For weak signal: improve AP placement or adjust transmit power. For interference: move to 5 or 6 GHz, change channels, or identify and eliminate the source. For congestion: redistribute clients across APs and channels, enable band steering, or deploy additional APs. For sticky clients: enable 802.11k/v/r on your controller, adjust BSS transition thresholds, or increase RSSI thresholds for client association. For WAN packet loss: contact your ISP or review your firewall and router health.
Frequently Asked Questions
- What percentage of Wi-Fi packet loss is acceptable?
- For most applications, under 1% packet loss is acceptable. Above 2%, users will notice issues with video calls and VoIP. Above 5%, the network has a serious problem requiring immediate attention.
- Can packet loss be caused by a specific Wi-Fi channel?
- Yes. High channel utilization causes packet loss from airtime exhaustion. On 2.4 GHz, channels 1, 6, and 11 are the only non-overlapping channels and congestion is common in dense environments. Moving to 5 GHz or 6 GHz, which have many more non-overlapping channels, typically resolves congestion-related packet loss.
TekFidelityIQ
See Wi-Fi health monitoring in action
Launch the interactive demo or request a free Wi-Fi Health Review — no obligation, results in about 48 hours.