What Is Bufferbloat? Why Your Ping Spikes During Uploads and Downloads
How oversized router and modem buffers cause latency to spike under load even when bandwidth looks fine, and how to fix it.
By the SpeedFox team · Last updated
Your idle ping looks great: 12ms, rock solid. Then someone starts a large upload, a cloud backup kicks in, or you start downloading an update, and suddenly your video call stutters and your game turns to soup, even though a speed test still shows plenty of Mbps available. That gap between idle latency and latency while your connection is busy is bufferbloat, and it's one of the most common causes of a connection that "has the speed" but still feels bad in real use.
What Bufferbloat Actually Is
Every router, modem, and many points in between hold a buffer: a small queue of outgoing packets waiting their turn to go out over a connection that's currently busy. Buffers are a good idea in principle, they absorb brief bursts of traffic so packets aren't dropped unnecessarily. The problem is that consumer routers and ISP modems are frequently built with buffers that are far larger than they need to be. When a big upload or download fills the connection, that oversized buffer fills up with queued packets, and every other packet, including the ones carrying your game inputs or voice call audio, has to wait in line behind all of them.
The connection isn't dropping packets or running out of bandwidth. It's making every packet wait its turn in an increasingly long line. That's bufferbloat: added latency caused by excess queuing, not by a lack of raw speed.
Why It Happens
It comes down to a mismatch between buffer size and what TCP (the protocol behind most internet traffic) expects. TCP treats a dropped packet as its signal to slow down. A buffer that's too large delays that signal: instead of dropping the excess packets when full, it keeps queuing them, so TCP keeps sending at full speed, believing everything is fine, while the queue and the latency both keep growing. Only once the buffer is genuinely maxed out does TCP finally get the drop signal it needed minutes of lag ago.
How to Tell If You Have It
The signature is a large gap between your idle ping (latency with the connection otherwise quiet) and your loaded ping (latency while the connection is saturated with a download or upload). A connection with no bufferbloat holds roughly the same ping whether it's idle or fully loaded. A connection with severe bufferbloat might sit at 15ms idle and spike past 400ms the moment a large transfer starts.
SpeedFox measures exactly this: every test compares your idle ping against the 90th percentile of ping sampled while the download and upload phases are actively saturating your connection, then grades the increase on an A+ through F scale (the same convention popularized by Waveform's bufferbloat test):
| Grade | Increase Under Load | What It Means |
|---|---|---|
| A+ | Under 5ms | No noticeable bufferbloat |
| A | 5–29ms | Minimal impact under load |
| B | 30–59ms | Slight lag under load |
| C | 60–199ms | Noticeable lag under load |
| D | 200–399ms | Significant lag under load |
| F | 400ms or more | Severe lag: real-time use degrades sharply |
Run a test and check the "Bufferbloat (Latency Under Load)" section of your results to see your own grade. Full detail on how the loaded-ping figure itself is captured is on the Methodology page.
Why It Matters More Than It Sounds
A connection can have excellent download and upload numbers and still be genuinely unpleasant to use for anything real-time the moment it's under load, precisely because bufferbloat is invisible to a plain bandwidth test. Video calls, competitive games, and voice chat all depend on low, consistent latency, and bufferbloat is one of the few things that can wreck that latency on an otherwise fast connection, exactly when you're also busy using the bandwidth for something else.
How to Fix It
- Enable Smart Queue Management (SQM) or QoS on your router, if it supports it, such as fq_codel or CAKE. These actively manage queue length instead of letting a buffer fill unchecked, and are the single most effective fix.
- Set a bandwidth cap slightly below your real max (roughly 90-95% of your tested speed) in your router's QoS settings. Counterintuitively, this often produces a snappier connection: it keeps your router, not your ISP's oversized buffer further upstream, in control of queuing.
- Check for router firmware updates. Bufferbloat mitigation has improved significantly in modern router firmware; an old router may simply not have it.
- Consider router hardware built around it, several current consumer router lines now ship with SQM enabled by default specifically because bufferbloat became a well-known, well-understood problem.
Bufferbloat vs. Other Causes of Lag
It's worth separating from two other common culprits it's often confused with: Wi-Fi interference, which degrades a connection regardless of load, and peak-hour congestion, which is caused by traffic outside your own network. Bufferbloat is specifically self-inflicted queuing, triggered by your own connection being busy, and it's the one of the three you have the most direct control over.
Key Takeaways
- Bufferbloat is added latency from excess queuing in an oversized buffer, not a lack of bandwidth.
- The tell is a big gap between idle ping and ping while the connection is under load.
- SpeedFox grades this automatically on every test, from A+ (no noticeable bufferbloat) to F (severe).
- Smart Queue Management (fq_codel/CAKE) on your router is the most effective fix.