What Is Bufferbloat?

Bufferbloat is the excess latency and jitter that shows up when your internet connection gets busy — during a big download, a cloud backup, or when someone else in the house starts streaming. Your connection can be blazing fast on paper yet feel laggy the moment it is under load, because oversized buffers inside your router queue up packets and make everything wait. This guide explains what bufferbloat means, why it ruins gaming and video calls even on fast plans, what causes it, how to test for it with an idle-versus-loaded ping comparison, and how to fix it. You can spot it in seconds with a free speed test.

Bufferbloat meaning: latency that spikes under load

Bufferbloat is what happens when network equipment uses buffers that are far too large. A buffer is a small holding area for packets waiting their turn to be sent. Buffers are useful in small doses — they smooth out brief bursts of traffic. But when a buffer is oversized and the link is fully saturated, packets do not get dropped (which is the network's normal signal to slow down). Instead they pile into a huge queue and sit there.

The visible symptom is simple: your ping is low when the line is idle, but it shoots up — sometimes from 15 ms to 300 ms or more — the instant a download or upload fills the connection. That delay is bufferbloat. The bandwidth (your Mbps) might be exactly what you pay for, but the responsiveness falls apart under load.

A plain-English analogy: the oversized on-ramp

Imagine a single-lane highway exit. Normally a few cars roll through instantly. Now imagine engineers added a queue so long it can hold a thousand cars before anyone is turned away. The moment a flood of traffic arrives — your big download — the queue fills end to end. A new car (a time-sensitive game packet or a word in your video call) joins the back and has to crawl past all thousand cars before it reaches the exit.

That waiting line is the oversized buffer. It does not lose any cars, so throughput looks fine, but every car now takes far longer to get through. A smaller, smarter queue would wave most cars through quickly and only briefly delay the bulk traffic — which is exactly what the fixes below do.

Why it ruins gaming and calls even on a "fast" connection

People assume a 500 Mbps or gigabit plan guarantees a smooth experience. It does not. Bufferbloat is about delay, not bandwidth, so a fast connection with bad bufferbloat can be worse for real-time apps than a slower one with none.

• Gaming — your inputs and the server's updates are tiny packets, but they get stuck behind a bulk transfer in the bloated queue. You see lag spikes, rubber-banding and delayed hit registration the moment any download starts. See what a good ping for gaming is.
• Video calls — audio and video need steady, low latency. Bufferbloat causes the choppy, robotic, frozen-frame calls that strike right when someone else hits the internet hard.
• Web browsing — even loading a page feels sluggish during an upload, because the requests queue behind the bulk traffic.

What causes bufferbloat?

Two ingredients have to come together:

• Oversized buffers — many routers, modems and ISP gateways ship with buffers that are far larger than they need to be. Manufacturers oversize them to avoid packet loss in benchmarks, but big buffers trade latency for that loss.
• A saturated link — bufferbloat only appears when the connection is full. A large download fills your download direction; a cloud backup, video upload or torrent fills the upload direction. Asymmetric plans with small upload (common on cable) are especially prone to upload bufferbloat.

Put them together and any saturating transfer floods the oversized buffer, the queue grows, and latency for everything else balloons. This is why your ping can read perfectly until the exact moment the line gets busy.

How to test for bufferbloat: idle vs loaded ping

The whole test is a comparison. You measure ping when the connection is idle, then measure ping again while the connection is saturated with a download or upload. The difference is your bufferbloat.

1. Make sure nothing else is using the internet, then note your idle ping.
2. Start a transfer that fills the line — a large download or upload, or a speed test that loads the connection — and watch the loaded ping at the same time.
3. Subtract idle from loaded. The bigger the jump, the worse the bufferbloat.

Here is how to read the result:

As a rule of thumb, an increase under about 30 ms is fine, 30 to 100 ms is worth fixing, and over 100 ms is a clear bufferbloat problem. Note that download and upload can behave very differently, so it is worth checking both — see our results explained guide for how each number relates.

How to fix bufferbloat

Bufferbloat is highly fixable, and you usually do not need a faster plan — you need a smarter queue. The real solution is Smart Queue Management (SQM), which replaces the dumb oversized buffer with a modern algorithm that keeps the queue short and shares it fairly.

• Enable SQM with fq_codel or CAKE — these are the proven algorithms that defeat bufferbloat. CAKE is the newer, more capable option; fq_codel is excellent and widely supported. Many routers expose these under a "SQM" or advanced QoS menu.
• Run OpenWrt — the open-source router firmware OpenWrt includes first-class SQM with both fq_codel and CAKE, and is the most reliable way to get them if your stock firmware lacks them.
• Set the bandwidth limit slightly below your plan — SQM only controls the queue if your router is the bottleneck, not your ISP. Set the SQM limit to roughly 85 to 95 percent of your real download and upload speed so the queue forms in your router, where the smart algorithm can manage it. Use a speed test to find your true throughput first.
• Use built-in QoS — many consumer and gaming routers include QoS or "anti-bufferbloat" / "adaptive QoS" modes. Turn it on and set your line speed accurately.
• Upgrade an old router — very old or low-end hardware may lack the CPU to run SQM at high speeds. A capable modern router (or a dedicated gaming router with good QoS) solves both the buffer sizing and the processing headroom.

After any change, re-run the idle-versus-loaded comparison. A correctly configured fq_codel or CAKE setup typically holds the loaded ping within a few milliseconds of idle — the lag spikes simply disappear. For more on keeping latency low in general, see how to lower your ping.

Test your connection under load now

The quickest way to know whether bufferbloat is hurting you is to watch your latency while the line is busy. Run a free SpeedSnap speed test to see your download, upload, ping and jitter in about 30 seconds — no app and no sign-up. Compare your idle and loaded ping, then apply the SQM fixes above and test again to confirm the spikes are gone.

Frequently Asked Questions

What is bufferbloat?

Bufferbloat is excess latency and jitter that appears when your internet connection is saturated, such as during a large download or upload. Oversized buffers inside your router or modem queue up too many packets, so each one waits in a long line. The result is a connection that benchmarks fast but feels laggy whenever it is busy.

What causes bufferbloat?

Bufferbloat is caused by oversized network buffers combined with a saturated link. When your upload or download fills the connection, packets pile up in an overly large buffer in the router or modem instead of being dropped, creating a long queue. Every packet, including small time-sensitive ones for games and calls, has to wait behind that queue, which spikes latency.

How do I test for bufferbloat?

Compare your idle ping to your loaded ping. First measure ping while the connection is doing nothing. Then run a download or upload that saturates the line and measure ping again at the same time. If the loaded ping is far higher than the idle ping, you have bufferbloat. A rise of more than about 100 ms under load is a clear sign.

How do I fix bufferbloat?

The proper fix is Smart Queue Management (SQM) using a modern algorithm like fq_codel or CAKE on a capable router, often running OpenWrt or built-in QoS. SQM works best when you set its bandwidth limit slightly below your real plan speed so the router, not your ISP, controls the queue. Upgrading an old router or using a gaming router with good QoS also helps.

Why does my ping spike when I download something?

That is classic bufferbloat. A big download fills your connection and packets back up inside an oversized buffer, so your ping climbs from a low idle figure to hundreds of milliseconds. Games, video calls and even web pages then feel laggy because their small packets are stuck behind the bulk transfer.

Why do I lag when someone else uses the internet?

When another device starts a large download, upload or video upload, it can saturate your shared connection. Without Smart Queue Management, the oversized buffer fills and everyone's latency spikes, so your game or call lags even though the other activity is not yours. Enabling fq_codel or CAKE SQM keeps latency low for everyone by sharing the queue fairly.