What do the Mercury router indicator lights mean? The old and new SYS lights follow the opposite rules: disconnect the internet, check the light first, then proceed

cousin's mistake is a typical example: mistaking a "flash" for a malfunction. On the contrary, if the lights on the WAN and LAN ports flash, it means the data is moving and is a sign of health. What really worried about it was that the light that should have turned on just wouldn't turn on.

By the way, if all the lights are normal and the internet is working, but you just can't log into the melogin.cn in the background, that's a different matter. Go check the five I wrote about that won't open, and don't waste time on the lights.

the most frustrating thing is the system light: the old model flashes slowly, while the new model stay

s on. The system light is a major misjudgment area, because the old and new Mercury models have a "normal" appearance.

the old Mercury I bought in 2016, now retired and lying in a drawer, the system light flashes slowly every second, like a heartbeat—that's normal. If it stops flashing, stays on steadily, or simply shuts off, then the machine is truly in trouble.

cousin's D191G was a later cloud router, the kind that could bind MERCURY ID and manage remotely via mobile apps. The rule was the opposite: when power on, flash a few times, then stay on and still for normal . If you look at it with the old saying "flash equals being sick," you'll probably mistake a good machine for a bad one.

so before looking at the system lights, first identify which generation the machine you have and where the model is I wrote a separate . A rough way to classify things: the backend is mostly an old-style left-side tree-shaped menu, while the large icon page that appears melogin.cn is usually a new cloud router.

there's a third condition that needs to be highlighted separately: the system light flashing , which is much faster than normal heartbeat, and the network can't be accessed—this isn't a difference in old or new model rules, but a firmware issue. I'll explain how to fix it later.

disconnect from the internet, don't unplug the power immediately when you come on. Check the three-layer positioning of the lights.

The real purpose of the light is to split the home network into three segments, so you know where the problem is: the incoming cable segment (optical modem to router), router main unit, and output cable (router to computer TV). When disconnected, follow this order:

That was exactly how my cousin solved the case. He said the light kept flashing and told me to watch videos. My first question was: Is the WAN light on the modem on? He leaned in to look, but it wasn't lit. Looking at the optical modem, the LOS light is flashing red—the optical path is faulty, and it has nothing to do with the router. Later, I called 10,000 to report low light. The technician came to melt the fibers and collect the tails. The interpretation of the few lights on the light modem was from another book, so I had to study it separately.

if you follow his own 'router reboot' approach and unplug and restart, the lights stay the same—half an hour of fussing is wasted. This is the meaning of watching the lamp: the lamp is the triage desk, not the of the verdict. It tells you which section to look into, rather than directly deciding who lives or dies. Before

checking the lights, there's a prerequisite: Is the whole house disconnected, is it just one device disconnected, and is the WiFi still available? I wrote about triage in the of the offline ledger article: distinguish this first, then look at the lights; the order is correct.

the time the system light flashed quickly, I had to step three steps to save it

I had a real fight the winter before last. The main router at home was sent for repair, so I dug out the old Mercury from the drawer to cover the shift. The next night, the system light suddenly flashed from a slow flash every second to a rapid flash, and the internet disconnected.

Step one: Turn off the power and restart. After letting it rest for thirty seconds, I powered it on. The slow flash came back, and after two hours of stability, it happened again. This shows that restarting only treats the symptoms, not the root cause.

Step two: Feel the temperature and raise the firmware. The casing is warm and not hot, so overheating is ruled out first—I wrote about how to judge by feeling the casing in this article, overheating test . The Mercury series doesn't automatically upgrade. I manually flashed the last firmware package from the official website for the hardware version, and the flash interval was noticeably longer, but it still happened the next day.

third step, try desperate measures: hold the stitch needle against the reset to restore the factory, and reconfigure the broadband account. This time it was stable, and later it lasted nearly half a month until the main router returned.

experience from three steps: system light flashing is basically a matter at the system firmware layer, with the handling sequence being restart, firmware, reset, . Before resetting, remember to copy your broadband account. I wrote the rescue checklist in the of the restoration post; The firmware pitfalls with hardware versions on the official website are thoroughly explained in the upgrade article.

another truth: occasional flashes on old machines could also be a sign of aging—capacitors and flash storage are already old. I never let that old Mercury do heavy work anymore. How many years can the router last, and which signals should be retired? I've calculated in this lifespan account . If your device has a fixed number of times each week to wilt, you can set a scheduled restart. The Mercury backend is called "automatic cleaning," and set the path in this article.

the Ethernet port light shows no speed, and if the light is too bright, there's no software to switch on or off the

WAN or LAN ports. Home devices are basically monochrome and only tell you "if it's connected and if there's data," not whether you're running gigabit or 100Mbps .

some multi-port models and commercial machines have dual-color speed lights. The rule for TP-LINK commercial machines is that green equals Gigabit and orange equals HundredMbps. If you're using a single-light home setup, don't guess—there are two ways to see the truth: first, log in to the background to check the WAN connection speed—whether it's 1000Mbps or 100Mbps is obvious at a glance; Second, check the port on the optical modem's end and distinguish between gigabit and hundred-megabit ports which I have written about separately.

a quick reminder: when a gigabit port drops from a hundred Mbps, you can't tell by the lights. Four-core network cables, oxidized connectors, poor panel contacts all secretly reduce negotiation speeds to 100 Mbps, with speed tests always capped at just over 90 Mbps. I've written a thorough investigation of this as well—just focus on the numerical features.

here's a reverse question: some people aren't afraid the light won't work, but that it's too bright. Mercury's backend basically doesn't have an LED light off switch—some Xiaomi and ASUS models have it, but most Mercury don't. At night, use physical methods: cut electrical tape into 4mm wide strips, or buy indicator light blackout stickers that cost a few yuan per board, and wrap the mesh port row around them.

system lights and network port lights are two different things: system lights are managed by the firmware, so some models can turn off them by software; The Ethernet port light is directly driven by the switch chip; the software can't turn it off, so you can only stick it on. I explained the difference between these two in the of the Turn off the lights.

there's another line: the network port lights flash wildly at midnight, don't complain—they're telling you there's data running, and your home devices sync and back up at midnight are all normal. Only when it really stops flashing will it be your turn to get nervous.

Finish: If you take them out in order

disconnect from the internet, don't rush to unplug the power—just repeat this sequence:

• first distinguish whether the whole house is disconnected or a single device is still off. Check the WAN light
• Check the WAN light: if it's not on, check the fiber modem and incoming cables. Most routers are innocent
• Check the system light: the old model should blink slowly, the new model should stay on but flashes frequently. Follow the three steps: restart, firmware, and reset
• Check the LAN light: If it doesn't light up, change the network cable and port. Check which device is installed
• the light is all normal and you can't access the backend. That's a login issue, not the light

light is the triage desk. Once the three stages are clear, either you have direction to do yourself, or make your call for repairs clear—the technician will come to the door when hearing "WAN light not working, optical modem LOS flashing red" or "network is down," and the equipment they bring is different.