Topic
Registry Governance
Within the Topic facet, Registry Governance topic intelligence connects articles that share a specific subject, signal focus, or monitoring theme. The page gives readers a richer path through related reporting, source evidence, market actors, and infrastructure implications, with enough context to understand why the topic matters across company movements, governance decisions, regional exposure, and operational risk. Readers can compare recurring signals, affected organisations, public evidence, market context, service continuity, procurement, competition, compliance, and strategic planning questions behind the subject instead of stopping at a thin list of matching articles. It explains what the topic covers, which infrastructure actors or policies are involved, what evidence supports the coverage, and why the subject may matter for operators, customers, investors, and policy readers.
Story
ARIN Can Attach a Ticket to an Org ID. That Does Not Make It the Organization’s Decision.
ARIN fixed a mundane but costly support problem: staff no longer need to begin every ambiguous question by asking which organization it concerns. The resulting Org ID selector gives a ticket context and a durable home. That is good service design. It also makes one distinction…
IETF
INTAREA Adopted a Registry Cleanup. IANA Has Not Applied It.
An Internet-Draft can acquire a working group without changing a single live registry. That is what happened on 11 September: INTAREA published its version of a proposal to close one legacy list, assign procedures to three others and remove a fifth. The institutional handoff is…
Story
APNIC’s Priority Survey Has Three Bases: 1,039, 1,038 and 1,037.
APNIC asked its community to divide exactly 100 points among eight strategic activities. The resulting chart looks unusually complete: every point is accounted for and no priority overwhelms the rest. The publication trail is less settled. Three official artifacts attach three…
Story
AFRINIC-38 Has a Named Safety Concern. A Hybrid Format Is Not a Risk Assessment.
A public message from an experienced Malawian operator does not prove that Cape Town is unsafe. It does something more precise: it puts a concrete delegate concern into AFRINIC-38’s record. AFRINIC’s own meeting guide already treats security as a location-selection input. The…
Story
RIPE Atlas Put Reconnects and Liveness Through One Event Processor. A Slow Backend Blocked Both.
A RIPE Atlas software probe could have working Internet access on 8 June and still be shut out of the measurement network after a routine disconnect. The public incident record explains why: reconnect work and controller-liveness evidence passed through the same event processor.…
Story
RIPE NCC’s Four Stale IPv6 Glue Records Are Now Three. Root Repair Was Never a Batch.
One of four old IPv6 glue mappings identified after RIPE NCC’s AuthDNS renumbering has aligned with the nameserver’s current address. The other three have not. That split result reveals the real unit of root-zone maintenance: one delegation, one authorised decision and one…
Story
AFRINIC Calls 122 New Members a 4% Increase. The Baseline Is Missing.
AFRINIC’s statistics portal compresses five year-to-date counts into five whole-number growth labels. The figures look self-explanatory until one asks the ordinary questions behind any percentage: compared with what, at what time, under which inclusion rules, and rounded how? The…
Story
LACNIC Counts 2.223 Billion BGP Messages. Its Family Table Totals 853 Million Updates
Two sums on LACNIC’s noisy-BGP study close perfectly. A third opens a 1.37-billion-count question. That does not make the research wrong; “messages” and “updates” may describe different stages. It does make the missing bridge between raw RIS files and the published tables the…
Story
LACNIC Signs 150 Reverse-DNS Files. The Batch Has No Manifest.
LACNIC’s public directory gives every reverse-DNS data file its own signature and checksum. What it does not give a whole-directory consumer is one signed statement saying which 150 filenames belong to the same completed publication.
Story
ARIN Waited for a Geofeed Standard. Its RDAP Help Still Does Not Claim It.
Two years ago ARIN tied a community request to a visible trigger: once the common RDAP geofeed standard was accepted, three named product surfaces would change. The standard is now RFC 9877. The useful question is no longer whether the IETF will finish the vocabulary, but how an…
Story
BCAP’s Prize Entry Preceded Training. Its Outcome Receipt Has Not.
The WSIS Prize submission window closed two days before BCAP’s published professional-development start window opened. The project won in July and is still listed as ongoing through 2027. The award may be sound; the public record still needs to say which finished phase and which…
Story
AFRINIC’s ccTLD Map Counts 27. Three Require an Address Join.
AFRINIC’s new DNS surface gets the total right, but it does not show the work behind the number. Twenty-four of its 27 ccTLD rows name the registry in a delegated hostname. Somalia, Nigeria and Mali become legible only when their nameserver addresses are joined to AFRINIC’s…
Story
APNIC Prop-173 Would Make Every Directory Query an Agreement. The Response Would Carry No Version.
An acceptable-use policy can change while the response governed by it remains in a cache for years. APNIC's prop-173 would make ordinary WHOIS, RDAP and web queries subject to a clear, versioned policy and would tell users that querying or using the service means agreeing to…
Story
AFRINIC Can Close a Support Ticket After About Ten Working Days. It Never Ranks the Risk.
A registry is right to ask who is touching its records. AFRINIC's public Contractual Obligations Check makes that defence concrete: the sender must be registered, the member must be in good standing and a signed agreement must be on file. The problem begins after a check fails.…
Story
LACNIC's Open-Source Election Lookup Puts the Email Address in the Request Path
LACNIC's open-source election system authenticates a participation lookup before returning its answer. Yet the documented interface has already placed the entity identifier in the part of the request most likely to be copied by infrastructure. The distinction is not a disclosed…
Story
A Space IPv6 Draft Gives Every Planet Up to Five RIR Prefixes. It Never Defines the Region.
The appealing part of a new space-address proposal is that it does not start a sixth registry from scratch. The harder part is hidden in two words. Applicants would use their “appropriate RIR”, but a moving spacecraft has no obvious place on a map built for terrestrial service…
Story
ARIN Can Trace an API Key. Its Dashboard Still Cannot Say What the Key Is For
ARIN tells customers to separate credentials so that actions can be traced, but its public key-management guide says those credentials are identified only by prefix and creation date. The missing description field is a small interface omission with a large operational…
Global Institutional
ISC’s Five Control Surfaces: What the Public Record Can—and Cannot—Prove
Internet Systems Consortium, Inc. appears across some of the Internet’s most consequential technical systems: BIND and Kea software, an F-root role, Internet-number registry records, observed routing and RPKI authorization. Those appearances are important, but they do not…
Story
APNIC Will Automate Route-Record Alignment. The Roadmap Does Not Name the Conflict Winner
“Alignment” sounds like database housekeeping. In APNIC’s Q3 2026 roadmap, it means something harder: deciding how resource holdings, a route-management template, Whois route objects and RPKI authorizations should change when they disagree—and preserving enough evidence to show…
Story
ARIN Let Consultant Hiring Advance Before the Control Plane Vote.
ARIN’s draft Board minutes preserve an awkward but legitimate sequence: outside-consultant hiring could keep moving while the Registry Control Plane itself awaited a detailed plan and a later approval meeting. The issue is not whether preliminary expertise is useful. It is how…