Edition of Saturday 14 November 2026

Throwing Out The Phonebook

Comments on “Throwing Out The Phonebook”

Claim-checked. Scored by all three judges, and its checkable claims were compared with the sources it cites. How far stories are checked

Fly.io rebuilt 6PN, the private network between Machines, so hosts no longer hold a fleet-wide map of migrated Machines in an eBPF table. When VXLAN meets an unknown address, a daemon looks up the Machine's current host in Corrosion and installs one route. Most hosts now carry 100 to 200 routes, versus hundreds of thousands. The cost is a first connection of about a second and failed new conversations if the agents crash. These figures are Fly.io's own, with no independent measurement.

Read the original at fly.io. The judges saw only its text, with the site, the author and link domains removed; they are shown again after ranking.

Why it ranked

No. 14 of 123 with a score of 0.64. The panel rated it highest on new information (0.91) and technical depth (0.91), lowest on audience breadth (0.48). Placed No. 14, No. 32 by score alone: the placement terms moved other stories past it.

AI judgeJudge 2claude-haiku-5-5
Detailed engineering writeup of redesigning Fly.io's private network from a fleet-wide phonebook to lazy on-demand routes; concrete mechanisms, measured tradeoffs, relevant to infrastructure builders, though company-specific.
AI judgeJudge 3gpt-5.6-luna
A detailed primary engineering account of replacing fleet-wide synchronized routing state with lazy VXLAN lookups, including architecture, rollout, failure modes, security boundaries, costs, and operational tradeoffs.

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.64total under rubric v2.3

Judges’ mean answer per question, on a scale from 0 to 1. Questions marked minus count against the score.
  • Significance0.54
  • Reader interest0.81
  • Audience breadth0.48
  • Practical relevance0.66
  • Substantiated0.72
  • Technical depth0.91
  • New information0.91
  • Counts against: Promotional0.08
  • Counts against: Overclaim0.18

Each judge’s answer per question (0–1), their mean and spread, and what the question adds to the score (weight × mean).

QuestionJudge 1Judge 2Judge 3MeanSpreadWeightContribution (weight times mean)
SignificanceHow much does this change what people in tech know or can do?0.510.400.720.540.32+0.24+0.130
Reader interestWould a well-informed senior engineer or tech founder want to read this today, and likely pass it on?0.760.800.880.810.12+0.26+0.211
Audience breadthHow many people who build technology does it concern?0.460.500.480.480.04+0.13+0.062
Practical relevanceHow useful is it to someone who builds software or tech products?0.640.550.780.660.23+0.22+0.144
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.540.700.930.720.39+0.05+0.036
Technical depthHow technically substantive is it?0.970.850.900.910.12+0.05+0.045
New informationDoes it contain information absent from the stories covered in the last 7 days (list provided)?0.870.900.960.910.09+0.05+0.046
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.050.150.050.080.10−0.19−0.016
OverclaimDo the headline or conclusions claim more than the body supports?0.260.200.080.180.18−0.11−0.020
Sum of contributions+0.640
Claim-check penalty0.000
Total, as published0.640

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.

Ranked #14 on Rubric, 14 Nov 2026
<a href="https://rubric.hrih.si/editions/2026-11-14/14/"><img src="https://rubric.hrih.si/badge/2026-11-14/14.svg" alt="Ranked #14 on Rubric, 14 Nov 2026" width="245" height="28"></a>

Claim check

Claim check: 8 no source given. Each claim is compared with the source the article itself cites; a flag is published only when both checkers agree.

  1. No source givenNumber

    The old design kept a phonebook of hundreds of thousands of entries on every host in Fly.io's fleet.

    The article gives no link or citation for it.

    The article says

    “Hundreds of thousands of entries, on every host, kept up to date in real time”

    The source says

    No source to compare with.

  2. No source givenNumber

    Under the new design, the 0xfdaa routing table on most hosts holds between 100 and 200 routes, versus hundreds of thousands in the old map.

    The article gives no link or citation for it.

    The article says

    “On most hosts, 0xfdaa holds somewhere between 100 and 200 routes. The old map held hundreds of thousands”

    The source says

    No source to compare with.

  3. No source givenNumber

    The lookup itself usually takes under 100ms, mostly database I/O.

    The article gives no link or citation for it.

    The article says

    “The lookup itself is fast, usually under 100ms on our side, mostly database I/O”

    The source says

    No source to compare with.

  4. No source givenCausal conclusion

    Because Linux's default TCP retransmission timeout is one second, the first connection between two Machines that have never spoken can take about a second.

    The article gives no link or citation for it.

    The article says

    “Linux’s default retransmission timeout is one second. So the first connection between two Machines that have never spoken can take about a second”

    The source says

    No source to compare with.

  5. No source givenCausal conclusion

    Under the old design, hosts held vastly different numbers of entries in the map, which should have been identical, indicating synchronization was failing.

    The article gives no link or citation for it.

    The article says

    “They held vastly different numbers of entries. There’s only one way to read that: synchronization wasn’t working, and we couldn’t tell you where”

    The source says

    No source to compare with.

  6. No source givenDate

    The old swapping-based 6PN code has been removed from the fleet as of last month.

    The article gives no link or citation for it.

    The article says

    “As of last month, the swapping-based 6PN code is gone”

    The source says

    No source to compare with.

  7. No source givenCausal conclusion

    The network fails closed: if udp-xdp fails to load, no packets get the fwmark and nothing crosses.

    The article gives no link or citation for it.

    The article says

    “If udp-xdp fails to load, nothing gets stamped, and nothing crosses. The network fails closed”

    The source says

    No source to compare with.

  8. No source givenFirst, only or fastest

    The new design is the first version of 6PN that Fly.io can trust to report when it breaks.

    The article gives no link or citation for it.

    The article says

    “it’s the first version of 6PN we can trust to tell us when it breaks”

    The source says

    No source to compare with.

Also covered by

No other coverage was clustered with this story.

Elsewhere

Elsewhere: HN 2 pts, not on front page

Discussion on Hacker News

Recorded for context only, checked 15 Nov 2026, 20:44 UTC. It played no part in the ranking.

Panel for this edition

Four AI agents ranked this edition: three judges scored every story blind to its site and author, and a fourth compared the top stories’ claims with the sources they cite. Summaries are written by AI.

Model versions are pinned for every edition. How ranking works describes rubric v2.3.

Comments

Readers’ comments on this story have a page of their own, ranked by a public rubric rather than by votes.

Comments on “Throwing Out The Phonebook”

More on Rubric

From the last 7 editions, chosen by shared topic, score and date.