Why does my internet slow down in the evening?
Published on
All day it's fine. Then around eight in the evening the stream starts buffering, your ping jumps mid-match, pages take a beat too long to open. By midnight everything is back to normal. If you've wondered why your internet slows down at night, the answer usually isn't your router — it's the shared capacity between your home and the exchange.
What makes evening the busy hour?
Traffic peaks roughly between 7 pm and 11 pm. Everyone gets home at the same time, starts a series at the same time, joins a game at the same time, takes a video call at the same time. The industry calls this peak time, and it's when the network is under the most strain.
Here's the part that surprises people: your subscription is not a private pipe reserved for you. The line leaving your home reaches a street cabinet, then an exchange, then your provider's backbone. Every link in that chain is shared with your neighbours. Providers size capacity around average usage — and the average doesn't happen at 8 pm, it happens at 3 in the afternoon. When demand peaks, the pipe fills and everyone's share shrinks.
Is the slowdown outside your home, or inside it?
There are really two kinds of evening slowdown, and mixing them up sends you looking for the fix in the wrong place:
1. Local congestion (outside). The street cabinet, the exchange, or your provider's upstream capacity is saturated. There is no setting you can change at home; the fix is evidence plus a conversation with your provider.
2. Simultaneous use at home (inside). It's evening and five people are in: one streaming 4K, one downloading a game update, a phone running its cloud backup. The line didn't slow down — it got divided. We worked through how much you actually need in how many Mbps do you need at home.
The quickest way to separate them: when the slowdown hits, pause everything else on the network for a minute and measure. If speed recovers, the problem is inside. If it doesn't, it's outside.
A 10-minute self-diagnosis
- Measure at two different times of day. Run the speed test once in the afternoon and once around 9 pm. Use a cable — Wi-Fi adds noise of its own.
- Watch ping and jitter, not just download. The classic congestion signature is download falling while ping rises and starts bouncing. If download drops but ping stays flat, the cause is usually in-home usage.
- Repeat at midday on a weekend. If it's slow then too, this isn't a peak-hour issue — you may have a plain fault.
- Ask a neighbour. If someone in the same building or street on the same provider sees the same evening dip, it's almost certainly local capacity.
- Keep records. Date, time, result. When you talk to your provider, this is the only thing that moves the conversation forward.
"Will rebooting the router fix it?"
It's the most common advice on forums, and for peak-hour congestion it usually does nothing. Rebooting clears a stall on your own device — a full memory buffer, a stuck session. It cannot widen the pipe out in the street.
When it does help: if speed genuinely returns to normal after a reboot and stays there for hours, your problem was the router, not congestion. Trying it once is free — but if you need a nightly reboot to stay online, that's not a fix, it's a symptom of failing hardware.
What actually helps during peak hours
You can't expand the shared capacity, but you can spend your share more carefully:
- Switch to a cable. When the line is already tight, the extra latency and loss Wi-Fi adds hurts twice as much. For gaming and calls, Ethernet is the single biggest win.
- Move big downloads to the small hours. Game updates, cloud backups, torrents — all of them have a schedule setting. Set them for 2 am.
- Drop streaming quality one notch. At peak time, 1080p that plays is better than 4K that stalls. Per-platform requirements are in how many Mbps for streaming.
- Turn on QoS/SQM in your router. If it's available, it suppresses the latency spike a full line causes (bufferbloat), which makes gaming and video calls far more usable.
- Use the 5 GHz band. In the evening your neighbours' Wi-Fi is on too, and 2.4 GHz gets crowded. The trade-offs are in 2.4 GHz or 5 GHz.
When to call your provider
| Symptom | Likely cause | What to do |
|---|---|---|
| Slow only in the evening, ping bouncing too | Local congestion | Log results, report to provider |
| Slow in the evening, fine once devices are paused | In-home sharing | Schedule usage, review your plan |
| Slow at every hour | Line, router or plan problem | Start with a general diagnosis |
| Test looks fast, browsing feels slow | Latency, DNS, Wi-Fi | A separate issue |
If local congestion looks likely, go in with at least a week of wired, timestamped measurements. "It's slow in the evenings" gets you a script; "over the last 7 days I average 22 Mbps between 8 and 11 pm versus 94 Mbps during the day" gets you an engineer. If nothing moves, the escalation path and your rights in Türkiye are laid out in not getting your advertised speed.
Does switching to fibre solve it?
It usually improves things, but it isn't magic. Fibre carries far more capacity per subscriber than copper and doesn't degrade with distance, so the peak-hour dip is much less noticeable. Still, fibre is shared too — if the exchange uplink or the provider's backbone is saturated, a fibre customer feels the evening dip as well. Fibre reduces the problem; it doesn't guarantee it away.
Don't confuse it with general slowness
The signature of evening slowdown is that it's tied to the clock. If things are slow all day, look elsewhere; the step-by-step path is in why did my internet slow down. And if the numbers look fine but everything still feels sluggish, the culprit is latency rather than throughput: speed test is high but the internet feels slow.
Summary
- Evening slowdown is mostly shared capacity filling up between 7 and 11 pm — not your router.
- Separate the two cases first: outside (local congestion) or inside (simultaneous use at home)?
- The congestion signature is download falling while ping rises and bounces.
- Rebooting won't fix congestion; scheduling big downloads, using a cable and enabling QoS will.
- If you suspect local capacity, collect a week of timestamped, wired measurements before you call.