You're standing two feet from a router. Two feet. The signal icon shows two sad bars, your video is buffering, and the closer router is basically close enough to touch. Your phone is ignoring it completely.
The short answer: your phone decides when to switch routers, not the network. And phones are, by design, deeply conservative about that decision.
The sticky client problem
Wi-Fi devices are called "clients" in networking. The client, meaning your phone, holds onto an existing connection until the signal drops below a threshold it considers unacceptable. Routers can't force a client to leave. They can send a deauthentication frame, a kind of polite eviction notice, but whether the client respects it depends on the manufacturer and the driver.
So your phone connects to the downstairs router when you're in the kitchen. You walk upstairs. The signal weakens, but it's still technically functional, maybe a -72 dBm signal where -50 dBm would be clean and fast. Your phone does a quiet calculation: I have a working connection, switching costs me a brief interruption, I'll stay.
It is optimizing for stability, not speed. Noble intention, genuinely terrible outcome.
This is called the sticky client problem, and it's been annoying people since multi-router home networks became common.
Why the numbers matter more than the signal bars
Signal strength is measured in dBm, a logarithmic scale where bigger negative numbers mean weaker signal. The gap between -65 dBm and -80 dBm looks small on paper but represents roughly a 97% reduction in signal power. Two bars on your phone's display can mean anything from "fine" to "barely holding on," which makes the bars about as useful as a weather vane in a closed room.
Most phones won't roam to a new access point until the current signal drops below roughly -75 to -85 dBm, depending on the operating system and chipset. Some Android devices roam earlier than iPhones. Some budget chipsets barely roam at all. There's no universal standard, which is exactly why two people can buy the same mesh system and have completely different experiences.
Take Priya, who set up a three-node mesh at home and gets clean, uninterrupted handoffs on her Pixel, while her partner James, on an older iPhone SE, regularly has to toggle airplane mode to force a reconnect when moving between floors. Same network. Different clients. Two completely different afternoons.
The upstairs router, meanwhile, is sitting at -45 dBm from where you're standing. Loud and clear. Your phone doesn't care, because from its perspective, abandoning a working connection is a risk.
What actually fixes it
Modern mesh systems attack this from two angles. First, band steering nudges clients toward 5 GHz when they're close and 2.4 GHz when they're far, since 5 GHz has shorter range but higher throughput. Second, the better systems implement 802.11r, 802.11k, and 802.11v, a trio of Wi-Fi standard amendments that together make roaming faster and give access points the tools to actively suggest a client move.
802.11k lets your phone build a list of nearby access points and their signal strengths without scanning constantly. 802.11v lets an access point send a BSS Transition Management request, essentially a firm suggestion: "Hey, that other node is better for you right now, please move." It's still a suggestion. A stubborn client can refuse. But most modern phones respect it.
Then there's 802.11r, which handles the actual handoff by letting the phone pre-authenticate with the new node before fully leaving the old one, cutting the interruption from hundreds of milliseconds to nearly nothing.
What most people miss: if your setup is a single router plus a range extender bolted on as an afterthought, none of this applies to you. Extenders create a separate network, or a poorly bridged one, and your phone treats them as strangers. A true mesh system, where all nodes share the same management layer, is the only configuration where coordinated roaming is even possible. Spending money on a second extender when your roaming logic is broken is just throwing good money at a firmware problem.
Stuck on a weak signal right now? Check your Wi-Fi settings and find the signal strength reading if your OS exposes it. Below -75 dBm with another node available, toggle Wi-Fi off and on to force a fresh connection. Blunt. Works every time.
The deeper issue is that "stronger network" and "smarter client" are separate problems that the industry has never quite forced itself to solve together. Better hardware fixes the first. The second is a firmware decision baked into your phone by an engineer who prioritized not dropping your call over giving you the fastest possible connection. Reasonable trade-off, honestly. Just not the one you wanted while standing two feet from a router, watching your video buffer.