Advanced Bufferbloat Guide

Answer

Bufferbloat is the reason a fast line can feel like a slow one the moment anything uploads. It is caused by oversized send buffers in home routers, and the fix — Smart Queue Management (SQM / CAKE) — is free if your router supports it. This is the single highest-impact upgrade most home gamers can make, and no booster can substitute for it.

7 min readReviewed Jul 2026TTML Editorial
SQM & CAKERouter-level fixAdvanced

Disclosure: We may earn a commission if you purchase through links on this page. This never affects our reviews.

Mental model

Why buffers hurt latency

Bufferbloat — router queue saturation
ClientRouter send queuenew game packet waits behind backlogUplink
When the uplink is saturated, the router's send queue fills up. New packets — including game packets — wait behind the backlog, adding hundreds of milliseconds of latency to an otherwise-fast line.

A router's send buffer smooths bursty traffic. When bulk uploads sustain a full buffer, every subsequent packet — game included — waits behind the backlog. On some ISP-supplied routers this can add hundreds of milliseconds of latency to an otherwise-fast line.

The fix is to stop the queue from ever filling. SQM shapes the outbound rate below the true link capacity and uses fair queueing (fq_codel, and CAKE) to keep latency low for every flow, not just the fastest one.

Diagnose

Test before you change anything

  • Wire in and pause all uploads.
  • Run Waveform bufferbloat test. Record the loaded ping figures.
  • If A / A+, bufferbloat is not your problem — investigate elsewhere.
  • If C / D / F, you have measurable bufferbloat. Continue to the fix section.
  • Repeat the test on Wi-Fi. Any additional latency added is your wireless overhead, not bufferbloat.
Symptom matching

Common bufferbloat patterns

SymptomLikely causeHow to testPossible fix
Ping is fine idle, spikes during any uploadClassic bufferbloat — router send queue overflowsWaveform bufferbloat test — expect C/D/F ratingEnable SQM/CAKE and set upload/download limits at ~90-95% of measured line speed
Ping is fine idle, spikes when a family member is on video callBufferbloat plus concurrent-flow contentionWaveform under 'medium' plan presetSQM/CAKE with per-host isolation — this is what CAKE was built for
Ping is bad even when nothing is uploadingNot bufferbloat — investigate ISP transit, hardware, or Wi-FiRun a wired continuous ping with all uploads pausedTraceroute; contact ISP; consider routing only after eliminating your line
Fix

Enable SQM / CAKE

  1. Confirm your router supports SQM. OpenWrt, ASUS-Merlin, EdgeOS, MikroTik and pfSense/OPNsense do; most stock ISP routers do not.
  2. Measure your actual line speed wired (not the marketing number). Use a wired browser speed test at an idle time.
  3. In your router's SQM/QoS settings, set upload and download limits to 90-95% of measured speed.
  4. Choose CAKE as the queueing discipline where available. Otherwise fq_codel.
  5. Re-run Waveform. Target A / A+. Adjust the shaping limits down 5% if you still see loaded latency.
FAQs

Common bufferbloat questions

What is bufferbloat and why does it hurt gaming?
Bufferbloat is the latency added when your router's send queue fills up under load. On many ISP-supplied routers, a single upload can push your gaming ping from 25 ms to 300 ms because game packets queue behind the backlog. It is the single most common invisible cause of 'my ping is fine when idle but terrible in matches'.
How do I test for bufferbloat?
Use Waveform's Bufferbloat Test in a browser — it measures ping under simultaneous upload and download load. An A or A+ rating means bufferbloat is not your problem. C, D or F means you need Smart Queue Management (SQM / CAKE).
What is SQM/CAKE?
Smart Queue Management is a family of algorithms that prevent the router's send queue from ever filling to the point of adding latency. CAKE is the current best-in-class implementation, available in OpenWrt, most ASUS-Merlin firmwares, EdgeOS, MikroTik and pfSense/OPNsense.
Will a game booster fix bufferbloat?
No. Bufferbloat happens on your side of the modem — before any external routing decision. A booster cannot see or fix your own outbound queue. SQM is the specific tool for bufferbloat; a booster is the specific tool for upstream ISP transit problems.