Home / Knowledge Center / Ping & Latency
What Is Bufferbloat?
9 min read · Updated 2026-09-17
Bufferbloat is what happens when network equipment holds too much data in a queue instead of dropping a little of it early. Throughput looks perfect, but every interactive packet waits behind a long line of bulk traffic. It is the single most common reason a gigabit connection feels unresponsive while someone uploads a video.
Key takeaways
- Bufferbloat is a latency problem caused by queue size, not by insufficient bandwidth.
- The signature symptom is idle latency that is fine and loaded latency that is many times worse.
- It hits video calls, games and page loads while a large upload or download runs.
- Smart Queue Management (SQM, usually fq_codel or CAKE) is the real fix.
- A faster plan can mask it but does not remove it.
Why buffers cause delay
Every router, modem and switch has a buffer to absorb bursts of traffic. Congestion control expects a full buffer to drop packets, which signals the sender to slow down. When the buffer is far larger than needed, it absorbs everything instead, so senders keep pushing and the queue keeps growing.
Nothing is lost, but everything is late. A packet that needs 20 ms to cross the internet may sit for 300 ms in a queue on your own modem before it leaves the house.
How it feels in practice
The symptoms are specific enough to diagnose from experience alone.
- Video calls break up while a cloud backup or game update runs.
- Games rubber-band whenever someone else in the house streams or uploads.
- Web pages take seconds to start loading during a large download.
- Speed tests report the full advertised speed, which makes the problem look invisible.
How to test for it
Measure latency while the connection is idle and record the number. Then start a sustained upload and a sustained download and measure again. Compare the two figures rather than looking at either alone.
A rise of a few milliseconds is normal. A rise from 20 ms to 150 ms or more means the queue is the bottleneck, and no amount of extra bandwidth will change that ratio.
How to fix it
The fix is to manage the queue rather than enlarge it.
- Enable SQM or QoS on your router — look for fq_codel, CAKE or a bandwidth-limited QoS setting.
- Set the shaping limits slightly below your measured line rate, typically 85–95 percent, so the queue lives on your router rather than in the modem.
- Retest idle versus loaded latency after each change; the goal is a small, steady increase under load.
- If the router lacks SQM, an aftermarket firmware or a router that supports it is a more effective purchase than a faster plan.
- Prefer Ethernet for latency-sensitive devices, since WiFi adds its own variance on top.
What bufferbloat is not
It is not packet loss, though a badly managed queue eventually drops packets. It is not distance-related latency, which stays constant whether the line is busy or idle. And it is not an ISP fault in most cases — the oversized buffer is usually in consumer equipment inside the home.
Put this into practice with a real measurement.
Measure idle latency first