You sit down for a ranked match with 18 ms ping. Someone in the next room starts a 4K stream and your latency shoots past 150 ms without warning. The line still shows plenty of megabits — so what changed? The answer is usually bufferbloat: routers holding packets in oversized queues instead of dropping or scheduling them fairly.
Queues are not free storage
Every router between you and the internet has buffers. When traffic arrives faster than the next link can send it, packets wait in line. A small buffer smooths bursts; a large buffer hides congestion from TCP, which then keeps sending until the queue is full. By the time packets finally leave, they are seconds late — but throughput still looks high because data is moving, just slowly through a long pipe.
That is why a speed test and a latency test tell different stories. Throughput measures how much data you can push through the pipe. Latency measures how long each packet waits in line. Bufferbloat is the gap between idle latency and latency under load.
How to recognise it at home
Classic signs include voice calls that crackle only when a backup runs, games that stutter during evening streaming, and web pages that feel fine until a large download starts. Run a simple experiment: note ping while idle, then start a big download on the same connection. If median ping rises more than a few milliseconds — especially past 50–100 ms on a wired link — queueing is likely the culprit, not your ISP's headline speed tier.
- •Wired vs Wi‑Fi — test on Ethernet first. Wi‑Fi adds its own delay and can mask or mimic bufferbloat.
- •Upload matters — video calls and cloud backups saturate upload queues on asymmetric lines (typical cable/DSL).
- •One device can affect everyone — the bottleneck is often the home gateway, not the device that started the transfer.
Fixes that actually work
Buying a faster plan rarely cures bufferbloat if the router still buffers megabytes per flow. Better approaches:
- Enable SQM or fq_codel on a router that supports it (OpenWrt, many mesh systems). These algorithms drop or schedule packets before queues grow huge.
- Set sane upload/download caps slightly below your line rate so the ISP modem is not the first place packets pile up.
- Use wired backhaul for mesh nodes — wireless backhaul doubles the contention.
- Schedule heavy backups for off-peak hours when real-time traffic is quiet.
Bufferbloat vs other problems
High latency under load is not the same as packet loss (dropped packets), jitter (uneven spacing), or slow DNS (naming delays before a connection even starts). Triage in that order: if loss is zero but latency balloons when the link is busy, focus on queue management. If loss is high even when idle, look for Wi‑Fi interference or failing cabling instead.
The takeaway
A connection can be fast and unresponsive at the same time. Bufferbloat explains that paradox. Measuring latency while the line is busy — not just when it is quiet — is the single most useful habit for gamers, remote workers and anyone sharing a household connection.