How do you set a router to restart at a timer? Five brands, five names. I spent the whole night searching for the Mercury one hidden in the "automatic cleaning" section

the old AC2100 at home was bought in 2019, and this year I figured out a pattern: after more than forty consecutive days of continuous power-up, the 5G band inevitably slows down first. Standing in front of the router to test speed, the phone dropped from about 300 Mbps to 60 or 70 Mbps, but 2.4G still held firm. Unplugging and plugging in, good, it lasts another month or so. Later, I got annoyed and thought about setting a scheduled restart for a permanent fix, but after nearly an hour of scrolling in the background, I found that the menu didn't even mention "scheduled restart."

finally realized that each brand has a different name for this feature, and some are not even in the web backend but hidden in the mobile app. This article explains the real paths of each brand, how to choose the right timing to restart, and what happens at home during that one and a half minutes of restarting.

first deciding: should you set up your router or not

Scheduled reboots are not health supplements, so not everyone needs to take them. There is only one criterion to judge: if doesn't restart for a long time, will there be noticeable lag ?

How do

check? Open 192.168.1.1 in your browser and go to the background. On the homepage or in the "System Status," there is a runtime , measured in hours. My AC2100 lasted over 900 hours when it was down, and some old machines from friends lasted over 1,000 hours before slowing down. There is no absolute red line for this number. The rule is: start paying attention after 800 hours, and only act after the lag symptoms appear. Don't just look at the numbers.

card symptoms usually look like this: sudden latency at midnight, 5G negotiation speed drops (the WiFi speed drops from 867Mbps to 1200 Mbps in the phone's WiFi details), and the new device won't connect no matter what, so you have to restart to recognize it. If your router has been using it for two or three years without ever restarting or having any issues, then there's no need to set it up—don't add drama to yourself.

when checking the backend, I glanced at the system logs. Disconnection records were concentrated in the afternoon or early morning, so you could tell if they were "tired" or "sick"—how to read logs. I previously wrote an article 192.168.1.1 on checking the logs, the idea for catching the real culprit during the early morning network disconnection.

Five Brands and Five Names: Backend Path Comparison

that's why I spent the whole night checking the backend. The same function, five brands, five names—follow this chart to find them:

three additions. First, the name "Mercury Auto-Cleanup" is the most misleading. At first, I thought it was for clearing cache logs and didn't dare to click it, but later I checked the official documentation and found out it actually restarts the game at a timer. Second, ASUS's scheduled restart requires firmware versions; older firmware doesn't even have this option in the app, so upgrade first; If you really don't have one and insist on a timer, you can only flash Merlin firmware and write a line in the planned task 0 4 * * * /sbin/reboot. Beginners should avoid this item. Third, I wrote about Xiaomi's specific operations Xiaomi router restarts at a timed time, both the Mi Home app and the 31.1 backend have screenshot-level steps, so I won't repeat them here.

Mercury backend has another easily confused feature: "Auto Cleanup" restarts the whole device, while "WiFi Timer Switch" just turns off wireless . The two functions are close together, so don't set them wrong. WiFi timer switches are used to shut off wireless devices and the router itself doesn't stop. I wrote an article about Mercury WiFi timer switch used to treat kids sneaking around with their phones late at night.

time is set to 4 a.m.—it's not just a casual phrase

let's talk about frequency: once a week is enough The purpose of a restart is to clear out runtime junk like memory fragments, NAT session tables, and device lists. A normal household load wouldn't be enough for a week; once a day is just a ritual, and it even makes the whole family disconnect from the internet once a day.

let's talk about timing. ASUS's official documentation says rebooting takes 1 to 3 minutes, and fast devices like TP and Mercury take over a minute. In this window, the entire network is disconnected. The logic for choosing 4 a.m. is simple: night owls are basically asleep, and early risers haven't gotten up yet. But if someone at home works night shifts or someone is used to gaming and stays up until 3 a.m., then move the schedule back to 5 or 6 a.m., and don't stubbornly stick to 4 o'clock.

there's another pitfall exclusive to the TP series: scheduled tasks follow the router's own system time After the router loses power, the system time may not sync successfully. It always comes by factory default. The "4 AM" you set actually runs at 12 noon, but the whole family is happily online and suddenly disconnects. Before setting up, check the current time in System Tools → Time Settings. This step takes ten seconds, saving you a troubleshooting experience.

restart that minute and a half, what will happen at home

I set my home to 4:00 a.m. every Wednesday. The morning after the first restart, the Mi Home app lined up a row of "device offline" notifications: two cameras, one speaker, standing in the list with red eyes. Startled, I clicked in and saw that all devices were actually online—that was the moment the window was rebooted and the internet disconnected. The device disconnected and reconnected, and the slow camera reconnect took two or three minutes. Mi Jia recorded this process as an offline incident and passed it on to me.

So, after setting a scheduled restart, don't panic if you see sporadic offline notifications in the first week or two. First, check the time: notification time falls just a few minutes before or after your set restart time, that's a normal phenomenon. If the offline time doesn't match the restart time, or if the device goes offline and never returns, that's the real problem. Follow the order of the Mijia device offline troubleshooting to check signal, power, and firmware.

If you have a NAS at home, pay attention: downloading and syncing tasks in the restart window will interrupt. It's fine if things like qBittorrent automatically resume uploads, but scheduled backups running may cause errors and interrupts. My approach is to move NAS backup tasks to early Friday morning, stagger the router to restart on Wednesday, and avoid disturbing each other—how to schedule scheduled tasks on the NAS machine? The approach is the same as checking NAS hard drive hibernation but the post about secretly rewriting disk processes is the same: first make a list and then stagger the schedule.

three signals that reactivate at a fixed time to address the symptoms, not the root cause

Scheduled restart is a life-prolonging experience, not a cure. If these three situations occur, restarting will only push the problem back a few days:

First, equipment is really overloaded . Dozens of smart devices hanging at home, routers with power at maxed usage, but after rebooting and two days of quiet noise, the problem resurfaced—this isn't just about memory fragments. According to the idea in article about routers with capacity, the device should be slimmed down—switch to IoT private network when needed, and replace devices where needed.

Second, fever and frequency reduction . In summer, the weak current box is around fifty degrees, the router's thermal protection is downclocked, and after a few minutes of reboot, it gets hot again. This method first addresses ventilation and cooling. I the outdated method about level 4 cooling Xiaomi router heating, and the principle applies across all brands.

third, firmware defects . If a firmware version has a memory leak, restarting will only reset the leak count, and after a few days, it will still recover. Go to the backend to see if there are any new firmware upgrades available, whether you need to enable automatic firmware upgrades. The article discussed which machines are suitable for automatic and which require manual ones. Follow that guide.

the reverse holds: if you rule out all three—even if the machine is old and firmware has stopped updating—then a scheduled restart is the best end-of-life care. Doing it once a week can last a long time. My AC2100 still survives thanks to that Wednesday nap.

Conclusion: The complete sequence from judgment to verification

to sum it up in one sentence: Scheduled restarts are a routine if set correctly; set them wrong means a weekly disconnection for the whole family. Spending ten minutes to find the right path and choose the right timing is better than anything else.