Why is my Wi-Fi fine during the day but terrible after 8pm? I read that evening slowdowns usually mean neighborhood congestion, but I’m not sure whether “congestion” applies to Wi-Fi itself or my internet connection. At 8:17, streaming starts buffering in the living room, even after I move my router off the floor. Does that explanation hold up?
Moving the router off the floor may improve signal, but it will not fix an evening slowdown caused by your ISP or heavy traffic from devices inside your home.
Run the same internet speed test during the day and after 8pm, first over Wi-Fi and then with a computer connected directly to the router by Ethernet. If Ethernet slows down too, the likely issue is your internet connection or neighborhood capacity. If Ethernet stays fast while Wi-Fi tanks, nearby networks may be crowding the same channels, especially on 2.4 GHz. Try 5 GHz or 6 GHz if your equipment supports it.
The consistent 8:17 timing is worth checking. A cloud backup, security camera upload, game update, or another household device may start on a schedule and consume bandwidth. Check the router’s device or traffic list when buffering begins before assuming the neighborhood is responsible.
17 Likes
Don’t pay for a faster plan or new router until you know which side is slowing down. “Congestion” can mean crowded radio channels in your home area or an overloaded ISP connection, and only the first is actually a Wi-Fi problem.
A Speedtest by Ookla result over Wi-Fi can’t tell you which side is congested. Run it by Ethernet during the day and after 8pm: if wired speed drops too, blame the ISP connection; if wired stays steady, troubleshoot Wi-Fi channels and interference.
Plugging into a mesh satellite or wireless extender does not count as a true Ethernet test. That traffic still crosses Wi-Fi before reaching the modem, so evening interference can make the “wired” result slow too.
Connect directly to the main router, ideally with mesh nodes and extenders temporarily unplugged. If that connection remains fast after 8pm, the trouble is inside your home’s wireless setup. If it slows at the same time, ISP congestion becomes much more likely.
The consistent start time still makes scheduled household traffic suspicious, but check the router’s traffic page before changing plans or buying hardware. A mesh backhaul problem can look almost identical to an overloaded internet connection.
Don’t start buying hardware or changing channels at random. First test the Wi-Fi link without involving the internet: ping your router’s local address during the day, then repeat after 8pm from the same spot.
If latency or packet loss to the router gets much worse, the slowdown is Wi-Fi interference or congestion. If that local connection stays steady while websites and downloads crawl, look at scheduled household traffic or the ISP connection instead.
Repeat the local test on 5 GHz near the main router. A clean 5 GHz result with a bad 2.4 GHz result usually means crowded radio channels, while both bands staying clean points away from Wi-Fi.
The scheduled-traffic theory everyone keeps circling back to is the least likely explanation once you see a consistent evening drop. That pattern is textbook peak-hour ISP congestion, especially on cable where you share a segment with the whole block and everyone starts streaming around the same time. A cloud backup wouldn’t line up neatly at 8 every night unless you actually set it that way.
The ping-your-router idea from @shadow_cloud_root is the smart first move though, since it separates your wireless from the internet without touching a single setting. Just don’t expect it to catch shared-line congestion, because your local link can stay perfect while the connection past the modem crawls. Run a wired Speedtest at 8 and again at 2am. If the late-night result jumps back up, it’s the ISP and no new router fixes that.
Don’t factory-reset the router or start changing several settings at once. That can erase the evidence and leave you with a different problem.
I’d be cautious about calling an exact 8:17 slowdown “textbook” ISP congestion. Neighborhood traffic usually builds gradually as people get home and start streaming. A sudden change at nearly the same minute every night points more toward a schedule somewhere. Besides backups and cameras, check the router itself for parental controls, bedtime rules, QoS profiles, guest-network schedules, automatic channel scans, or “eco” settings. Some routers and mesh systems can also steer a device from 5 GHz to crowded 2.4 GHz without making it obvious because both bands use the same network name.
Watch what happens at the moment it slows down. Does every phone, TV, and computer become sluggish, or only one device? Does the Wi-Fi indicator disconnect briefly? In the router page, check which band the affected device is using and whether its link speed suddenly drops. Testing another device in the same room is useful because a single laptop’s driver, power-saving mode, VPN, or background task can look like a whole-network failure.
The direct Ethernet test suggested earlier is still the cleanest final check, but timing matters. If wired service gradually worsens through the evening and improves late at night, ISP capacity is a reasonable suspect. If everything falls off a cliff at 8:17 and returns at another exact time, I’d inspect schedules and router behavior before trying to convince the ISP that the neighborhood is overloaded.
A clean wired speed test does not automatically clear the ISP.
Speed tests usually hit a nearby server with a favorable route. Your result can look normal while streaming, gaming, or certain sites are struggling farther upstream because of routing or peering congestion. If Ethernet stays fast after 8pm but every device has trouble with the same services, that still points beyond the Wi-Fi. Try more than one test server and compare a large download, video stream, and ordinary browsing rather than treating a single number as a verdict.
There is another common culprit that has only been touched on here: upload saturation. A camera, backup, photo sync, torrent, or console can fill a modest upload connection and make downloads feel awful because acknowledgments and other small packets get stuck behind it. The headline download speed may even remain respectable while latency jumps through the roof. Watch both upload use and latency when the slowdown begins. Pausing suspected devices for a minute is more useful than guessing what they might be doing.
The exact 8:17 start still makes me skeptical of the “whole neighborhood starts streaming” explanation. ISP congestion usually follows a rough evening window, not a clock alarm. That does not rule out the ISP, since maintenance jobs or network policies can run on schedules too, but your router’s parental controls, traffic rules, automatic optimization, and connected-device list deserve inspection first.
Check the modem or router logs before rebooting anything. Look for repeated WAN reconnects, loss of synchronization, or error counts climbing around the same time, and take screenshots because a restart may clear the evidence. If local pings remain clean, direct Ethernet remains fast, and only particular internet services degrade, report that pattern to the ISP instead of saying only “my Wi-Fi is slow.” If local pings worsen, then it really is the wireless side and channel use, band steering, or mesh backhaul becomes the better target.