Router keeps needing a restart? It is telling you something
If your router has to be restarted every few days, the box is not being fussy. Here is how to read its uptime counter and tell memory, heat and power apart.
It usually starts the same way. The WiFi feels heavy on a Tuesday evening, someone says "restart the router lah", and everything is fine again for three days. Then it happens again. After a month, unplugging the box has become part of the household routine, somewhere between taking out the rubbish and paying the bill.
That is not maintenance. A router that needs a restart on a schedule is a router with a problem, and the restart is only clearing the symptom. The good news is that the box usually tells you which problem it has, if you know where to look.
The one check that splits the problem in half
Before you change anything, find out whether the router is rebooting by itself or whether you are restarting it because it slowed down. Those are two completely different faults, and almost nobody checks.
Open the router's admin page — usually 192.168.0.1 or 192.168.1.1, with the login printed on the sticker underneath the box — and look for Uptime or System Time on the status page. Uptime means "how long since this box last started".
Write down the number and the date. Check again two days later, without restarting it in between.
- Uptime kept counting (say, 2 days became 4 days): the router never crashed. You are restarting it because it got slow, so the fault is memory or CPU load.
- Uptime reset on its own (2 days became 40 minutes, and you did not unplug anything): the router rebooted itself. The fault is heat or power, and no amount of changing WiFi channels will touch it.
That single number decides whether the rest of this article is about load or about hardware. Everything below is ordered by cost, cheapest first.
What you are seeing, and what it means
| What you notice | What is probably happening | Does a restart help? |
|---|---|---|
| Fine after restart, slow again in 3–5 days | Working memory filling up under load | Yes, for days. Treat it as a clue, not a cure |
| Whole box powers off and comes back | Heat, or the power adapter failing | No. It will keep happening |
| Only 5GHz dies, 2.4GHz survives | Radio chip overloaded or overheating | Briefly. Then the same band dies again |
| Wired speed fine, WiFi slow | The WiFi part of the box, not the line | Barely. The line was never the issue |
| Drops at the same time every evening | Peak-hour load on the line, not the router | No. Test with a cable to confirm |
Cause one: memory, because nothing ever switches off
A home router has a small amount of working memory and a long list to keep: every device's address, every open connection, every app phoning home. Some of that list is never cleaned up properly. Manufacturers call it a memory leak; at home it just looks like a box that gets tired.
The giveaway is the pattern — fine, then slow, then fine again after a restart, on a roughly fixed cycle. Adding devices makes the cycle shorter. Two things help without spending anything: turn off features you do not use on the admin page (guest network, USB sharing, parental controls, remote access), and remove devices you no longer own from the list of connected clients. If the cycle is down to a day or two, the box is simply undersized for the house.
Cause two: heat, which nobody checks because the box is always warm anyway
Routers run warm. Warm is fine. Hot is not, and a router sitting in a closed cabinet, on top of an amplifier, behind a curtain, or under a stack of papers has no way to shed heat. When the chip gets too hot it protects itself by throttling, and if that is not enough, it reboots.
Touch the top of the box after it has been on for an hour. If you would not leave your hand there comfortably, move it. Also check the vents for dust — a router in a house with a cat, or near a kitchen, collects a felt-like layer that insulation does nicely.
Cause three: firmware that was never updated
Router firmware fixes the exact bugs that cause memory leaks and random reboots. Most people have never opened that page. It is free, so it belongs near the top of the list — but do it from the manufacturer's own support site, using the model number printed on the box, not a file from a download forum. Flashing the wrong firmware turns a slow router into a dead one.
The cause most people miss: the power adapter
If your uptime keeps resetting by itself, look at the little black adapter on the floor, not the router. Adapters age. The capacitors inside dry out, and under load the voltage sags just enough for the router to brown out and restart. The symptom is maddening because it looks random: fine for a week, then three reboots in an evening, usually when several devices are working hard.
Two cheap checks. Feel the adapter while the router is busy — a failing one runs noticeably hotter than the box itself. Then unplug the adapter and look for a bulge on top or a slightly domed case. A replacement adapter with the same voltage and at least the same amperage is inexpensive and often brings an old router back for another two years. Take the router's label with you when you buy it; voltage must match exactly, amperage can be higher but never lower.
What to do, in order
- Write down the uptime number so you know if it is rebooting or just tiring.
- Move the router into open air, off the floor, with nothing on top of it. Free.
- Turn off unused features and clear old devices from the client list. Free.
- Update the firmware from the manufacturer's site. Free.
- Check the power adapter for heat and bulge. Cheap to replace.
- Only then consider a new router — and if you get one, put the old box in bridge mode rather than running two routers side by side.
Restarting is not the fix. It is the box asking for help.