WiFi Roaming Explained: How Devices Switch Between Access Points and How to Improve It

If you’ve ever walked from your living room to your bedroom and had a video call drop, or noticed your phone showing one bar of WiFi while standing directly under an access point, you’ve experienced a roaming problem. WiFi roaming — the process by which a client device transitions from one access point (AP) to another — sounds simple but involves a surprisingly complex negotiation between your device, your router, and any mesh nodes or APs on the network. Understanding how it works is the first step to eliminating the dead zones and slowdowns that roaming failures cause.

Why Roaming Is Harder Than It Sounds

Unlike cellular networks, where towers actively hand off your connection as you move, WiFi puts the client device in charge of roaming decisions. Your phone or laptop decides when to leave one AP and join another — the AP you’re currently connected to cannot simply force a disconnect. This design means roaming behavior varies enormously across device types, operating systems, and firmware versions. Two phones standing in the same spot may make entirely different roaming decisions based on their individual algorithms.

The core metric devices use is RSSI (Received Signal Strength Indicator) — a measure of how strongly the current AP’s signal is received, expressed in negative decibels (dBm). RSSI closer to 0 is stronger; closer to −100 is weaker. Most devices begin scanning for a better AP somewhere between −65 and −75 dBm, and will roam when a nearby AP offers a signal that is meaningfully stronger than the current connection.

The Three Roaming Protocols: 802.11k, 802.11v, and 802.11r

Three amendments to the 802.11 WiFi standard were designed specifically to make roaming faster and smarter. Together, they form the foundation of seamless roaming on modern mesh systems and enterprise networks.

802.11k — Radio Resource Measurement

802.11k gives your device a “neighbor report” — a list of nearby access points, their channels, and signal quality — provided by the AP you’re currently connected to. Without 802.11k, your device must scan every WiFi channel on its own to discover neighboring APs, a process that takes several hundred milliseconds and temporarily interrupts your connection. With 802.11k, your device already knows where the neighboring APs are and can roam to them with minimal scanning delay. This is particularly important for real-time applications like voice and video calls, where even a 300–500 ms interruption is noticeable.

802.11v — BSS Transition Management

802.11v flips the roaming dynamic by allowing the network to suggest that a client should roam to a different AP. Rather than passively waiting for the device to decide it should move, an 802.11v-capable AP can send a BSS Transition Management request — essentially a polite nudge — to a client that is getting a weak signal or consuming too much airtime at a low data rate. The client can accept or decline the suggestion, but most modern devices honor it. This is the mechanism mesh systems use to actively load-balance devices across nodes rather than letting them all pile onto the nearest one.

802.11r — Fast BSS Transition

802.11r solves the authentication delay that occurs during a roam. On a standard WiFi network secured with WPA2 or WPA3, every time a device switches to a new AP, it must complete a full four-way authentication handshake — a process that can take 200–500 ms. For voice calls or online gaming, that gap causes a noticeable stutter or packet loss. 802.11r pre-caches the security keys across all APs in the same “mobility domain,” reducing the reassociation to a two-step handshake that completes in under 50 ms. Most users describe the result as instantaneous — a phone call that continues uninterrupted as you walk room to room.

The Sticky Client Problem

The most common roaming failure is the sticky client: a device that refuses to leave a distant, weak AP even when a closer, stronger one is available. Because WiFi roaming is client-controlled, a device can technically stay connected to its original AP indefinitely — even if the signal has degraded to −85 dBm and the connection is barely functional — as long as it can still transmit and receive frames.

Sticky clients are more than a personal inconvenience. Because WiFi is a shared medium, a sticky client operating at a weak signal must use slower modulation rates and retransmit more frames, consuming channel airtime that blocks every other device on the same AP. A single sticky laptop in the far corner of a house can measurably slow down every other device on that access point.

Some routers and APs address this with a minimum RSSI threshold setting — if a connected client’s signal drops below a set value (commonly −70 to −76 dBm), the AP sends a de-authentication frame, forcing the device to reconnect. It will typically reconnect to whichever AP it now sees most strongly. This is a blunt tool but an effective one for stubborn clients that don’t honor 802.11v suggestions.

How Mesh Systems Handle Roaming

Purpose-built mesh systems — like Eero, Google Nest WiFi Pro, TP-Link Deco, and ASUS ZenWiFi — are specifically engineered around roaming. They use a single SSID across all nodes, share security keys between nodes automatically (effectively implementing 802.11r), and run proprietary steering algorithms on top of 802.11k and 802.11v. The result is significantly better roaming behavior than a traditional router-plus-extender setup, where each device broadcasts a different SSID (or the same SSID but without coordinated key sharing) and the client must handle everything on its own.

Wired backhaul between mesh nodes makes roaming more reliable because it eliminates the wireless backhaul congestion that can make one node temporarily appear weaker to the network. Our guide on wired vs wireless mesh backhaul explains the difference and when it matters most.

How to Improve Roaming on Your Home Network

Whether you’re running a mesh system or a router-plus-access-point setup, these steps make a measurable difference:

• Use a single SSID and password across all APs. Devices only roam seamlessly between APs that share the same network name. Separate SSIDs (e.g., “Home” and “Home_5GHz”) require the device to manually disconnect and reconnect, which is not roaming — it’s a cold join.
• Enable 802.11k, 802.11v, and 802.11r in your router or AP admin panel. Most modern routers expose these under “Advanced Wireless,” “Fast Roaming,” or “BSS Transition.” Note that 802.11r can cause connection issues with older IoT devices and some printers — if a device won’t connect after enabling it, toggle 802.11r off and test again.
• Set a minimum RSSI threshold if your router supports it. −70 to −72 dBm is a reasonable starting point that disconnects weak clients without aggressively kicking devices that are simply a room away.
• Place access points strategically. Each AP’s coverage should overlap with its neighbors by about 15–20% — enough for the client to see the next AP at a usable signal level before the current one degrades. Too far apart creates a dead zone between APs; too close causes unnecessary competition. Our mesh node placement guide covers the geometry in detail.
• Use wired backhaul where possible. A mesh node connected via Ethernet has consistently lower latency and higher throughput on its backhaul link, making it a more attractive roaming target for the network’s steering algorithm.

Roaming Behavior by Device Type

Not all clients roam equally. Apple devices (iPhone, iPad, Mac) are generally considered among the most aggressive and well-behaved roaming clients — they honor 802.11v suggestions reliably and implement 802.11k scanning. Android roaming behavior varies significantly by manufacturer and chipset; Google Pixel devices tend to roam well, while some older budget Android phones are notoriously sticky. Windows laptops depend heavily on the WiFi adapter driver — Intel adapters running current drivers roam reliably, but older adapters or out-of-date drivers can behave poorly. IoT devices (smart plugs, cameras, thermostats) are almost universally sticky and often 2.4 GHz-only, making RSSI threshold enforcement on the 2.4 GHz band counterproductive if it kicks IoT devices that can’t reconnect reliably.

The Bottom Line

Good WiFi roaming requires three things: a network that speaks 802.11k/v/r, APs placed with appropriate coverage overlap, and client devices willing to move when the signal warrants it. Mesh systems handle most of this automatically. On a traditional multi-AP setup, enabling the roaming protocols in your router’s admin panel and setting a minimum RSSI threshold resolves the majority of sticky-client complaints. If you still experience drops after optimizing the network side, check your device’s WiFi adapter drivers — an outdated driver is often the real culprit. Run a speed test before and after making changes to verify the improvement is real.