How often should you get a check-up at home online? I checked monthly, quarterly, semi-annually, and yearly, and found three hidden dangers that had been hidden for two years

last month, my cousin's NAS hard drive suddenly passed away without warning. He only found a screenshot of SMART from three years ago after digging through chat history, and was instantly stunned. After reading about his experience, I looked back at my own home: the optical modem hadn't been in the background for four years, the router configuration backup was only done the year I replaced the device, and since buying the UPS, I haven't done any power outage drills. Simply put, the network equipment at home is like a car—it's not worth checking just because it's broken, but it needs regular maintenance. Taking advantage of a weekend, I checked my home from start to finish in four cycles—monthly, quarterly, semi-annually, and yearly—and found three hidden dangers that had been hidden for two years. In this article, I will clearly explain the criteria and periodic table in one go.

be clear: the physical exam is about thunder, not illness

many people have no concept of "online health checkups" and think that normal internet speed is healthy. In fact, most faults in home networks don't happen suddenly; they accumulate gradually: light deterioration causes two or three dB of drift per year, and when it drifts to around -28, it starts dropping in the middle of the night; Capacitors wear out by a bit every year, and in three years, they'll crash in summer; If you haven't changed your password for three years, the dictionary you've been using online has already reached its eighth round. By the time you really sense something is wrong, something has probably already happened.

the approach to the checkup is simple: while it's still not bad, pick out the trend of 'deteriorating' and . So the core action isn't about revising, but about 'keeping a baseline and making comparisons.' On the day of installation, I recorded how much light degradation, how many speeds I tested, how many devices I had—I copied them all down; Whenever you take another look, the direction the numbers are heading is clear at a glance. I personally write these numbers on a piece of paper and stick them on the inside of the weak current box cover. Even after four years, I still annotate them—it's more effective than any memo.

two things I do casually each month, and together they take less than ten minutes

the principle of monthly inspections is "no fuss," just look at the details, not hands-on work. The first thing to do is log in to the router's backend homepage and quickly check the fields on the running status page: WAN port IP, running time, number of connected devices, memory usage, . If the WAN port changes from a public address starting with 100.64, the operator has cut you into the internal network, cutting off the remote return route on the spot. You wouldn't know this unless you see it. If the operating time frequently resets to zero, it means the machine is repeatedly restarting, so you need to check the power supply and heat sources.

second thing, pick a late-night rush hour (the most typical time) to measure your speed and write down the numbers. Speed testing posture is important: plug in the cable, turn off downloads and backups, and test again. specific pitfalls, I've written in this article. Keeping a monthly evening rush hour speed test is more convincing than any single speed test—my home had gigabit speeds stable around 940 last year, but dropped to 880 this year. This slow downward curve is the strongest evidence when you request repairs from your carrier.

once every quarter: equipment is heavily targeted, and I clear out seventeen zombies

The highlight of

quarterly inspections is the equipment inventory. Open the router's device list and identify each one: who is this one, who is that one? I have 62 devices at home, and I really can't remember them when I don't call names. If you can't recognize a device, don't rush to block it. Follow the three tricks identify people: check the online time pattern, check the top six MAC vendors, and use elimination to turn off each one one one by one. This time, I was called out and cleared out two zombies: the device list had a dozen long-discarded disposable devices (phones refreshed by relatives visiting, old tablets I replaced), and an even more hidden item—the static IP binding table, where the HP printer I sold in 2023 was still stuck at 192.168.31.15. This kind of entry itself is harmless, but when you manually assign this IP to a new device, you'll encounter a mysterious 'intermittent connection' glitch, and you won't find it for a long time to find it.

two small things to do during roll call: first, rename and note the devices they recognize ('Living Room TV', 'Parents' Phone'), so that next time something goes wrong, they can be quickly pinpointed at a glance; Second, turn off the guest network—the visitor WiFi was still on after a relative was away for half a month, and this happened more than once at my house.

every six months: firmware, backup, UPS discharge testing

half-year period is a hands-on event, with three things. The first item: firmware. I wrote about router firmware strategies in my article on automatic upgrades: Stable version with automatic upgrades enabled, don't mess with the optical modem's firmware yourself—wait for the carrier to implement it. Just check the version number once every six months; don't be obsessed with not seeing the new version and feel upset. I also checked the surveillance camera in the yard. I hadn't pushed firmware in three years, so for this kind of pause device, I followed the old routine: change the password, don't expose the port, and follow the list from the security self-inspection article exactly .

second item: configure backups. The router exports config.bin in the background, with one copy stored on both the computer and the cloud drive. This file is tens of KB long, and even after ten years, it doesn't take up space. But if the main router gets struck by lightning one day, the new machine can restore it to exactly the same state in ten minutes—the broadband account, WiFi password, and static binding are all inside. backup paths and several pitfalls written before, no repeats. During this checkup, I found that my backup is still two years old. After installing a new one, I didn't delete the old one: old backups are assets, and if there are issues with new configurations, you can roll them back.

third, UPS discharge test, which was the second hidden danger I identified during this checkup. I have two UPS systems at home, and the one with a NAS is 600VA. the year I bought it, I managed to practice for 47 minutes . This time, after unplugging the mains power and testing again, only 18 minutes remained—a lead-acid battery has been used for three and a half years, so this level of degradation is normal, but 18 minutes is enough for "waiting for the NAS to safely shut down," while waiting for "I'll handle it manually at home" is risky. Buy a battery of the same specification online for 115 yuan, replace it yourself, and it takes five minutes. Another small UPS with an optical modem router is in the four-hour mode and healthy. This test is really recommended: batteries are consumables, and you never know how much power they have left until you test them.

once a year: compare the light degradation bases and identify the four dB

annual inspection is the main focus; the core is light decay. The year my optical modem was built, my technician measured the received optical power at -19.2dBm, as recorded on the sticker. This time, I went to 192.168.2.1 to check—my home changed the bridge, so the backend of the optical modem needs to be set a static IP first. I wrote an article about the whole story of this step and it was -23.5. In four years, it has drifted by 4 dB, still in the healthy zone (-8 to -27), but the trend is different: at this rate, in another four or five years it will be on the line; above -28, it will be a continuous stream of errors, disconnections, and midnight disconnections.

trace the thread to find the cause, follow the old three self-check light decay: thread straightening, wiping the end, and reinserting. In the end, the culprit was found inside the weak current box—back then, when I was organizing the box, I wanted to keep it fresh, and a zip tie tied the leather cable and network cable together, forming a small right angle. Fiber optics are sensitive to bending but not pulling; if the bending radius is less than 5 centimeters, light leaks out. Cut the cable tie, coil it into a large loop, then check the light decay to return to -21.8, recovering 2 dB. The remaining degradation is natural aging of cold connectors and optical modules, so there's no choice but to record it in the baseline and keep observing.

annual inspection were manual labor: dust removal from the weak current box (the dust accumulated over four years could cover the cooling holes, so following the same set of cleaning the weak current box as done); Run the two NAS drives SMART interpret the , focusing on whether the remapping and RAW values to be mapped are zero, and how much the power-on hours have increased; A quick glance at the storage pool water level shows that over 80% of the time to plan expansion or cleaning—don't wait until it's full and then panic.

Conclusion: Stick this periodic table on the weak current box, just follow the instructions

compiled four years of medical examination experience into a single table, that's all there is to it:

my order is simple: First, make sure to fill in the 'baseline'—light decay, speed test, equipment inventory, configuration backup. These four are the benchmarks for all subsequent comparisons. Without them, the physical exam is just a random test. Then just scroll according to the periodic table. The most worthwhile of the three hidden dangers was that cable tie. It cost one pair of pliers and recovered 2 dB, so at the rate of light decay drift, it was basically two years of life for free. When it comes to network equipment, the more you pay attention to it, it saves you ten points when it goes offline at night.