How do you adjust the router time when it's incorrect? If the scheduled network disconnect is not executed at midnight, it's likely that the system time has reset to zero

last Wednesday at 3 p.m., my mom called to say the WiFi at home was gone and asked if the broadband was broken. I checked remotely and saw the router was fine, except the WiFi timer switch had turned off the wireless at the right time—though I had clearly set it to turn off at 11 p.m. Checking the backend, I almost laughed in anger: the system time showed it was around 4:10 a.m. The night before, she had tripped the door in her hallway, the router lost power and restarted, and the time reset to zero. My set of "turn off WiFi at 11 PM" became "turn off at 3 PM." Then the whole family didn't use the internet all afternoon.

this incident made me turn the "router system time" upside down. Here's the conclusion: it's normal for home router to reset to zero after power outage, not a broken , but you can fix it in ten minutes. This article will explain the principle, where each brand sets the time, and which NTP server to fill in. After reading your home timer feature, you'll never run it incorrectly in the middle of the night or mess up in broad daylight again.

to clarify: the router's power outage time is zero, so it was born without a battery

the desktop powers off and then turns it on, the timing is still accurate, because the motherboard has a CR2032 button battery dedicated to powering the clock chip. Routers are different. To save costs and save space for a single battery, most household models don't even have this installed. So once the power is unplugged, the timer stops, and after the call comes in, the time starts from the factory default—some show January 1, 1970, others show a default time of four or five in the morning, but it's not the current one.

then why is the time used normally accurate? Timing is kept online for timing. After the router is connected, it regularly checks a "time server" (called an NTP server in jargon) to set its clock to the right time. Your router's regular time isn't because the meter is good, but because it's secretly checking the meter.

the timing is off, it's basically one of these three reasons:

The third method is easiest to recognize: accurate minutes and hour differences. For example, if the time difference from Beijing time is exactly eight hours, then the time zone is not set in GMT+8 East Zone 8. The first type is ignored; the second is the root cause of most people's illnesses, which will be explained in detail later.

the timing is wrong, and these four features are the ones that fail

some people think the timing is off, so be it, as long as you can get online. Normally, it's fine, but the following four functions all rely on the router's clock for eating:

First, scheduled restarts. you set it to restart at 4 a.m., and the router thought it was 12 noon, just as the whole family was happily online, suddenly the internet was cut off for over a minute. I mentioned the TP series in my post router reboot schedule, but I only briefly mentioned it at the time. This time, my mom's home model has taught me a complete lesson.

second, WiFi timer switches. was the trap I fell into this time: setting it to close at 11:00 PM and open at 6:30 AM, then after zeroing the time, the execution point drifts completely, and by 3 PM, the whole family disconnected from the internet. WiFi How to set up a timer switch The idea for treating children playing on their phones late at night is always accurate on the clock.

third, parental control. my child's tablet goes offline at 10 PM, but the wrong time turns it out at 2 AM, and I play during the day. No matter how detailed the Mercury parent's control time grid is, if the clock is wrong, it's always a blank check. I wrote the specific settings in the article restricting children's internet time .

fourth is the log timestamp. every record in the router's log has a time, the clock is inaccurate, and troubleshooting is all a mess—your phone records the internet is disconnected at 3:30 PM, but the log says 4 AM, so the number doesn't match. check the router's logs I mentioned in that post that timestamps drift, and that's the root cause.

four functions, one root cause. So if you've used any timer function at home, the system time is worth spending ten minutes getting right.

first step is always: go backstage and check the current time

don't rush to change the settings; first get diagnosed. Open 192.168.1.1 (Mercury is melogin.cn, Xiaomi is 192.168.31.1) to enter the backend. The current time is usually displayed in two places: in the corner of the homepage/system status page, or on the time settings page itself. Check it on your phone—if the time, minutes, and date all match, it's accurate.

three outcomes and three ways to go:

• time is consistent with the phone: clock is fine, the timer function isn't working, it's another reason. Don't keep stubbornly trying to get
• minutes accurate but the hour is off by several hours: the time zone is wrong, go to the time settings and change the time zone to GMT+8. Beijing
• date is incorrect (1970, or several days off): it's just power outage reset or NTP failure. Read on

by the way, don't use "good WiFi signal" as the basis for accurate timing; these two things have nothing to do with each other. My mom's house had full signal that day, but the clock was still wrong.

Where to set time for each brand: find the right place with one table

Like scheduled restarts, each brand hides this feature differently. I checked every backend I could reach:

two additions. First, Xiaomi can basically ignore this issue; the firmware synchronizes the time itself. My two Xiaomi units have never had time issues, which is one of the few things they can worry about. Second, if ASUS's time is constantly out of sync, it's usually not an NTP address issue, but rather the router misidentifying the network and thinking "no network and no time"—the official solution is to configure "network detection" in system settings to learn whether it's truly or fake disconnected. I helped a friend's RT-AX86U check this problem overnight before finally finding the official documentation.

Which server to fill in

NTP: The default one may have long been invalid

here's the key point. For machines like TP and Mercury, some of the factory-preloaded NTP servers are already outdated, with domain names stopping or servers going offline. The router repeatedly asks, but no one answers, so the timing keeps getting off. Tenda is even more typical. By default, it fills in the pool.ntp.org international public pool, but in domestic network environments, connections often fail—NTP uses UDP port 123, and some lines just don't work. When changing the address doesn't help, the problem lies with the line, not you.

so my suggestion is to switch directly to a domestic timekeeping server, pick any one of the three:

operation sequence: Go to the time settings page→ Confirm time zone, GMT+8→ NTP Server Bar, change the default address to any of the → above, and save. Most machines will have the timing accurate within a few dozen seconds after saving. If there's no activity, restart the router once. After restarting, wait two or three minutes before checking to allow time for table alignment.

here's another tip: the time settings page usually has a "Manual Sync" or "Sync Now" button. Click it. If the time is accurate immediately, it means NTP has just not reached the sync cycle before; If you hit an error or the time doesn't change, that's when NTP is not working. Change servers or check the line.

manually setting the time is only for emergencies; the root cause depends on NTP

someone wants to save trouble and just manually enters the current time when the time is wrong. It works, but remember, this is a stop-and-go sticker: the manually set time only lives in memory. Next time it trips and the power goes out, it resets to zero. You can't remember to change it every time. I replaced my mom's NTP with a ntp.aliyun.com now, and after the switch trips, it automatically resets the meter within minutes of powering on, and the timer function never misses a point.

the time prediction is completely fixed, there's only one simple trick: test the timer function you care about most overnight . My verification system uses a scheduled restart, setting a time for midnight that night. The next day, I check the timestamp in the backend log to see if the restart records match. By the way, it's done; No, come back and check NTP. After one inspection, it can be managed for years.

Finish with a complete order:

in short: the router's clock is different from the wall clock at home. No one has put a battery on it, so you have to connect to the network and check the meter. Getting NTP right at once — scheduled restarts, scheduled internet disconnections, parental control, and log review—all four benefits together.