How to Fix Bufferbloat: Step-by-Step SQM Guide

How to fix bufferbloat: first prove which queue is causing loaded latency, then configure SQM, CAKE or shaping limits without sacrificing more speed than necessary. Retest under load after every change.

Loaded-latency troubleshooting guide

Find and Control the Queue Causing Lag

Prove whether upload, download, Wi-Fi or router queues are causing the delay, then apply the smallest SQM or traffic-control change that improves the wired result.

Bufferbloat troubleshooting illustration showing a busy router queue and controlled loaded latency

Start here

The fastest bufferbloat fix workflow

Do not begin with router shopping or random QoS rules. Use one wired test to identify the loaded direction, make one controlled change, then repeat the same test.

Instant SQM target calculator

Calculate a safe first shaping limit

Enter repeatable wired speeds rather than the single highest result. The calculator produces starting download and upload limits for the router.

These are starting values, not guarantees. Retest loaded latency after every change and reduce the affected direction further when spikes remain.

Suggested starting values

Download limit
Upload limit

Enter repeatable wired speeds and choose a percentage.

Why does shaping below line rate reduce bufferbloat?

The router can manage delay only when its queue becomes the controlled bottleneck. Setting the managed rate slightly below the real connection rate prevents a modem, radio link or provider-side queue from filling first. For the deeper queueing explanation, read What Is Bufferbloat?

1

Run the live test over Ethernet

Pause backups, downloads and VPNs. Record idle, download-loaded and upload-loaded latency.

2

Find which queue fills

Upload worst points to the smaller upstream path; download worst points to ingress or downstream queueing.

3

Shape, retest and keep evidence

Start below stable line rate. Keep the setting only when latency improves without excessive speed loss.

Quick reference

Match the loaded-latency result to the next action

This replaces separate symptom and cause lists. Start with the pattern that matches the completed test.

Idle ping is good, upload load is bad

The upstream path is filling. Cloud backup, CCTV, file sync or a speed-test upload can delay calls and gaming packets.

Next: cap upload traffic or apply egress SQM first.

Idle ping is good, download load is bad

The downstream path or router ingress queue is building delay while large downloads arrive faster than the managed rate.

Next: shape download below stable throughput and retest.

Wi-Fi is poor, Ethernet is good

Wireless airtime, retransmissions, weak signal or mesh backhaul is adding delay before traffic reaches the broadband queue.

Next: fix Wi-Fi rather than replacing the broadband package.

Both loaded directions are poor on Ethernet

The router may lack queue-management capacity, the shaping rate may be too high or an external queue may be filling first.

Next: lower both limits, check CPU load and verify the overhead preset.

Idle ping is already high

This is not a pure bufferbloat pattern. Server distance, VPN routing, Wi-Fi delay, DLM, congestion or provider routing may be raising the baseline.

Next: use the high-ping guide before tuning SQM.

Packet loss appears with the latency rise

Queue overflow, Wi-Fi instability, damaged cabling or a line fault may be dropping packets as well as delaying them.

Next: run the packet-loss test over Ethernet and Wi-Fi.
↑ Back to guide index

Test in order

Prove where the queue starts

Keep the same device, cable and test method. Changing several variables together makes the result difficult to interpret.

  1. Record the quiet wired baseline.

    Connect directly to the router, pause household traffic and note idle latency, jitter and packet loss.

  2. Run the download and upload phases.

    Use the LinkSpeed bufferbloat test and record the added latency for each direction rather than looking only at headline speed.

  3. Pause upload-heavy services.

    Stop cloud backup, camera uploads, livestreaming and file synchronisation. A large improvement identifies upstream contention.

  4. Compare Ethernet and Wi-Fi.

    A good wired result with a poor wireless result moves the fault boundary to signal, interference, roaming or mesh backhaul.

  5. Enable one queue-management mode.

    Use CAKE, FQ-CoDel or the strongest genuinely rate-aware QoS mode available. Avoid stacking several prioritisation systems.

  6. Retest at the same limits.

    Repeat the test after each rate or overhead change and save the result that gives the best balance of latency and throughput.

Do not judge bufferbloat from average ping alone. Compare idle latency with the added download and upload latency, and check the high-percentile spikes shown by the test.

↑ Back to guide index

SQM settings

Choose a safe shaping starting point

These are starting ranges, not universal final values. Use repeatable wired throughput and lower the limit until the managed router queue remains in control.

ConnectionStarting pointQueue optionImportant check
FTTP / full fibreStart around 90–95% of stable wired throughput.CAKE where supported; FQ-CoDel is a capable alternative.Account for PPPoE if used and confirm the router CPU can shape at the package speed.
FTTC / VDSL2Start around 85–92% of stable sync or wired throughput.CAKE or FQ-CoDel.Use the closest VDSL/PTM overhead preset and avoid repeated modem reboots during testing.
Cable / DOCSISStart upload lower than download; 85–90% is a practical first test.CAKE, FQ-CoDel or effective rate-aware QoS.Variable upstream capacity can require a more conservative upload limit.
5G home broadbandShape against the lower repeatable rate, not the best speed-test burst.Adaptive SQM where available.Radio rate changes can move the bottleneck outside the router, especially at peak times.
Locked ISP hubUse device limits or basic QoS if no rate-aware mode exists.Vendor QoS may help, but generic priority labels are not the same as SQM.Bridge/modem mode plus a capable router may be needed after wired proof.

CAKE

Combines flow isolation, fairness and overhead handling. It is useful where the router has enough CPU and the firmware exposes correct line settings.

FQ-CoDel

Separates traffic into flows and controls queue delay with less processing overhead. It remains a strong option when CAKE is unavailable.

Traditional QoS

App or device priority can help, but it will not control an external queue unless the router also shapes below the real bottleneck rate.

Overhead preset

Ethernet, PPPoE, VDSL and PTM framing consume capacity. An incorrect preset can let the modem or provider queue fill before SQM takes control.

↑ Back to guide index

Router and line paths

Use the path that matches your router or UK provider hub

Open only the route that matches your hardware. Provider voice services, authentication and support requirements can affect whether a third-party SQM router can replace the supplied hub.

Provider-supplied hub

Start with the model-specific route for Virgin Media, BT/EE or Sky. Bridge, modem and direct-ONT options are not interchangeable.

Open UK provider hub routes ↓

OpenWrt or ASUS

Use CAKE, FQ-CoDel or the strongest rate-aware mode supported by the exact router and firmware.

Open firmware routes ↓

Gigabit, cable or 5G

Check router CPU headroom and use a shaping rate based on repeatable capacity rather than the fastest burst.

Open high-speed routes ↓
Standard ISP router or hub

Look for Smart Queue Management, adaptive QoS, bandwidth control or per-device upload limits. Use one feature at a time and verify the result with the same loaded-latency test.

Useful labels include SQM, CAKE, FQ-CoDel, Adaptive QoS, Bandwidth Control and Game or Call Priority. Priority labels alone are not a substitute for rate-aware shaping.

Virgin Media Hub 3, 4 or 5

Virgin Media provides modem mode on Hub 3, Hub 4 and Hub 5. Connect to the hub, open 192.168.0.1, sign in with the settings password printed on the hub, then enable Modem Mode. Once active, the hub management address changes to 192.168.100.1.

Connect the third-party SQM router after the hub has restarted, then run the same wired bufferbloat test. Virgin Media states that modem mode is not currently available on Hub 5x, so use the model-specific provider route instead of assuming the same steps apply.

Check Virgin Media's current modem-mode instructions or open the LinkSpeed Virgin Media guide.

BT Smart Hub 2 or EE hub on Openreach

Do not copy BT Business bridge-mode instructions onto a residential hub. On Openreach FTTP, a compatible router may connect to the ONT when the provider's authentication and Digital Voice requirements allow it. On FTTC or VDSL, a compatible modem or modem-router is still required.

Keep the supplied hub available for fault diagnosis and voice services. Before replacing it, confirm the WAN authentication method and whether the phone service depends on the provider hub.

Check BT's current Full Fibre hub instructions or use the LinkSpeed BT guide.

Sky Broadband Hub, Sky Max Hub or Gigafast+ Hub

Sky's consumer hub controls expose Wi-Fi, DMZ, port-forwarding and related advanced settings, but replacing the hub is not a simple universal bridge-mode procedure. A direct third-party-router setup can depend on the access technology and Sky authentication method, and Internet Calls or support may be affected.

For a low-risk test, keep the Sky hub in service and use the new device as an access point first. Use a router-behind-router or direct-ONT configuration only after checking the exact Sky product, authentication support and double-NAT impact.

Check Sky's current hub-settings guidance or use the LinkSpeed Sky guide.

OpenWrt with CAKE or FQ-CoDel

Disable software or hardware flow offloading if it bypasses the active queue discipline. Check that CAKE or FQ-CoDel is attached to the correct interface and that the configured rate is below the real bottleneck.

tc -s qdisc show top cat /proc/interrupts

During a wired loaded test, watch for a queue backlog that remains large or one CPU core reaching sustained saturation.

ASUS or Asuswrt-Merlin QoS route

Use the strongest rate-aware mode available on the exact router and firmware. Enter repeatable wired upload and download values from the calculator above, disable conflicting acceleration only when the firmware requires it, then compare loaded latency before and after.

Model support varies. Do not assume that every ASUS router exposes CAKE or that an Adaptive QoS preset controls the bottleneck as effectively as SQM.

Gigabit FTTP and router CPU limits

At high packet rates, SQM can become CPU-bound before the line reaches full speed. A result that improves latency but caps throughput well below the configured rate may indicate processor limits rather than an incorrect percentage.

Change one setting at a time and avoid combining experimental packet steering with hardware offload while diagnosing.

Variable cable or 5G rates

A fixed shaping rate only works while it stays below the real bottleneck. Cable upstream and 5G radio capacity can vary by time and load, so use a conservative rate based on repeated lower results or adaptive shaping where supported.

Provider settings change. Check the current provider instructions before disabling the supplied hub, and keep a record of the original cabling and settings so the supported configuration can be restored.

↑ Back to guide index

Gaming and consoles

Bufferbloat fixes for PS5, Xbox and PC gaming

Console network settings cannot remove an unmanaged broadband queue. Control the queue first, then use device priority only as a secondary refinement.

Do not confuse NAT fixes with latency fixes

A static local IP, port forwarding or a more open NAT type can help connectivity, but none of them prevents upload or download queues from delaying game packets.

Shape before prioritising the console

Enable effective SQM and set the real line limits first. Add console or gaming-device priority only after the loaded test proves the managed queue is working.

Test with real household pressure

Run the game or cloud-gaming session while another device starts a download and an upload. A stable result under controlled load is more useful than a quiet late-night test.

↑ Back to guide index

Verify the change

A fix is successful only when the same test improves

Measure the result, not the setting name.

Keep the change

Confirmed when: loaded latency falls substantially in both directions, jitter is steadier and real-time apps remain responsive.

Check: throughput loss is acceptable for the household.

Lower the rate further

Use when: latency improves slightly but one loaded phase still spikes.

Check: reduce the affected direction in small steps and repeat.

Undo the change

Use when: speed falls sharply without a meaningful latency improvement or the router becomes unstable.

Check: restore the last known-good configuration.

Investigate another layer

Use when: idle ping, packet loss or Wi-Fi remains poor even with the line quiet.

Check: use the high-ping, packet-loss or unstable-Wi-Fi guide.

↑ Back to guide index

Provider escalation

When the problem is not controlled by the home router

Contact the provider when repeatable Ethernet tests remain poor with household traffic paused and a correctly configured router cannot keep the external path responsive.

Evidence to collect

Date and time, wired connection, idle latency, added download and upload latency, jitter, packet loss, measured speeds and the router/SQM settings used.

Strong provider-side pattern

The router gateway stays stable, but public loaded latency or loss repeatedly worsens at similar peak times across more than one service.

Ask for a latency or congestion investigation, not just a speed retest. Explain that the fault remains on Ethernet with local traffic paused and include comparable quiet-time and peak-time results.

Copy a clear support message

Edit the bracketed values before sending. This reports the evidence without assuming the provider is definitely at fault.

↑ Back to guide index

Focused answers

Bufferbloat fix FAQs

These answers match the FAQ structured data in the page head.

What is the quickest way to fix bufferbloat?

Run a wired bufferbloat test, identify whether upload or download load causes the largest latency rise, then enable effective SQM or QoS and shape the connection slightly below the stable measured rate. Retest after each change.

Should SQM be set to 90 percent of line speed?

Around 90 to 95 percent of stable wired throughput is a useful starting point for many fixed connections, but the correct value depends on the access technology, router CPU and how variable the line rate is.

Is CAKE better than FQ-CoDel?

Both can control queueing delay. CAKE combines flow isolation, fairness and overhead handling in one system, while FQ-CoDel is lighter and widely supported. Router capability and correct shaping matter more than the label alone.

Can full fibre still have bufferbloat?

Yes. FTTP removes the copper access-line bottleneck, but queues can still form in the router, Wi-Fi link, Ethernet interface or provider path when traffic reaches the available rate.

Why is upload bufferbloat often worse?

Many broadband packages have much less upload than download. Cloud backup, CCTV, file synchronisation and livestreaming can therefore fill the upstream path quickly and delay acknowledgements, calls and gaming packets.

When should I replace the router?

Replace or supplement the router only after a wired test confirms poor loaded latency and the current hub lacks effective SQM, cannot sustain the required throughput or still performs badly after correct shaping.

↑ Back to guide index
How LinkSpeed tests and checks claims