What Is Bufferbloat? The Hidden Cause of Lag

Bufferbloat is when your router gets too greedy with data. It stuffs its memory full of packets instead of sending them right away. The result? Your game lags, your video call freezes — even though your speed test looks fine. You can have 500 Mbps internet and still get terrible latency when someone else is downloading a file. That's bufferbloat, and it's way more common than most people think.

Here's the confusing part. Your speed test will show great numbers. 500 Mbps download, 50 Mbps upload, 8ms ping — all green. But the moment your household starts actually using the connection, latency jumps to 200ms. Calls fall apart. Gaming lag kicks in. The speed test measures your bandwidth. It doesn't measure what happens when multiple devices compete for it at the same time. Bufferbloat only shows up under load.

What a Buffer Is and Why It Causes Problems

Your router uses memory buffers to hold packets when traffic arrives faster than it can send them out. Think of a buffer like a waiting room. When too many people show up at once, they queue up instead of getting dropped. That prevents packet loss during short bursts — which is good.

But modern consumer routers have enormous buffers. They can hold hundreds of milliseconds worth of traffic. Router makers thought "more buffer = fewer dropped packets = better experience." The problem is the side effect. When your connection is full, your video call audio, your game inputs, and your DNS queries all get stuck behind a giant download in the queue. That queue can take hundreds of milliseconds to drain. That's your gaming lag. That's your choppy streaming. That's bufferbloat.

See that chart? A normal idle ping of 12ms shoots up to 350ms the moment a download starts. With SQM active, it stays near 15ms. That difference is everything. It's what separates a clear video call from a robotic one. It's the difference between smooth gaming and lag spikes every time someone loads a YouTube video.

How to Detect Bufferbloat

Quick test (manual)

1. Run a speed test right now and note your ping.
2. Start a large download — a game update, a big file, or a YouTube 4K video at full resolution.
3. While the download runs, run another speed test or keep pinging a server.
4. Compare the ping under load to your earlier baseline.

A jump of more than 30ms under load means you have bufferbloat. A jump of 100ms or more is severe. If your ping goes from 10ms to 250ms the moment a download starts, that's classic bufferbloat.

Dedicated bufferbloat tools

These tools flood your connection on purpose while measuring latency at the same time. That simulates real-world conditions instead of the clean, quiet conditions a standard speed test uses.

What Causes Bufferbloat

• Oversized router buffers: This is the main cause. Budget routers ship with huge buffers. Manufacturers treated packet loss as the enemy without thinking about what large buffers do to latency.
• Cable modem buffers: The equipment at your ISP's end can also buffer traffic aggressively. You can't fix this one — it's outside your home.
• Saturated upload, not just download: Filling up your upload bandwidth causes bufferbloat too. Uploading to Google Drive or using a VPN with heavy upload can degrade your call quality on connections with limited upload.
• Asymmetric connections: Cable and DSL connections with low upload are especially vulnerable. A full 10 Mbps upload queue fills up faster and hurts more than a full 500 Mbps download queue.

How to Fix Bufferbloat

1. Enable SQM (Smart Queue Management)

SQM is the best fix for bufferbloat. It actively manages your router's queue so latency stays low even when traffic is heavy. Instead of letting the buffer fill to the brim, SQM controls how deep the queue gets. It keeps your router from turning into a traffic jam.

The two best SQM algorithms are:

• CAKE (Common Applications Kept Enhanced): The modern standard. It handles both download and upload queuing. It's very effective and doesn't need much processing power.
• FQ-CoDel (Flow Queue Controlled Delay): CAKE's predecessor. Still very effective and widely available. It's the default on OpenWrt routers.

SQM needs router firmware that supports it. Most routers from your ISP don't. Your options are:

• OpenWrt: Free open-source firmware that works on hundreds of router models. It includes SQM with CAKE built in.
• DD-WRT: Another open-source option that supports SQM on some builds.
• IQrouter: A router built specifically to kill bufferbloat. It ships with CAKE already set up.
• GL.iNet routers: These run OpenWrt and support SQM right out of the box.

When you set up SQM, enter your download and upload speeds at about 90–95% of your measured max. This gives SQM room to manage the queue before your connection hits its limit.

2. Enable QoS (Quality of Service)

QoS is a simpler option that most consumer routers already support. It lets you tell your router which traffic gets priority. Video calls and gaming go first. File downloads and cloud backups go last. QoS doesn't eliminate bufferbloat, but it makes sure your latency-sensitive traffic doesn't get stuck behind bulk transfers in the queue.

Look for QoS settings in your router's admin panel. You can usually prioritize by device or traffic type. Prioritizing your work laptop and deprioritizing streaming devices is a common and effective settings change.

3. Rate-limit background traffic

As a workaround, manually cap the speed of apps that hog your connection. Most torrent clients, download managers, and cloud backup services let you set a bandwidth limit. Capping a cloud backup at 5 Mbps instead of letting it run at full speed stops it from saturating your upload and triggering bufferbloat.

4. Upgrade your router

Gaming routers and home office routers are getting better queue management built in. Look for routers that say they support CAKE or FQ-CoDel. Asus, Netgear, and TP-Link's higher-end models have improved their default queue management in recent years.

Bufferbloat by Connection Type