Bufferbloat Explained (and How to Actually Fix It)

Your connection is perfect — until someone starts a download, a backup, or a 4K stream, and your ping explodes from 20 ms to 400 ms. That’s not “slow internet.” That’s bufferbloat: your router politely making your game packets stand in line behind someone’s Netflix stream or a Windows update. It’s one of the most common — and most fixable — causes of gaming lag.

What bufferbloat is

Every router and modem has buffers: small queues that hold packets when more traffic arrives than the line can send right now. Think of it as a waiting room at the ISP’s front door — a few chairs are fine, but your router has a stadium. A small queue smooths over tiny bursts and is healthy. The problem is that for years, manufacturers shipped equipment with enormously oversized buffers, on the theory that bigger buffers mean fewer dropped packets.

They do — but a packet sitting in a queue is a packet being delayed. When your line saturates, an oversized buffer can hold seconds of traffic. Your game’s packets join the back of that queue and wait behind someone’s file download. Nothing is “lost”; everything is just late. That excess delay under load is bufferbloat.

The cruel part: TCP, the protocol most traffic uses, adapts to delay by filling the buffer even harder. So the queue rarely drains on its own while the load continues.

It’s worth understanding why games suffer so much more than other apps. Streaming video buffers many seconds ahead, so a queueing delay is absorbed silently. A game can’t buffer the future: your inputs and the server’s world state are exchanged in real time, dozens of times per second, and every packet delayed in a queue arrives stale. A two-second buffer is a minor detail for Netflix and a death sentence in a ranked match.

The telltale symptoms

• Ping is low and stable when the connection is idle.
• Latency balloons the moment any heavy traffic starts — yours or anyone else’s on the network.
• Games rubber-band and calls go robotic during downloads, cloud backups, game updates or streaming, then recover seconds after the load stops.
• Speed tests look great, because they only report throughput — they measure the very condition (a saturated line) that triggers the problem, without reporting what it did to latency.

How to test for it: measure latency idle vs under load

Diagnosing bufferbloat takes two numbers: your latency while the line is idle, and your latency while it’s pushed hard. LagScope’s stress test does exactly this in about 8 seconds: it measures your baseline ping, saturates the line with a download and upload, measures again under load, and grades the difference.

• Small increase (a few ms to ~30 ms) — your queuing is healthy. Your lag has another cause.
• Large increase (hundreds of ms) — classic bufferbloat. Every busy moment on your network is a lag event for everyone on it.

Run it a couple of times — once with the network quiet, once while a big download is already running — to see the full picture.

The fix: smart queue management

You don’t fix bufferbloat by buying more bandwidth; a bigger pipe just fills the same broken queue faster. You fix it by managing the queue:

1. Enable SQM with Cake or fq_codel. SQM (“smart queue management”) is a bouncer for the waiting room: it keeps the line short and makes every app take turns, so no single download can hog the queue. OpenWrt has them built in (the SQM QoS package); many newer routers from gaming- and prosumer-focused brands ship Cake, fq_codel or an equivalent under names like “Smart Queue Management” or “anti-bufferbloat.”
2. Set the SQM bandwidth to ~90–95% of your measured line rate. SQM only works if your router becomes the bottleneck; if the real chokepoint stays inside the ISP’s modem, the queue builds there, out of reach.
3. No SQM available? Use plain QoS/bandwidth limiting. Capping your line slightly below its maximum in the router’s QoS settings prevents saturation altogether — cruder than Cake, but it keeps latency flat.
4. Consider replacing ISP-supplied equipment. Provider combo boxes often lack any smart queuing. A router that supports OpenWrt or ships Cake/fq_codel is one of the best upgrades a gamer can make.

Verify the fix

Re-run the stress test after changing settings. The loaded latency should collapse to near-idle levels. Keep LagScope running during your next gaming session with the network busy — the lagspikes that used to appear whenever someone streamed should simply be gone from the event log. If spikes remain even with a quiet queue, the problem is elsewhere: check your Wi-Fi link next, or document the fault for your ISP.