Bufferbloat is the undesirable latency that comes from a router
Comments on “Bufferbloat is the undesirable latency that comes from a router”
Claim-checked. Scored by all three judges, and its checkable claims were compared with the sources it cites. How far stories are checked
The Bufferbloat Project's introduction explains how oversized packet buffers in routers and other network gear add latency and make traffic bursty, and why more bandwidth or larger buffers do not help. It recommends smaller unmanaged buffers and smarter queue management than FIFO, naming fq_codel. The page is an early-2011 advocacy text, and its claims, including that fixes reduce the need for bandwidth caps and that bufferbloat is a systemic risk, are stated without supporting data. For product builders, it argues for testing latency under load before blaming capacity.
Why it ranked
No. 14 of 62 with a score of 0.62. The panel rated it highest on new information (0.93) and audience breadth (0.73), lowest on substantiated (0.41). Placed No. 14, No. 24 by score alone: the placement terms moved other stories past it.
- AI judgeJudge 2claude-haiku-5-5
- Essay on bufferbloat, a well-known networking problem, with solid explanation and historical context but little new information beyond the last 7 days' stories and a somewhat dated framing.
- AI judgeJudge 3gpt-5.6-luna
- A technically useful explanation of bufferbloat, its network effects, detection, and mitigation, with broad infrastructure relevance. It is persuasive and largely unsupported by direct measurements here, and some catastrophic conclusions exceed the evidence presented.
Each judge wrote its line after answering the rubric, with the site and the author still hidden. Every answer behind this is in the table under Score.
Score
0.62total under rubric v2.3
- Significance0.68
- Reader interest0.66
- Audience breadth0.73
- Practical relevance0.70
- Substantiated0.41
- Technical depth0.70
- New information0.93
- Counts against: Promotional0.06
- Counts against: Overclaim0.49
Each judge’s answer per question (0–1), their mean and spread, and what the question adds to the score (weight × mean).
| Question | Judge 1 | Judge 2 | Judge 3 | Mean | Spread | Weight | Contribution (weight times mean) |
|---|---|---|---|---|---|---|---|
| SignificanceHow much does this change what people in tech know or can do? | 0.70 | 0.55 | 0.78 | 0.68 | 0.23 | +0.24 | +0.163 |
| Reader interestWould a well-informed senior engineer or tech founder want to read this today, and likely pass it on? | 0.47 | 0.70 | 0.82 | 0.66 | 0.35 | +0.26 | +0.172 |
| Audience breadthHow many people who build technology does it concern? | 0.88 | 0.60 | 0.72 | 0.73 | 0.28 | +0.13 | +0.095 |
| Practical relevanceHow useful is it to someone who builds software or tech products? | 0.65 | 0.70 | 0.76 | 0.70 | 0.12 | +0.22 | +0.154 |
| SubstantiatedHow well is it backed? Consider whether it is the primary source, and whether its main claims come with data, code, a demo, a reproducible method or citations. | 0.28 | 0.45 | 0.50 | 0.41 | 0.22 | +0.05 | +0.021 |
| Technical depthHow technically substantive is it? | 0.76 | 0.65 | 0.68 | 0.70 | 0.11 | +0.05 | +0.035 |
| New informationDoes it contain information absent from the stories covered in the last 7 days (list provided)? | 0.93 | 0.90 | 0.96 | 0.93 | 0.06 | +0.05 | +0.047 |
| PromotionalIs it mainly marketing with little substance (a press release, ad or sponsored post with no real information)? A launch post that carries real news is not promotional. | 0.10 | 0.05 | 0.03 | 0.06 | 0.07 | −0.19 | −0.011 |
| OverclaimDo the headline or conclusions claim more than the body supports? | 0.46 | 0.45 | 0.55 | 0.49 | 0.10 | −0.11 | −0.054 |
| Sum of contributions | +0.622 | ||||||
| Claim-check penalty | 0.000 | ||||||
| Total, as published | 0.622 | ||||||
Spread is the highest minus the lowest judge answer. marks a spread above 0.40: the judges disagree, and the story is marked contested.
The badge for this ranking, for the author's page or anyone's: one line of HTML, and it links back here.
<a href="https://rubric.hrih.si/editions/2026-11-15/14/"><img src="https://rubric.hrih.si/badge/2026-11-15/14.svg" alt="Ranked #14 on Rubric, 15 Nov 2026" width="245" height="28"></a>Claim check
Claim check: 7 no source given · 1 couldn’t check. Each claim is compared with the source the article itself cites; a flag is published only when both checkers agree.
Couldn’t checkCausal conclusion
Bufferbloat is now relatively easy to fix after 4 years of research, development and deployment, with fq_codel as the fix.
The source was unreachable, paywalled or too long, or the two checkers disagreed.
The article says “bufferbloat is now, after 4 years of research, development and deployment, relatively easy to fix”
The source says No passage could be compared.
Source cited by the article: bufferbloat.net/projects/codel/wiki
No source givenCausal conclusion
Fixing bufferbloat may solve many service problems currently addressed by bandwidth caps and metering, making the Internet faster and less expensive.
The article gives no link or citation for it.
The article says “fixing it may solve a lot of the service problems now addressed by bandwidth caps and metering, making the Internet faster and less expensive for both users and providers”
The source says No source to compare with.
No source givenFirst, only or fastest
The Bufferbloat Project has found Internet connections with buffers proportionally as large as the state of Texas if the connections were highways.
The article gives no link or citation for it.
The article says “May Internet connections have buffers that, if the connections were highways, would be the proportional size of the state of Texas”
The source says No source to compare with.
No source givenGeneralization
Perceived Internet speed depends much more on latency than on bandwidth.
The article gives no link or citation for it.
The article says “Perceived speed of the Internet is much more a function of latency (time to get a response) than of bandwidth (ability to bulk-ship”
The source says No source to compare with.
No source givenCausal conclusion
Buying fatter pipes does not fix bufferbloat cascades, and buying larger buffers makes them worse.
The article gives no link or citation for it.
The article says “buying fatter pipes doesn’t fix the bufferbloat cascades, and buying larger buffers actually makes them worse”
The source says No source to compare with.
No source givenCausal conclusion
Bufferbloat causes latency-sensitive services such as DNS, VoIP, video streaming, NTP, ARP, DHCP and SSH to degrade badly.
The article gives no link or citation for it.
The article says “DNS lookups get painfully slow. Voice-over-IP services like Skype and video streamers like YouTube become stuttery, prone to dropouts, and painful to use”
The source says No source to compare with.
No source givenDate
Bufferbloat-driven self-synchronising traffic could be a greater threat to the Internet than the congestion-driven near-collapse of the NSF backbone in 1986.
The article gives no link or citation for it.
The article says “could be a greater threat to the Internet than the congestion-driven near-collapse of the NSF backbone in 1986”
The source says No source to compare with.
No source givenGeneralization
Many problems now attributed to under-capacity and bandwidth hogging are actually symptoms of bufferbloat.
The article gives no link or citation for it.
The article says “many of the problems now attributed to under-capacity and bandwidth hogging are actually symptoms of bufferbloat”
The source says No source to compare with.
Also covered by
No other coverage was clustered with this story.
Elsewhere
Elsewhere: HN 3 pts, not on front page
Recorded for context only, checked 15 Nov 2026, 20:46 UTC. It played no part in the ranking.