My internet dropped while I was working, and the router still showed its normal lights. I restarted the router because that is always the first advice, but the connection only came back briefly and then died again. I also checked the cables and tried another device, with the same result.
What is a restart actually supposed to fix, and what should I check next when it does not restore a stable internet connection?
A restart only clears temporary problems. It is not a repair.
Rebooting wipes the router’s short-term state and makes it rebuild its connections. That can fix a stuck DHCP lease, a full or corrupted connection table, a firmware process that stopped responding, or a failed link between the router and the modem. If you have a combined modem/router gateway, restarting it also forces a fresh connection to the ISP. Normal-looking lights only show that certain hardware links exist. They do not prove the internet connection is healthy.
Since yours came back briefly and failed again, I would check beyond the router:
Do not jump straight to a factory reset. That erases your settings and often does nothing when the fault is the modem, outside line, or ISP. If a direct wired connection drops too, record the approximate times and contact the provider. If direct modem service stays stable but the router connection fails, then the router, its power supply, firmware, or WAN cable is the likely problem.
The missing question is whether all devices lost connectivity at the same time. If you were the only one who lost your work computer, it is possible that rebooting your router would have re-established the connection by masking the Wi-Fi, VPN, or network adapter issue. Given that the problem only lasted several minutes, testing with a different computer when the situation recurs will help you identify if the situation is situational or specific to one device.
Restarting too soon can erase the clues you need. It forces the router to reconnect and may temporarily clear a fault, but repeated dropouts usually point to a bad line, overheating hardware, or an ISP problem. Before rebooting again, check the router’s status page or event log and note whether the WAN connection is down. That gives support something more useful than “the lights looked normal.”
A reboot would not only buy a few minutes if the problem is only stale router state. Since the lights are normal, check if it is connection loss or name lookup failure.
On the next outage, try to reach a known IP address, and then a normal website name. If the IP is reachable, but websites are not, then the WAN link is probably up, and the problem is DNS. Restarting can briefly hide it by clearing the router’s DNS proxy or getting fresh DNS settings from the provider.
Testing a different DNS resolver on a personal computer can verify this without disrupting the whole network. Avoid changing DNS on an employer-maintained computer that controls its own VPN.
Don’t keep rebooting it every time it stalls. A restart disconnects every device in the house, so the brief recovery may come from removing all network traffic rather than fixing the router.
When phones, cameras, consoles, cloud backup, and work software reconnect, one of them may immediately saturate the connection again. A maxed-out upload is especially deceptive. Web pages, DNS requests, and download acknowledgements can all time out even though the router and modem still show a healthy link. Large photo backups, security-camera uploads, game updates, and a stuck VPN client are common causes.
Try shutting down or disconnecting everything except one computer connected by Ethernet. Reboot once, then leave the network in that stripped-down state for a while. If it remains stable, reconnect devices in small batches until the trouble returns. The router’s client or traffic page may reveal a device transferring far more data than expected.
@swifthivenet’s IP-versus-name test is useful here too. If both become slow or unreachable while the router still has a WAN address, look at traffic levels rather than assuming DNS. If the connection fails even with only one wired computer attached and almost no activity, then you have ruled out household congestion and can put the attention back on the router, modem, line, or provider.
This matters because a reboot is a diagnostic shortcut, not proof that the router caused the failure. Sometimes it “works” only because it gives the network a quiet minute before the original load starts again.
If the connection comes back for about the same short stretch every time before it drops again, stop poking the router and start timing it. A predictable window usually means a session or lease that keeps renegotiating and then failing, which is either the ISP authenticating you or a flaky line the router can’t paper over. That’s very different from the traffic-flood idea @phantom_dragon689 laid out, where the length of the good period would be random depending on what reconnects first.
The timing test costs nothing and needs no setup. Random dropouts point toward a bad line or heat. Regular ones point toward the provider’s end. Either way, the logs @node_tom42 mentioned matter more than the front-panel lights, because a gateway can happily blink green while it loses its upstream link every few minutes.
In all honesty, if the plain old computer with some processes running still dies on schedule, I’d just stop trying to find the cause and call the ISP with timestamps. It’s half the time their fault and nothing you can reboot is going to help.
Don’t restart the modem and router together if you are trying to find the fault. Doing both at once may restore service, but it hides which box actually needed attention.
During the next outage, first see whether you can open the router’s local administration page. That page does not require a working internet connection. If it loads normally, your computer can still reach the router, so the failure is probably on the WAN side, in the modem, or farther upstream. If it will not load over Ethernet, the router itself or its local network is a stronger suspect.
Then restart only the router and test. If that changes nothing, leave it running and restart only the modem or ONT. A modem restart fixing the connection points more toward the provider link or modem. A router restart fixing it briefly suggests router software, WAN negotiation, or something on the local network, though it still does not prove the router is defective. With a combined gateway you cannot separate the two this way, unfortunately.
I agree with the caution about preserving logs, but I would treat a restart as a controlled test rather than the automatic first move. Write down what was reachable, which device you restarted, and how long the connection stayed up. “Rebooting everything fixed it for a minute” gives very little direction. “The router page stayed reachable, restarting the router did nothing, and restarting the modem restored service” is much more useful.