Why Everything Slows Down at Night: The Last Mile

Same node, same device, smooth all day, and slow the moment evening hits — this kind of clockwork slowdown is rarely the VPN breaking. It's one segment of the path filling up with people during peak hours. Finding which segment is congested beats switching nodes a dozen times, and it beats waiting until midnight for speed to recover on its own.

The same rule as always: change one variable at a time. Switch the node, switch the device and switch networks all at once, and even once things improve you won't know which step actually did it.

"The VPN is broken" sounds like a simple explanation, but it doesn't hold up — the same client, the same account, working fine all day. Something broken doesn't break for only a few specific hours and work the rest of the time; it just stays broken. The one thing that genuinely changes by time of day is how congested this particular path happens to be.

This kind of clockwork slowdown has a tell: the symptom shows up at roughly the same time every day, and the daytime is fine. That one detail — a fixed time window — already rules out a broken device or a broken account, both of which would misbehave at random, and narrows things down to a short list of congestion-related causes.

Start with one test: run a speed test with the VPN off

On the same network, at the same hour things usually slow down, run a speed test with the VPN off, then run one with it on, and write down both numbers.

• Slow even without the VPN: the problem is on your own network — keep reading for the "last mile," specifically the part on your end.
• Fast without the VPN, slow only with it on: the problem is somewhere along the VPN's own path — keep reading to check the node or wider congestion.

This one step cleanly separates "a problem with my own network" from "a problem somewhere on the VPN's path," instead of suspecting both at once. The usual first move is to switch nodes, discover it's still slow, and only then think to test with the VPN off — that's backwards. Testing this first saves most of what comes after, and the two tests together take barely a minute or two.

Most common: peak hours congest the "last mile," not the VPN itself

Whether a VPN is involved or not, the "last mile" is the short segment between your device and your own internet provider. It gets busier during evening peak hours almost everywhere, for two separate reasons.

The last mile on your end

Everyone in the same building or neighbourhood gets home from work at roughly the same time and starts streaming, gaming or downloading updates almost simultaneously, and these users often share the upstream capacity of the same local line. More people using it means less bandwidth for each household, and that has nothing to do with whether a VPN is running — it would be just as slow without one, only nobody usually bothers to check until the day it feels slow with the VPN on and they notice for the first time that this hour was never great to begin with.

There's a pattern to this too: neighbourhoods with more concentrated evening usage, like ones with a lot of young renters, tend to show worse evening congestion than areas near business districts, simply because the second kind has fewer devices online at night.

The last mile on the exit end

The VPN node has its own "last mile" connecting it to the wider internet, and it gets just as congested when usage peaks. The key detail is that this "peak hour" runs on the clock of wherever the node sits, not yours — if the node is in a region with a very different time zone, its busiest hours might land at a time that means nothing to you, or they might land squarely on your own evening. It comes down entirely to the region.

Here's the logic: if a node sits in a region close to your own time zone, the two evening peaks mostly line up, so your evening is also its evening and the congestion stacks. Switch to a region seven or eight hours apart or more, and your evening lands somewhere in that region's daytime or even the middle of its night — which makes it easier to land outside the truly crowded window.

Next most common: a wider, regularly recurring congestion

Beyond the last mile on either end, the backbone links connecting different networks in the middle can also get congested at fixed times of day. This kind of congestion doesn't affect one node — it affects everyone passing through that backbone link, which looks a lot like a single node having a problem, except switching nodes doesn't fix it, because the next node very likely routes through the same backbone anyway.

Try two or three nodes in different regions. If all of them slow down at the same peak hours and all of them test fine during the day, that points at this wider kind of congestion rather than any one node.

There's no reliable way around this kind of congestion — the practical move is shifting off the real peak window, half an hour earlier or later is often enough to miss the worst of it. Trying a node much further away in time zone at the same moment is also worth doing, and it can work better than cycling through nearby regions, for the same time-zone-mismatch reason covered above.

Rarer: not a time-of-day issue, the node is just consistently crowded

Some nodes aren't slow only at peak hours — they're carrying more users than they comfortably should on an ongoing basis, and the evening peak just makes an already-tight situation more obvious. Testing at a different time of day won't help much here, because the bottleneck is structural, not tied to a particular hour; daytime looks tolerable purely because the daytime baseline is lower than the evening one.

Pick an off-peak moment on an ordinary day and test that specific node on its own. If even its daytime performance is noticeably worse than other nodes, the node itself is carrying too much load — the evening slowdown was never really about the evening. Testing a different node side by side makes the gap obvious.

Switch your everyday default to a node in a different region, rather than only swapping temporarily when it feels slow at night — a structural problem needs a steadier default, not a nightly workaround.

Judging whether a node is chronically overloaded takes a few days of observation, not one test. If a region offers several nodes, rotating through them for a few days and keeping notes beats drawing a conclusion from a single speed test.

Rule out the device and everything else at home

Beyond congestion, evening hours tend to stack a few unrelated factors on top:

• Other people at home are online during the same peak hours, and one router has to serve several devices at once — when a home router simply can't keep up, it looks a lot like line congestion. Worth asking whether anyone else is downloading or streaming at the same moment you're testing.
• An older router is most likely to show its age during the busiest hours of the night. Whether a reboot helps is a simple way to tell — if it does, the router itself can't handle peak load; if it doesn't, keep looking at the network layer instead.
• Video and games have their own server-side load during evening peaks too, a separate question from this network layer entirely — video that keeps buffering breaks that chain down on its own, and the two together cover most evening slowdowns.

In summary

For a slowdown that hits every evening, start with a VPN-off speed test to tell whether the problem is on your end or somewhere on the VPN's path, then check the last mile on both ends, wider backbone congestion, or a node that's chronically overloaded — without overlooking the router and other devices at home, which are easy to miss. What actually needs fixing long-term is keeping a less congested node as your default, rather than re-testing from scratch every night.

If cycling through nodes still doesn't reveal a pattern, VPN running slow: check these six things first covers more ground; when a good speed test number doesn't match how it actually feels, why a good speed test can still feel slow is worth reading too. FastOrange switches nodes in one tap, so hitting a slow line at peak hours means trying another one within seconds — every registered account gets free daily trial time to start testing with.