What Is Bufferbloat, and Why Fast Internet Still Feels Slow
A fast connection that feels slow under load usually isn't your internet plan. It's bufferbloat, a latency problem hiding in oversized router queues, and it's fixable.
Your speed test says 500 megabits down. Your video call still stutters the moment someone else in the house starts a cloud backup. That gap, a fast connection that feels slow under real load, usually isn't your internet plan. It's a two-decade-old networking problem with an odd name: bufferbloat.
The buffers that are supposed to help you
Every router and modem holds a memory buffer to store data packets that can't be sent out immediately. That's normal and necessary; without any buffer, a network would drop data the instant traffic spiked. The trouble starts when those buffers are too large and poorly managed. Instead of sending packets promptly or dropping the ones it can't handle, a bufferbloated router keeps stuffing more data into an ever-growing queue.
Jim Gettys and Kathleen Nichols, the researchers credited with formally identifying the problem around 2010, described it as the existence of excessively large and frequently full buffers inside the network
, in an account cited by the networking firm Preseem. Gettys went on to co-found the bufferbloat.net project with developer Dave Taht, whose work on fixing it became one of networking's more quietly influential side projects.
Why does bufferbloat make video calls and games lag specifically?
Because those applications need low latency, not raw throughput. A large file, whether a photo backup, a big download, or an operating system update, can fill the upload or download queue with hundreds of packets. Your Zoom audio or a game's input data gets stuck behind all of it, waiting its turn, according to the tech outlet MakeUseOf. Latency that would normally sit at 15 milliseconds can spike to 200, 500, or over 1,000 milliseconds while the queue drains, enough to turn a clean video call into a choppy one, even though the speed test taken moments earlier showed nothing wrong.
TCP, the protocol that carries most internet traffic, makes the problem worse on its own. It learns how many packets a network can absorb before dropping one, then deliberately keeps that many packets in flight to avoid losses, creating what engineers call a standing queue that adds delay to every packet for as long as the connection stays busy.
How to actually check if it's happening to you
Standard speed tests won't catch it, because they mostly measure throughput, not latency under load. The tool built specifically for this is the Waveform bufferbloat test, which measures your baseline "idle" latency, then saturates the connection with simultaneous uploads and downloads and tracks how far latency climbs. A grade of A means your connection holds steady under load; anything below a C points to real bufferbloat.
How do I fix bufferbloat on my own router?
The standard fix is Smart Queue Management, sometimes just labeled QoS in a router's settings. SQM uses an algorithm called FQ-CoDel — Fair Queuing Controlled Delay — to keep queues short on purpose, isolating bulk downloads from latency-sensitive traffic like calls and games so one doesn't crowd out the other. Not every consumer router ships with SQM built in; where it's missing, third-party firmware like OpenWrt can add it on supported hardware. When you enable it, set the router's WAN speed a notch below your actual measured line speed (on a 100 Mbps down / 20 Mbps up connection, something like 95 and 18) so the router controls the queue instead of your ISP's equipment further upstream.
What it isn't
Bufferbloat is easy to confuse with ordinary video buffering, the spinning wheel on a slow stream, but the two are unrelated. Streaming buffering means not enough data is arriving fast enough to keep playback going; bufferbloat means plenty of data is arriving, just stuck behind an oversized queue that adds delay to everything sharing that link. Wi-Fi interference and an overloaded router juggling too many connected devices can produce similar-looking lag spikes with none of the same fix, which is why testing over a wired Ethernet connection first is the more reliable way to isolate the cause before blaming your ISP, your router, or the household member currently backing up four years of phone photos to the cloud.
