Why restarting your router actually works (and when it doesn't)
"Have you tried turning it off and on again?" gets treated as a joke, but for routers it's legitimate engineering. A home router is a small always-on computer, typically with 128–512 MB of RAM, running for months without a break — something you'd never ask of your laptop. Restarting it isn't superstition. It's a hard reset of four specific things that quietly degrade.
What a restart actually fixes
1. Leaked memory. Router firmware is built cheaply and rarely updated. Small memory leaks — a few kilobytes that never get released — are common, and after weeks of uptime the router runs out of working memory and starts dropping or delaying traffic. A restart hands it a clean slate.
2. An overflowing connection table. Every device in your home shares one public internet address, and the router keeps a ledger (the NAT table) mapping each active connection to the right device. That table holds a few thousand entries on typical home hardware — and a modern household chews through them fast: one phone with 40 apps syncing, a smart TV, a couple of laptops, and torrenting or cloud backups can hold thousands of connections open. When the table fills, new connections silently fail or stall. Restarting empties the ledger.
3. A stale session with your provider. Your router maintains a negotiated session with your ISP's equipment — on cable (DOCSIS), it locks onto specific frequency channels; on fiber or DSL, it holds authentication and routing state. These sessions can degrade into a half-working condition where the link is technically up but performing badly. A restart forces a full renegotiation from scratch, which is why the provider's support line always asks you to do it: it genuinely re-syncs the physical link.
4. A bad Wi-Fi channel. Many routers only scan for the least congested Wi-Fi channel at boot. If your neighbor's router appeared on your channel three weeks ago, yours may have been shouting over it ever since. Restarting triggers a fresh scan — one of the reasons Wi-Fi often feels snappier after a reboot.
Why the 30 seconds matters
The classic advice is unplug, count to 30, plug back in — and the number isn't folklore:
- Capacitors keep the board alive. The electronics can hold charge for several seconds after unplugging. A 3-second off-on can leave memory contents intact — meaning you didn't actually reset anything.
- The other end needs to notice. Your provider's equipment holds session state for your line. If you reconnect before it notices the drop, you may resume the same degraded session instead of negotiating a clean one.
Also: if you have a separate modem and router, restart the modem first, let it fully sync (steady lights, usually 1–3 minutes), then start the router. Bringing the router up before the modem is ready is how you end up with "no internet" and a second round of restarts.
When restarting does nothing
A restart only fixes problems that live inside the box you're restarting. It cannot help when:
| The actual problem | What helps instead |
|---|---|
| The website itself is down or overloaded | Nothing on your end — verify it's them and wait |
| Provider outage in your area | Check their status page; report it |
| Weak Wi-Fi in parts of the home | Placement, 5 GHz, or cable — see Wi-Fi vs. ethernet |
| Your plan is simply slow | Compare speeds — see what's a good speed in 2026 |
| Router restarts help daily, then it degrades again | That's a failing or overheating router — replace it |
Run the 10-second test →
The right order of operations
- Test first. If it's the website, you're done — it's not you.
- If it's your line: restart modem and router (30 seconds, modem first).
- Re-test. Fixed? Great — and if you find yourself doing this weekly, the router itself is the suspect.
- Not fixed? Test on a cable next to the router. Still slow = call your provider, and tell them you've already power-cycled; you'll skip the first ten minutes of the script.