Bufferbloat by Connection Type Report 2026
By SpeedTestHQ Research ยท Updated May 14, 2026
Bufferbloat is the reason a connection can look fast on a speed test but still lag when the household is busy. This report compares which connection types are most likely to show loaded-latency spikes and what fixes actually work.
Key findings
- Cable and 5G are the most variable. Both can be fast, but shared capacity and asymmetric upload make loaded latency more noticeable during busy periods.
- Fiber is the easiest connection type to keep stable. Symmetric upload and lower access-network delay reduce the conditions that create long queues.
- Satellite has a different problem. LEO satellite can be usable but jitter varies; geostationary satellite starts with very high baseline latency.
- The fix is local and upstream. Good router queue management helps, but congested ISP nodes and tower load can still create latency outside your house.
Bufferbloat risk table
| Connection type | Idle ping | Loaded ping risk | Main cause | Best fix |
|---|---|---|---|---|
| Fiber | 3-12 ms | Low | Router queue if misconfigured | SQM only if uploads are saturated. |
| Cable DOCSIS | 10-25 ms | Medium to high | Shared node and low upload | SQM, upload shaping, DOCSIS 3.1/4.0 upgrades. |
| 5G home internet | 25-55 ms | Medium to high | Tower load and radio scheduling | Better placement, external antenna, backup router. |
| DSL | 20-60 ms | High | Small upstream pipe | Upload caps and SQM. |
| Fixed wireless | 20-70 ms | Medium | Signal quality and sector load | Antenna alignment and ISP capacity. |
| LEO satellite | 30-80 ms | Medium | Beam handoff and congestion | Clear sky view and peak-hour testing. |
| GEO satellite | 600+ ms | Very high baseline | Orbital distance | Not suitable for real-time apps. |
Why upload causes more pain
Most residential internet plans are asymmetric: download is much higher than upload. A 500/20 cable plan has plenty of download room for streaming, but a single cloud backup can fill the 20 Mbps upstream. Once the upstream queue fills, every outbound packet waits: voice, game input, video-call camera frames, DNS requests, and acknowledgements for downloads.
This is why a household can complain about lag even while download speed looks excellent. The bottleneck is not always how much data can come in. It is often how long urgent packets wait to get out.
Loaded latency bands
| Loaded ping increase | User experience | Severity |
|---|---|---|
| 0-20 ms | Hard to notice | Excellent |
| 20-50 ms | Minor call/gaming impact | Good |
| 50-100 ms | Video calls and games feel unstable | Needs tuning |
| 100-250 ms | Audio dropouts, rubberbanding, lag spikes | Severe |
| 250+ ms | Real-time use becomes unreliable | Critical |
Practical fixes
- Enable SQM or adaptive QoS on the router and cap speeds slightly below the real line rate.
- Prioritize upload control before download control on cable, DSL, and fixed wireless.
- Move large backups and game downloads outside work or gaming hours.
- Use Ethernet for workstations, consoles, and streaming boxes that cannot tolerate jitter.
- If bufferbloat happens only at night, the ISP access network may be congested; collect tests at multiple times before calling support.
Methodology
This report compares common access technologies using SpeedTestHQ loaded-latency scenarios: idle, download-saturated, upload-saturated, and mixed household load. The output is a planning risk model based on typical consumer deployments and known technical limits of each access type.
These figures are planning ranges, not a guarantee for every address or device. Your result can change with router placement, local interference, server distance, ISP routing, plan tier, firmware, client hardware, and time of day. For your own connection, run a wired speed test and compare it with Wi-Fi and peak-hour tests.
Frequently Asked Questions
What is a good bufferbloat score?
A loaded ping increase under 20 ms is excellent. Under 50 ms is usually fine. More than 100 ms means real-time apps will likely suffer when the connection is busy.
Can bufferbloat happen on fiber?
Yes, but it is less common because fiber has more upload capacity and lower baseline latency. A weak router can still create queues on any connection type.
Why does my ping spike only when uploading?
Uploads fill the smaller upstream pipe. When that queue is full, game inputs, voice packets, and TCP acknowledgements wait behind bulk traffic.