How to Actually Fix Bufferbloat: The Router-by-Router Guide

Bufferbloat is almost always fixable in 20 minutes, on hardware you already own, for $0. The one-line version is: enable a queue manager called CAKE (or failing that, FQ-Codel) on your router, set the shaping limit to about 90% of your measured line speed, verify the fix with a continuous monitor. The rest of this page is the per-router specifics, the common mistakes, and how to tell when you're actually done.

1. Diagnose first, fix second

Before touching anything, confirm that bufferbloat is actually your problem. A lot of "my internet is slow" is really Wi-Fi congestion, DNS, or a neighbor hammering a shared segment. Bufferbloat has a specific signature: idle latency looks fine, loaded latency spikes, and the spike correlates perfectly with anyone in the house hitting play on something big.

The direct test is a loaded-latency measurement. Start a sustained download and ping a nearby server at the same time. The difference between your ping during the download and your ping when the link is quiet is the bufferbloat grade. Under 30 ms is clean. Over 100 ms is a problem you will feel on every video call, every game, every page that loads while someone else is streaming. Y2KDASH measures this continuously so you can watch the shape of it instead of catching a single moment; waveform.com/tools/bufferbloat runs a one-shot version.

2. Know your real throughput (not your plan number)

Every fix below needs a number: your actual sustained download and upload in Mbps. Not the plan sticker, not the Wi-Fi number, not the last Ookla peak — the number your router actually sees coming in and going out on a wired client during a 5-second-or-longer saturated test, repeated a few times.

Record both. Most residential plans are asymmetric (e.g. 500 down / 20 up), and bufferbloat on the upload side is often worse because the upstream pipe is smaller and buffers fill faster. Set aside both numbers — you'll plug them into the router.

3. The fix, by router type

Below is the practical matrix. If your router isn't in the list, the trick is the same one everywhere: find a menu that says any of SQM, CAKE, FQ-Codel, Adaptive QoS, or Smart Queue, enable it, and set the ingress/egress limits to roughly 90% of your measured line speed. If none of those words appear in the firmware, skip to the "no-knobs router" section.

OpenWRT (the gold standard)

OpenWRT's sqm-scripts with the cake queue discipline is the reference implementation. Everything else on this page is a compromise with it. Setup in the LuCI web UI:

1. Install the sqm-scripts and luci-app-sqm packages (opkg install luci-app-sqm).
2. Go to Network → SQM QoS. Add a rule on your WAN interface.
3. Queue discipline: cake. Queue setup script: piece_of_cake.qos.
4. Download limit: 90% of measured download. Upload limit: 90% of measured upload. Both in kbit/s.
5. Link layer adaptation: Ethernet for fiber or cable with a separate modem; ATM for DSL; DOCSIS on DOCSIS if available.
6. Save + Apply. Reboot the WAN connection.

That's it. On a 300/25 cable plan this typically reduces loaded latency from ~250 ms over idle to under 5 ms over idle. The CPU cost on a modern ARM router (GL-MT3000, GL-AXT1800, anything with a dual-core Cortex-A53 at 1+ GHz) is negligible up to a few hundred Mbps. Above 500 Mbps you want hardware with a faster CPU — the common pattern is an x86 mini-PC running OpenWRT or a Banana-Pi-class board.

ASUS routers with stock firmware

Since 2018 most ASUS RT-* routers ship with Adaptive QoS, which is a Trend Micro signature-based classifier plus a shaper. It's not CAKE, but it is useful. Settings:

1. Adaptive QoS → QoS → Enable QoS: On.
2. QoS Type: Adaptive QoS.
3. Download bandwidth: 90% of measured download. Upload bandwidth: 90% of measured upload.
4. Priority: set "Web Surfing" or "Gaming" higher than "File Downloading" — this is the actual queue-priority behavior. Default order is usually fine.

Caveat: Adaptive QoS uses deep packet inspection, so it reduces max throughput slightly on the highest plans. On gigabit fiber the cost is real; on anything under 500 Mbps you won't notice.

ASUS routers with Asuswrt-Merlin (recommended)

Asuswrt-Merlin is a maintained, mostly-stock fork of ASUS firmware that unlocks proper CAKE via the FreshJR_QOS / CAKE-QoS scripts on the Diversion + Scribe / scripts entware stack. On a supported RT-AX86U / RT-AX88U / GT-AX6000 this is as close to OpenWRT's performance as you get without giving up the ASUS UI. Install Merlin, then follow the FreshJR CAKE guide.

pfSense / OPNsense

Use the FairQ + CoDel shaper, or install the CAKE port. pfSense 2.7+ has native CAKE in the traffic shaper wizard. Run the wizard, pick CAKE, set ingress/egress to 90% of measured line speed, done. On OPNsense the same thing is at Services → Traffic Shaper → Pipes.

Ubiquiti EdgeRouter / UniFi

EdgeRouter (ER-X, ERLite, ER-4) supports FQ-Codel natively and CAKE via the shell, but the UniFi Dream Machine line historically doesn't expose queue management in the GUI. On a UDM / UDM-Pro / UDM-SE the workaround is shell-level tc commands after every firmware update. If you're on UniFi, consider whether an EdgeRouter or an OpenWRT box in front of your UDM is the pragmatic move.

TP-Link, Netgear Nighthawk, Linksys (stock firmware)

Most of these expose a "QoS" menu that does not do CAKE. It's usually a priority-by-device or priority-by-port system that ties tightly to the router's chipset shaper. The honest assessment is: it helps, it does not fix the problem. If the menu is there, set your line speeds, set priority for gaming/voice devices, and measure. If the delta is still over 50 ms loaded vs. idle, you are up against the firmware's limit.

The paths from here are: flash OpenWRT if your model is supported, replace with a GL.iNet or EdgeRouter, or put an OpenWRT box in series between your ISP device and your existing router.

ISP-supplied gateways (Xfinity xFi, AT&T BGW, Verizon Fios)

Short version: these almost never support CAKE or real SQM. The standard fix is bridge mode (or AT&T's IP-passthrough) with your own CAKE-capable router behind it. On Xfinity xFi this is on the Admin Tool at 10.0.0.1 → Gateway → At a Glance → Bridge Mode. On AT&T BGW210 / BGW320 it's in Firewall → IP Passthrough. On Verizon Fios Gateway it's in Advanced → Network Settings → Network Connections → Broadband → Settings.

You lose the ISP's mesh / 2.4-5-6 GHz Wi-Fi, but you gain a router you can actually tune. This is by far the most common upgrade path.

The "no-knobs" router (Apple AirPort, Google Nest Wifi, Eero)

Apple AirPort is discontinued and has no knobs. Google Nest Wifi has basic device prioritization but no CAKE. Eero Pro 6/6E offers "Eero Plus" which is not queue management. For bufferbloat, these platforms require the same fix as the ISP case: put a real router in front, run the no-knobs device in AP-only mode (Eero "Bridge Mode"; Nest Wifi disable gateway).

4. The most common setup mistakes

• Shaping to the plan speed instead of the measured speed. Your ISP delivers less than the plan number during peak hours. If your shaper is set to the plan, the real bottleneck is upstream, outside your queue. Set to 90% of measured.
• Only shaping download. Upload bufferbloat is usually worse and is what kills calls / uploads / screen-sharing. Both directions need limits.
• Wrong link-layer setting. On DSL, skipping ATM accounting costs you 8-15% of effective throughput. On DOCSIS, picking DOCSIS overhead is a small but free win.
• Running CAKE on a CPU that can't keep up. If your router's CPU pegs at 100% during a saturated download, you'll cap below your line speed. Check CPU load during a 5-second test; replace the router if it can't handle your plan.
• Putting the shaper on the wrong interface. SQM goes on the WAN interface (the one facing your modem/ISP), not on the LAN or a wireless interface.

5. Verify the fix

Immediately after enabling CAKE, run a loaded-latency test for at least 10 continuous minutes. You want to see:

The continuous-monitoring view on y2kdash is the fastest way to confirm. Put it on a second monitor, trigger a few family-style mixed workloads (Netflix + Zoom + a big download), and watch the loaded-latency line. With CAKE correctly configured, the line stays flat.

6. If it's still broken after CAKE

Three things to check, in order:

1. Are you still behind an ISP gateway? If so, your CAKE is only shaping the link between your router and the gateway. The gateway's own queue is still producing bufferbloat. Bridge mode.
2. Is your Wi-Fi the actual bottleneck? On a crowded 2.4 GHz band, airtime contention produces effects that look like bufferbloat but live in the AP, not the WAN. Test with a wired client to isolate.
3. Is your upload cap realistic? Cable upload plans frequently deliver well below the sticker number. Re-measure during peak hours and reset the upload limit.

7. FAQ