ISP Congestion
Your internet connection shares infrastructure with your neighbours. When many households are online simultaneously — typically 7–11 PM — speed drops across the shared segment. This is ISP congestion, and it's often the real reason your connection is slow in the evenings.
How ISP network infrastructure is shared
Your home connection doesn't have dedicated capacity all the way to the internet. Traffic flows through several shared segments:
- Last mile: The cable or telephone line from your home to the nearest ISP node. On cable (coaxial) networks, this node is shared with 100–500 neighbouring households. On FTTP (full fibre), each home has a dedicated fibre strand to the exchange, making the last mile non-contended. Fibre vs cable — why FTTP handles congestion better →
- ISP backhaul: Traffic from the local node travels over the ISP's internal network to their regional data centre. This capacity is also shared, though with more aggregate bandwidth available
- Peering and transit: Your ISP connects to other networks (Netflix, Google, Cloudflare) via peering agreements. If the ISP has insufficient capacity at these interconnection points, peak-hour congestion appears as slow speeds to specific services
Why evenings are the worst time
Peak hours (7–11 PM in residential areas) coincide with when the most households are simultaneously streaming, gaming, and browsing. On cable networks with shared last-mile infrastructure, a node serving 500 homes with a combined capacity of 1 Gbps will be stressed if 200 homes are each streaming 4K at 25 Mbps — that's 5 Gbps of demand on 1 Gbps of shared capacity.
ISPs plan for statistical multiplexing — they bet that not all customers will use maximum bandwidth simultaneously. This works most of the time, but during peak hours the assumptions break down. The result is congestion at the node level, causing slow speeds for everyone on that segment. How bandwidth contention works →
Diagnosing ISP congestion vs home network problems
| Symptom | Home network problem | ISP congestion |
|---|---|---|
| Slow at same time every day | Unlikely unless it correlates with a scheduled task | Strong indicator of congestion |
| Slow on all devices simultaneously | Possible (router issue) | Typical pattern |
| Slow on one device, fast on others | Strong indicator (device or cable issue) | Unlikely |
| Slow only on Netflix / specific service | Unlikely | ISP peering issue with that service |
| Random drops throughout the day | Hardware fault, overheating, line quality | Possible but less typical |
| Speed test to local ISP server fast, but slow to distant servers | Unlikely | ISP transit or peering congestion |
The test: compare speeds at different times
Run a speed test at 8 AM and again at 8 PM on the same day. If your 8 AM download speed is 300 Mbps and your 8 PM speed is 60 Mbps, and you're connected via Ethernet directly to your router, that pattern points to ISP congestion rather than anything in your home network.
The local server test
When running a speed test, select a server operated by your ISP (usually the default). Then select a server operated by a different ISP or hosted in a distant city. If the local ISP server shows high speed but distant servers are slow, the congestion is at your ISP's peering points — the connections between your ISP and other networks.
What you can do about ISP congestion
ISP congestion at the last-mile level is largely outside your control. Options:
- Contact your ISP with evidence: Send them the results of speed tests at different times of day and ask them to investigate congestion on your node. ISPs are required in most countries to deliver "up to" speeds during off-peak hours, but are expected to make reasonable efforts during peak hours. Persistent congestion is a support issue worth escalating
- Switch to FTTP if available: Full-fibre connections are typically non-contended at the last mile — your fibre strand is dedicated to your premises. Peak-hour slowdowns on FTTP are less common than on cable because the shared infrastructure is further up the network where capacity is much higher
- Consider a different ISP: Different ISPs serving the same area use different infrastructure. An ISP that has invested more heavily in its network or has fewer customers per node will experience less peak congestion. Check independent speed test data for ISPs in your area
- Time-shift bandwidth-intensive tasks: Large game downloads, OS updates, and file transfers can be scheduled for off-peak hours (midnight to 6 AM) when contention is low. Most download clients and cloud backup tools support scheduling
ISP throttling vs congestion
ISP throttling is deliberate speed reduction applied to specific types of traffic (video streaming, torrent, VoIP) or to specific customers who have exceeded data caps. This is different from passive congestion. Signs that suggest throttling rather than general congestion:
- Slow speeds on one service (Netflix, YouTube) but fast speeds to the ISP's own speed test server
- Speed improvement when using a VPN — VPN encrypts traffic, hiding the application type from ISP throttling systems. How VPNs affect speed →
- Throttling typically occurs consistently, not just at peak hours
Net neutrality regulations in many countries restrict ISP throttling of legal content, though enforcement varies. If you suspect throttling, documenting test results to the ISP's speed test server vs third-party servers, and testing with and without a VPN, provides useful evidence. Why your speed is lower than your plan →