What is a sticky client?
A sticky client is a wireless device that remains associated with an AP that is no longer providing the best signal, rather than roaming to a closer or better AP. As the client walks away from AP-A and toward AP-B, it should roam — but some clients stay connected to AP-A until the signal becomes nearly unusable. During this period, the client is transmitting at a low MCS rate (because of low SNR) and consuming far more airtime per byte of data than a client with good signal would. Other clients on the same AP suffer because the sticky client is hogging airtime at a low rate.
Why roaming happens too late
Roaming decisions in 802.11 are made by the client, not the AP. Each wireless device vendor implements its own roaming algorithm, and some are very conservative — they don't roam until the current connection is nearly failing. This is especially common with IoT devices, older enterprise laptops, and some Android handsets. The AP can signal to the client that a better AP is available (via BSS Transition Management, part of 802.11v), but the client can simply ignore it.
802.11k, v, and r: what they do
802.11k (Neighbor Reports) lets APs tell clients which other APs are nearby, making it faster to find a roaming target without a full scan. 802.11v (BSS Transition Management) lets APs send an explicit signal to a client asking it to roam to a specific AP. 802.11r (Fast BSS Transition) speeds up the actual roaming handoff, reducing connection interruption during the transition. For roaming to be smooth, both the AP infrastructure and the client device need to support the same features. All modern enterprise APs (Cisco Meraki, Aruba, Ruckus, Ubiquiti) support k/v/r; client support varies.
How to detect sticky clients
Signs of sticky clients include: a specific client consistently showing low SNR (below 15–20 dB) despite being in a building with good AP coverage; high retry rates on a specific client while others on the same AP have low retries; a client associated at very low data rates (6–12 Mbps) while near multiple APs. TekFidelityIQ's client monitoring tracks per-client SNR and associated AP over time, making it possible to identify specific devices that are chronically sticky and prioritize intervention.
How to fix sticky client problems
Adjust your controller's minimum RSSI threshold for association — if AP won't accept a client below -75 dBm RSSI, sticky clients will be forced to roam sooner. Enable 802.11k/v/r on your AP infrastructure and verify client support. Increase BSS transition aggressiveness settings in your controller (Meraki, Aruba, and Ruckus all expose tunable thresholds). For persistent IoT devices that can't roam, consider placing APs closer to them or dedicating an SSID with tighter coverage cells. Sometimes the fix is a coverage design problem — if there are coverage gaps between APs, clients have nowhere better to roam.
Frequently Asked Questions
- What causes sticky Wi-Fi clients?
- Sticky clients result from client-side roaming algorithms that are too conservative — the device doesn't roam until its current connection is nearly failing. IoT devices and older laptops are the most common offenders.
- Does 802.11r fix sticky client problems?
- 802.11r speeds up the roaming handoff but doesn't fix when roaming happens — that's 802.11v (BSS Transition). Together, k/v/r makes roaming faster and more directed, but a client can still ignore 802.11v transition requests.
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.