This is one of the most frustrating situations: you have a 200 Mbps plan, the speed test shows 18 ms ping, and yet your character rubber-bands and shots register late, precisely when someone else at home starts watching YouTube or downloading a file.
The ping most speed tests show is measured while the line is quiet. Nobody games on a quiet line. What actually matters is what happens to ping when the line is busy, and that is where bufferbloat comes in.
What is bufferbloat, in plain terms?
Your router has a small memory (a buffer) where data waits its turn to go out. When the line is saturated by a large download, that buffer fills up. Your game's small packet, carrying your movement and your shot, joins the back of the queue behind thousands of download packets.
Picture a single cashier in a supermarket with someone ahead of you pushing a full trolley. You only have a bottle of water, but you wait just as long. In a router that wait can reach 200 or 500 ms, while a game needs your packet to arrive in under 50.
How do you know this is your problem?
Run the speed test and look at three numbers: idle ping, latency during download, and latency during upload.
| Increase over idle ping | What it means |
|---|---|
| Under 30 ms | Excellent. The router manages its queue well. |
| 30–100 ms | Fine for browsing, but you will feel it in competitive games. |
| 100–300 ms | Clear bufferbloat. Lag whenever anything downloads at home. |
| Over 300 ms | Severe. Even voice calls will break up. |
Pay special attention to upload latency. ADSL and many home connections have small upload speeds, so the upload queue fills very quickly. A single photo backing up to the cloud from someone's phone can push your ping to 400.
The real fix: SQM or Smart Queue
The proper fix is for the router to manage its queue intelligently: let small, urgent packets through first and stop big downloads from filling the buffer. This is called SQM (Smart Queue Management), built on algorithms such as fq_codel and CAKE.
Where to find it
- Routers with advanced QoS: some modern home routers have an option called "Smart Queue", "Adaptive QoS" or "SQM". Look in the advanced settings.
- OpenWrt: if your router supports the open-source OpenWrt firmware, the
luci-app-sqmpackage is the best fix currently available for this problem. - Gaming routers: many include some form of queue management, but test it yourself; not every "Gaming Mode" actually fixes bufferbloat.
The key setting: cap the speed slightly below your real speed
For SQM to work, the router has to be the slowest point on the path, not the modem or the provider's network. So you set the SQM speed to 85–95% of what a wired speed test gives you. For example, if you measure 100 down and 20 up, start with 90 and 18, then test again and watch the latency under load. You give up a little peak speed and gain steady ping.
If your router does not support SQM
Nothing works quite as well, but these reduce the problem:
- Limit upload speed in background apps: Google Drive, OneDrive, Dropbox and camera apps. Most have a setting to cap upload.
- Schedule large updates: set console and Windows updates to run overnight.
- Use a cable for the gaming device: this does not fix bufferbloat, but it removes another source of jitter: Wi-Fi itself.
- Traditional QoS: prioritising the gaming device in the router sometimes helps, but it is far less effective than SQM because the queue itself stays long.
Other causes of lag that are not bufferbloat
If download and upload latency are close to idle ping and the problem persists, look at these:
- High idle ping (above 80 ms): usually a distant game server. Make sure the correct region is selected in the game settings.
- High jitter even on a quiet line: usually weak or congested Wi-Fi. Try a cable.
- Packet loss: even 1% makes players teleport. This is usually a cable fault or a problem on the provider's line.
- A problem with the game's own servers: the Services Status page measures response time from your device to Steam, PlayStation, Xbox and others.