Question 1

What exactly is bufferbloat?

Accepted Answer

Bufferbloat is the latency spike that appears when a network link is saturated and its queues fill up faster than they drain. Routers and modems buffer packets to avoid drops, but oversized buffers hold thousands of packets in line — meaning every new packet, including your ping, has to wait its turn behind a queue of bulk traffic. The result: your idle ping of 20 ms can balloon to 500 ms or more the instant someone starts a download, killing video calls and competitive gaming.

Question 2

How does this three-phase test reveal it?

Accepted Answer

Phase one pings for five seconds on an idle link to establish a baseline. Phase two starts a parallel download to saturate the downlink while continuing to ping every 200 ms. Phase three repeats with an upload flood. The grade compares loaded ping against the idle baseline: under 30 ms of lift earns an A, 30–60 ms a B, 60–200 ms a C, and anything beyond that fails. Most consumer routers without modern queue management land in C or worse.

Question 3

How do I fix bufferbloat at home?

Accepted Answer

Enable Smart Queue Management (SQM) — often labelled fq_codel, CAKE, or Adaptive QoS — on your router. OpenWrt, pfSense, and most recent ASUS/Ubiquiti firmwares ship it. Set the upload and download caps to roughly 85–95% of the speeds you measured on /network/speed; that small headroom is what lets the router actually control the queue rather than handing it off to the ISP's modem. Re-run this test afterwards — a properly tuned SQM connection holds latency lift under 20 ms even at full throttle.

Question 4

Why does upload saturation cause more bufferbloat than download?

Accepted Answer

Cable and DSL uplinks are typically far slower than downlinks, and the modem's upload buffer is usually the deepest queue in the path. A single cloud backup or video upload can pin the uplink at 100% for minutes, and every TCP ACK from your downloads has to fight through that same congested queue — which is why your downloads also slow down during a big upload. Symmetric fibre helps, but only if SQM is enabled.

Question 5

How does this relate to your speed and latency tools?

Accepted Answer

/network/speed measures capacity on an empty link — the marketing number. /network/latency tracks idle ping stability over time. Bufferbloat is the missing third leg: it asks what happens when capacity meets reality. A gigabit connection with severe bufferbloat is worse for real-time apps than a 50 Mb/s connection with good queue management. Always run all three before blaming your ISP.

Question 6

Does the test work behind a VPN?

Accepted Answer

It runs, but the numbers reflect the VPN tunnel and the VPN provider's exit-node queues, not your home link. For an honest reading, disconnect the VPN first. If you specifically want to compare VPN-on versus VPN-off latency under load, run the test twice and keep a screenshot of each — the difference is usually striking.

Bufferbloat.