Glossary · Performance
Network Congestion: definition, explanation, and why it matters
The slowdown that occurs when more traffic is offered to a network link than the link can carry, causing queueing, latency spikes, and packet loss.
Definition
The slowdown that occurs when more traffic is offered to a network link than the link can carry, causing queueing, latency spikes, and packet loss.
Plain-English explanation
Congestion happens when demand exceeds capacity at any hop in the path — your Wi-Fi, your ISP's backhaul, a peering point, or the destination server. Routers respond by queueing packets; full queues drop packets.
The classic symptoms are rising latency and jitter under load, even though bandwidth tests at idle moments look fine.
Real-world examples
- Streaming quality drops every evening when neighborhood usage peaks — that's local last-mile congestion.
- A game's ping doubles when someone in the house starts a large upload — that's congestion in the home upload buffer.
Why it matters
Congestion is invisible to single-shot speed tests but dominates the lived experience of a connection.
Mitigations like QoS, SQM, and traffic prioritization specifically target congestion.
Common misconceptions
- Myth: Buying more bandwidth eliminates congestion.
Reality: It can — but only if the congested point is the link you upgraded. Congestion further along the path is unaffected.
Frequently asked questions
- How can I tell if I'm congested?
- Run a ping during peak hours. Latency that climbs sharply under load (bufferbloat) is the hallmark.