Primary Domain
Internet Infrastructure Institution
Within the Primary Domain facet, Internet Infrastructure Institution intelligence groups reporting by primary domain so readers can follow a focused area of internet infrastructure, governance, connectivity markets, or digital capital. The page brings together related articles, public evidence, institutions, companies, people, regional exposure, operating dependencies, and market context that may otherwise sit across separate category pages. It explains the domain, the likely actor class, the market or governance context, and the source material readers should use when comparing signals. Operators, analysts, and governance readers can see how the same domain appears across events, profiles, market shifts, public-source evidence, regional dependencies, and longer-cycle infrastructure decisions over time.
Story
Krypt Cut One /17 Into Five Visible Pieces. Three Left; Two Stayed.
Three ARIN transfers from 16 October to 2 November moved 20,480 IPv4 addresses to North Central, Fatbeam and TensorWave. Exact RDAP shows the two untransferred gaps still registered to Krypt.
Story
APNIC’s /22 Came Back After 1,849 Days. Then Two U.S. Blocks Dwarfed It.
The exact 1,024-address range left a Dream-labelled holder in 2015 and returned to a similar name in 2020. Two 2026 transfers from ARIN added 12,288 addresses; current RDAP joins all three ranges.
Story
ARIN Moved 11 HugeServer Resources in One Second. AS25780 Kept the Old Name.
ARIN Moved 11 HugeServer Resources in One Second. AS25780 Kept the Old Name. intelligence summary explains the development, the public evidence available to readers, the organisations involved, the regional context, market exposure, and the infrastructure consequences that may…
Story
ARIN Moves the Certificate at Transfer. The Recipient Must Write the New ROA.
ARIN automatically changes the certified resource set when addresses transfer, but the recipient's origin authorization is a separate job. The handoff has a machine half and a human half.
Story
APNIC Gave Telecom Vanuatu Two IXP-Pool Prefixes. The Exchange Is Unnamed.
An IPv4 /26 and IPv6 /48 entered APNIC’s register a minute apart on 2 November. Both came from address pools set aside for Internet exchange points; the public entities identify the telecom, but no exchange or peering LAN.
Leaders
Anne Lord Let ISPs Allocate IPv4. Their Upstream Kept the Exit.
The downstream ISP gained a real job in 2002: it could divide addresses among its own customers. Anne Lord's APNIC proposal put that practice on the books, then attached a cord to the block. Leave the upstream LIR, and the allocation went back.
Story
CyberForest Took 16 IPv4 Blocks and an ASN. The ASN Left; the Blocks Stayed.
CyberForest Took 16 IPv4 Blocks and an ASN. The ASN Left; the Blocks Stayed. intelligence summary explains the development, the public evidence available to readers, the organisations involved, the regional context, market exposure, and the infrastructure consequences that may…
Story
RIPE Assigned 2,048 Addresses for Ten Days. Then the Row Vanished.
A British-coded /21 appeared inside RIPE NCC’s reserved address span on 23 October. The 2 November file folded it back into the reservation, and today’s RDAP has no more specific holder to name.
Story
AFRINIC Holds an IPv4 Block for 45 Days. The Applicant Never Sees Its Prefix.
Approval starts a 45-day reservation and invoice clock. AFRINIC keeps the exact IPv4 prefix out of the applicant's view until payment turns the hold into a WHOIS registration.
Leaders
Hugo Salgado Asked the DNS to Show Its Work
Latin America's DNS Observatory traded a comfortable word, “resilience,” for server counts, network diversity and a record that could change over time.
Leaders
Alejandro Acosta Put the IPv6 Next Hop Under a Microscope
A LACNIC classroom plan turned a deceptively odd routing sentence into BGP sessions, captured packets and a question engineers could actually test.
Leaders
Geoff Huston Emptied the DNS Cache and Found the Bill
When a resolver already knows the way, almost any domain looks easy. Geoff Huston cleared its memory and watched a simple lookup become a tour of other people's design choices. The bill for a long alias chain does not arrive at the desk that wrote it.
Leaders
Nathalie Trenaman Found 460 Missing IPv6 Stars. The Routes Had Different Stories.
The dashboard said hundreds of networks had lost an IPv6 star. Nathalie Trenaman went looking for the operators behind the dimmed icons. Some had finished a test. Some had pulled a production route. Some had not noticed the route was gone. One score had been trying to tell three…
Leaders
RIPE Has a Policy Index. Remco van Mook Wants the Rules to Share a Spine
RIPE already lists its IPv4, IPv6 and transfer policies. Remco van Mook’s RIPE 93 proposal asks how those separate texts could read as one system, with each resource chapter moved through its own community proposal.
Story
RIPE’s 1993 /17 Split Off 1,024 Addresses in 2026. The Date Stayed Put.
A daily registry file that showed one 32,768-address range on Sunday showed three on Monday. The new middle piece belongs to a different named holder, but every row still wears the date 1 September 1993.
Story
One /22, Two Mergers, Three Advania Names: RIPE NCC's Missing Nameplate
The same 1,024 IPv4 addresses appear in two merger transfers 21 months apart. RIPE's organisation history supplies the identity link that the transfer rows omit.
Leaders
Randy Bush Asked Who Was Missing. APNIC Put a Clock on Consensus.
In 2003, Randy Bush challenged an Internet policy meeting on the people it could not see. Protocol engineers, router designers and operators had reasons to miss a distant conference; a proposal could arrive a week before the room decided. APNIC's answer was a written record and a…
Academics
Usama Ejaz Found 786 Routes With a Registry Receipt and a Red Light
An operator checks a route object and finds the prefix and origin neatly paired. The RPKI validator still says Invalid. Usama Ejaz counted 786 such stubborn disagreements in a week of routing data, forcing a harder question than whether a database row exists: who actually…
Leaders
Tom Strickx Cut the Extra Routes. Then the Leak Lost Its Address.
Too many internal routes can choke a router. Strip them away and a network may lose the clue that says where a leaked route escaped. Tom Strickx brought both problems to RIPE 93, along with a small piece of code meant to keep the clue without reviving the pileup.
Academics
Thomas Holterbach Wants the Routes the Collector Never Saw
A prefix disappears at an Internet exchange. A conventional BGP collection session can tell an operator what it received. Thomas Holterbach wants the harder evidence: what the route server saw before filtering, what it discarded, and whether the peer went away at all.