The method

Wi-Fi symptoms feel maddening because 'my Wi-Fi is broken' is always a compressed guess covering up to five unrelated causes. The playbook order exists: the first five minutes of checking save the next five hours of random fixes. Work down; the moment a test splits your problem in two, follow only the half that's yours.

  1. Q1: Which hop is broken — Wi-Fi or the internet?On the troubled device, check the router's admin page shows a live WAN/IP (cable/fiber/DSL status 'online'). Or simplest: another device on the same Wi-Fi working fine = Wi-Fi's fine, the device is yours. All devices dead but router lights normal = reboot the router once, and if still down, it's the ISP — stop optimizing and call them.
  2. Q2: One device or every device?One device in every location (phone bad at home and at the office) is a device problem: forget & rejoin, restart, 'Reset network settings' (iPhone/Android guides), update the OS. Router-side settings can't fix a broken NIC driver.
  3. Q3: One location or everywhere?Everywhere-slow but the room with the router is fast = range/obstruction: placement, then band choice, then the mesh/access-point conversation (Optimize guide). Everywhere-slow including next to the router, but fast on Ethernet = the router's Wi-Fi radios or a congested channel: reboot, retest channels with the planner, firmware update, factory reset as the last router-level move.
  4. Q4: Constantly bad, or randomly bad?Random blinks and lag spikes (calls freezing, games rubber-banding) point at interference or channel churn: is 2.4 GHz full of neighbors? Is the auto-channel hunting every hour (some routers do; pin it manually)? Near an airport/weather radar on a DFS channel? Microwave, baby monitor, or a neighbor actively mining the building's 2.4 GHz? Constantly bad at the same level is capacity or the line — retest at midnight to feel the difference.
  5. Q5: What do the numbers say?Now you can measure with a purpose — the speed test below (and the numbers under it). If the signal in the problem room is weak…

Reading the numbers honestly

Android: Settings → Internet → (gear) on your network shows the link speed — the radio's real-time negotiation with the router. iPhone: no link readout, so measure throughput instead (a LAN speed test app against a local server, or a big file transfer to a NAS/PC on the same Wi-Fi is the honest version). Windows: `netsh wlan show interfaces` for both RSSI and link speed — the best free tool most people already own.

RSSI (signal)QualityWhat to expect
-50 dBm or closer to 0ExcellentSame-room. Top negotiated speed for the device.
-50 to -65GoodThe 'normal' house range. Streaming, calls, and gaming fine.
-65 to -75Workable, thin iceThroughput roughly halves per 5 dB past a point; video calls start choosing lower quality.
-75 to -85Technically connectedHeavy packet loss and lag; anything latency-sensitive is a coin flip.
below -85Disconnected-in-all-but-nameYou will see bars; you shouldn't trust them. This is the number that ends debates.

The other number is link speed vs. real throughput. A 1200 Mbps link rating moving a 300 Mbps internet plan at full tilt is a healthy network — radio ratings are shared, half-duplex best-cases. Judge Wi-Fi against the same device at the same spot over time, not against the number on the box. And for anything time-sensitive, the latency and jitter at the far point matters more than the download number: a 15 ms ping is a good network at any bar count; 200 ms under load is a bad one at full bars.

The dead-zone decision

Once you know the far room simply has weak signal, stop tuning — the physics is done answering. The ladder from cheapest to best: (1) relocate the router / reorient antennas and verify with readings; (2) move use closer, add a chair, change who sits where (free, underrated); (3) run a cable to that room, or reuse the old router as an access point (see the Upgrade guide); (4) a mesh node, ideally with a wireless 6 GHz backhaul or wired to the modem; (5) powerline (G.hn AV devices have matured — decent on a single-phase house with real sockets, not the extension-lead hell), or MoCA if you have coax; (6) extenders only if literally nothing else can physically happen, and expect half. The only permanent fix is more access points; everything else is negotiation with the medium.

Router-level last resorts

  • Factory reset and set up fresh — config drift and half-applied updates fix more than they should. Re-enter the same SSID+password and devices rejoin untouched.
  • Firmware reinstall or downgrade if this release correlates with the problem's start — a known-bad update is common enough that vendors keep old ones posted.
  • Try another radio's auto-channel (both bands) manually rather than trusting the picker after a big neighbor shift.
  • A USB Wi-Fi adapter or new phone as an experiment — isolating 'is it the device's radio?' sometimes saves buying a whole mesh kit for one laptop.
  • If the device is old and the answers are mixed: 802.11n-only client + a 2026 router is allowed to be awkward (old WPA quirk, old roaming logic). The honest fix may be that one device's 2.4 GHz-only life is the problem.
Before you 'test' anything, rule out the planundefined

Questions people actually ask

I've done every setting change and nothing works. Now what?

At this point the evidence points to hardware or the medium: a failing router radio (rebooting often more than usual, hot to the dead-touch, 2.4 GHz mysteriously useless while 5 works), a damaged coax/fiber drop upstream, or a neighborhood that has changed entirely. Borrow or buy a cheap known-good replacement router to A/B for a day — the one-variable test no setting menu can do.

Does my neighbor's Wi-Fi really slow mine?

Yes, measurably — Wi-Fi is shared spectrum and CSMA etiquette means your router literally waits out busy air. On 2.4 GHz in a dense building, a crowded channel is often the entire story. 5/6 GHz are where a modern router earns their space.

The internet died but the Wi-Fi stayed 'connected' — which box is at fault?

The router usually keeps broadcasting while its WAN is down, so 'connected, no internet' is accurate and not a lie: start at the ISP status, then the cable/fiber handoff, then reboot modem + router in that order.

Verified sources & further reading

External links below were live-checked in September 2026. They back up the specific claims on this page; open them and judge for yourself.

  1. IEEE 802.11 — the standard that defines the behaviour you are testingieee802.org
  2. Dynamic Frequency Selection — channel vacating on radaren.wikipedia.org
  3. ALOHAnet — why shared media gets slower with loaden.wikipedia.org