Bufferbloat: The Hidden Reason Your Internet Lags Under Load
The Lag That Speed Tests Don't Show
Your speed test shows great numbers. Games feel fine at 2 AM. But the moment someone starts a Netflix stream or a big download, your ping triples and shots stop registering. That's bufferbloat — excess delay created by oversized queues inside network equipment, and it affects most home routers shipped in the last fifteen years. The defining symptom is simple: your bandwidth is fine, your idle ping is fine, and your latency under load is destroyed.
Bufferbloat matters because almost nobody games on an idle connection. There is always a console updating, a phone backing up photos, or a browser tab pulling 4K video. A connection that only behaves when nothing else is happening is not really a working connection.
What Is Bufferbloat?
Routers hold packets in queues (buffers) when the connection is busy. Manufacturers made these buffers huge, thinking bigger = fewer dropped packets. The side effect: when your line is saturated, packets wait in line for hundreds of milliseconds before being sent. Your bandwidth is fine — your latency under load is destroyed.
The reason this backfires so badly is that TCP, the protocol behind most bulk transfers, uses packet loss as its main congestion signal. A download ramps up its sending rate until something drops, then backs off. When a router has an enormous buffer, nothing drops — the buffer just swallows the excess and grows. TCP reads the absence of loss as permission to send even faster, so the queue keeps filling until it is physically full. By then every packet entering that queue, including your game's tiny 60-byte position updates, has to wait behind everything already in line.
The maths is unforgiving. A queue holding one megabyte of data draining over a 10 Mbps uplink takes roughly 800 milliseconds to clear. Your game packet did not travel any farther and the route did not change; it simply sat in a queue in a plastic box in your hallway.
Why Upload Is Usually the Worst Offender
Most home connections are asymmetric: a large download pipe and a much smaller upload pipe. Because queueing delay scales with how long the queue takes to drain, the narrow upload path produces the biggest latency penalty. That is why a cloud backup, a Twitch stream, or a friend uploading video to Discord can wreck a connection that shrugs off a 500 Mbps download.
It also explains a symptom people misdiagnose constantly: your ping to the server climbs even though the game itself is barely sending data. The delay is added on the way out of your house, before the packet reaches your ISP at all.
Symptoms of Bufferbloat
- Ping is low when idle but spikes (100-1000ms+) during downloads or uploads
- Video calls freeze when someone else streams
- Games rubber-band during Windows/Steam updates
- Upload-heavy tasks (cloud backup) make the whole connection feel dead
- Web pages crawl while a download runs, then load instantly the second it finishes
- Jitter explodes under load even though packet loss stays at zero
That last point is the fingerprint. Bufferbloat produces delay without loss. If you see heavy loss instead of heavy delay, you are looking at a different problem — start with our packet loss troubleshooting guide.
How to Test for It
Run a ping test while a large download and upload are running. If your ping rises more than 50-100ms compared to idle, you have bufferbloat. The bigger the jump, the worse the problem.
Do it methodically so the result means something:
- Get an idle baseline. Wired if possible, everything else on the network quiet. Note both ping and jitter. Our browser ping and jitter test works well here — it measures warm HTTPS round-trip time to nearby cloud endpoints rather than sending ICMP packets, so it is a proxy for true network latency, but because the method is identical between runs the before/after comparison is fair.
- Saturate the download with a large game or OS update, and re-test while it runs at full speed.
- Saturate the upload separately — a big cloud sync or file upload — and re-test again. Test this direction even if it feels irrelevant; it is usually where the damage is.
- Load both directions at once for the worst case, which is what a house full of people actually looks like at 21:00.
- Subtract. The number that matters is loaded ping minus idle ping, not the raw figure.
Heavy bufferbloat can also show up as dropped real-time packets. Running the packet loss test while an upload is in progress shows whether queuing is turning into loss and jitter.
Reading Your Latency-Under-Load Number
Use this as a practical grading scale for that difference. These are working ranges rather than an official standard, but they map closely to how the problem feels in a game.
| Ping increase under load | Grade | What you actually notice |
|---|---|---|
| Under 5ms | Excellent | Properly managed queues. You can download a 100 GB game and play at the same time without knowing. |
| 5-30ms | Good | Slight softening under heavy load. Fine for everything except top-level competitive play during a full-speed download. |
| 30-100ms | Noticeable | Duels start going the other player's way when the household is busy. Video calls begin to stutter. |
| 100-250ms | Bad | Classic bufferbloat. Rubber-banding, delayed hit registration, voice chat breaking up whenever anything downloads. |
| Over 250ms | Severe | The connection is effectively unusable for real-time traffic while any transfer runs. Web browsing feels broken too. |
Which Connections Suffer Most
Bufferbloat is a queue-management problem, not a technology problem, so it can appear on any line. But some setups make it far more likely.
| Connection type | Typical tendency | Why |
|---|---|---|
| DSL / VDSL | High | Narrow upload and older modem hardware with large fixed buffers. |
| Cable (DOCSIS) | Moderate to high | Asymmetric upload plus modem-side buffering; newer standards include active queue management, older gear does not. |
| Fibre (FTTH) | Lower | Symmetric or near-symmetric capacity drains queues fast, but a cheap router can still bloat a fast line. |
| Fixed wireless / 4G-5G | Variable | Radio schedulers add their own queues, and capacity swings with signal quality and cell load. |
| Satellite | High | Long base latency plus deep buffers designed to keep the expensive link busy. |
How to Fix Bufferbloat
- Enable SQM / Smart Queue Management: the gold standard. Look for "SQM", "Cake", or "fq_codel" in your router settings (standard on OpenWrt, many ASUS and Ubiquiti models). These algorithms keep queues short deliberately, dropping or marking packets early so senders slow down before the queue grows.
- Use QoS with bandwidth limits: set limits to ~90-95% of your real measured speed — this keeps the queue in your router, where it's managed, instead of in your modem. This step is not optional. If your router thinks it has more capacity than the line really has, the queue forms downstream in equipment you cannot control and the fix does nothing.
- Tune the limit down, then back up. If latency under load is still poor at 95%, drop to 85% and re-test. Trading a slice of peak throughput for a flat latency curve is almost always the right deal for a gaming household. Our router QoS setup guide walks through the settings in detail.
- Check your router's CPU can keep up. Smart queueing is processing work. A budget router that shapes 100 Mbps happily may max out its CPU and cap your throughput at gigabit speeds. If enabling SQM slashes your download speed, the hardware, not the setting, is the limit.
- Upgrade your router: modern gaming routers ship with anti-bufferbloat QoS enabled by default.
- Ask your ISP about DOCSIS 3.1 / fiber: newer standards include Active Queue Management on the line itself.
What Bufferbloat Is Not
Three problems produce similar complaints and need different fixes:
- Wi-Fi instability. If ping is erratic even with the line idle, the radio link is the suspect, not queueing. Test wired to separate them.
- ISP peak-hour congestion. If your latency rises every evening while your own network sits idle, the queue is not in your house. That is peak-hour congestion, and no router setting fixes it.
- Distance to the game server. A steady, unchanging 120ms is geography. Bufferbloat is load-dependent by definition — if the number does not move when you start a download, look elsewhere.
The Bottom Line
Bandwidth tells you how much your connection can carry; bufferbloat decides how it feels when it's actually carrying it. If your connection is fast but inconsistent, fix the bloat before paying for more Mbps. A 100 Mbps line with proper queue management will beat a 1 Gbps line without it for every real-time application you care about — games, calls, and remote desktop alike.