Why Your Internet Drops at the Same Time Every Day
Short answer
A drop that happens at a predictable time is almost never random hardware failure. Check three things in order: a scheduled reboot or parental control timer in the router's settings, a DHCP lease renewal landing at the same interval, and something electrical switching on nearby. Note the exact time and duration for three days — the pattern identifies the cause.
On this page
A fault that happens at 2am every night, or every evening at seven, or every ninety minutes, is a gift. Random failures are hard to diagnose. Scheduled ones have a cause that is itself scheduled, and the timing narrows the list dramatically before you touch anything.
The first job is not fixing. It is recording. For three days, write down the exact time the connection goes, how long it stays down, and whether it affects every device or one. That log does most of the diagnostic work.
What the timing tells you
| Pattern | Most likely cause |
|---|---|
| Same time overnight, brief | Scheduled router reboot, or provider maintenance |
| Same time each evening, sustained | Congestion, or a parental control schedule |
| Regular interval (2, 12 or 24 hours) | DHCP lease renewal or provider session reset |
| Same time each morning | An appliance, boiler or timer switching on |
| Weekdays only, office hours | Something in the building or a neighbour’s routine |
| Random but clustered | Interference, not scheduling |
Two of those are configuration, two are environmental and two are your provider’s. Work through them in that order, because the configuration ones are free to check and instant to fix.
Check the router’s own schedules
Surprisingly often, the router is doing exactly what someone told it to do.
Log into the admin page — 192.168.1.1, 192.168.0.1 or 10.0.0.1 cover most
routers, and
reading the gateway address off your device
finds the rest. Then look for:
- A scheduled reboot, usually in the administration, system or maintenance section. Many routers ship with this on, set to an overnight hour. A reboot takes 2–3 minutes, which matches a short overnight drop exactly.
- Parental controls or access schedules, in a parental control or access control section. These can be set per device or network-wide, and an evening cutoff someone configured a year ago is a classic.
- A guest network timer, which expires the guest network on a schedule. If the affected devices are on the guest network, this is your answer.
- Firmware auto-update windows, which apply updates and reboot at a fixed hour.
If one of these matches your log, you are finished. Change or disable the schedule.
Check the DHCP lease interval
Your router leases each device an address for a fixed period, commonly 24 hours but sometimes as short as 2. When the lease renews, a correctly behaving device keeps the same address and nothing happens.
When it does not behave correctly — a firmware bug on the router, a conflict with a statically assigned address, or an exhausted address pool — the renewal produces a brief outage at an interval that exactly matches the lease time.
In the router’s DHCP settings, check the lease time. If it matches your drop interval, you have a strong candidate. Two fixes:
- Lengthen the lease to 24 hours or a week. Fewer renewals, fewer chances to fail.
- Widen the address pool. A pool of 50 addresses in a house with 40 smart devices runs out, and devices that cannot get an address fail in exactly this way.
A device showing an address starting 169.254 during an outage confirms it: it
failed to get a lease and assigned itself a placeholder.
What those address ranges mean
covers how to read them.
Check what switches on at that time
This is the one people dismiss and it is responsible for a real share of these cases.
Wi-Fi on 2.4GHz shares its spectrum with a lot of ordinary household equipment. Anything that runs on a timer, or that someone uses at the same time daily, will produce a daily fault.
- Microwave ovens emit directly in the 2.4GHz band. Wi-Fi measurably degrades while one runs, and an old or poorly sealed one degrades it badly.
- Cordless phone base stations, baby monitors and older wireless doorbells.
- Boiler timers, immersion heaters and electric showers — these cause electrical noise rather than radio interference, and matter most on DSL connections and powerline adapters, both of which run over wiring.
- Halogen lamps and some LED drivers on the same circuit as the router.
- A neighbour’s equipment on a routine. Harder to prove, worth considering when everything in your own house checks out.
The test is straightforward: when the drop occurs, check whether ethernet also fails. Interference affects Wi-Fi only. If a device on a cable keeps working through the outage, the fault is in the radio environment, not the line.
Switching the affected devices to 5GHz resolves most interference cases outright, since almost nothing else uses that band. Which band your devices should be on covers the trade-off.
Check whether the line itself goes
The router’s internet or WAN light answers this definitively. Watch it during an outage.
The light goes out or turns red. The connection from your provider dropped. Nothing inside your house caused that, and nothing inside your house will fix it.
The light stays solid while devices lose connectivity. The line is up. The fault is the router’s Wi-Fi, its DHCP, or the devices.
Most routers also keep a system log or connection log, usually under status, system or advanced. Entries timestamped at your outage window are the best evidence you will get. On DSL connections, look for lines about retraining, resynchronisation or errors — a line that resyncs daily is a line fault, and a provider engineer visit is the fix.
Providers also run maintenance windows, typically in the small hours. A brief overnight drop that never happens during the day, with the WAN light cycling, is very likely this. Their status page or app will sometimes say so.
What to do with each conclusion
| Finding | Action |
|---|---|
| Router schedule or parental control | Change the setting. Done. |
| DHCP lease interval matches | Lengthen the lease, widen the pool |
| Wi-Fi only, ethernet unaffected | Move devices to 5GHz, change the 2.4GHz channel |
| WAN light drops out | Report it to your provider with your log |
| Nothing matches, router is years old | Firmware update, then consider replacement |
When you contact your provider, lead with the log. “It drops at 03:15 every night for four minutes and the WAN light goes out” gets a different response from a first-line script than “my internet is unreliable”. Specific, repeatable timing is the one thing that makes a line fault easy for them to confirm.
The workaround that is not a fix
A scheduled nightly reboot, set in the router’s own settings for a time nobody is using the connection, masks a lot of these. If the router develops a fault after days of uptime, this keeps the house working.
It is a workaround. The underlying cause is usually ageing firmware, a memory leak or hardware degradation, so check for a firmware update first. A router that needs rebooting daily to stay reliable is near the end of its useful life, and a replacement will fix more than the schedule does.
Realistic expectations
Most daily drops turn out to be a router schedule someone forgot about, a DHCP lease interval, or a microwave. All three are identifiable in an evening and fixable for free.
The ones that are not fixable from your side are line faults and provider maintenance, and the timing log is what gets those taken seriously. If the WAN light goes out at the same minute every day, no router setting, DNS change or new equipment will alter that, and the only productive conversation is with the people who own the line.