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
LACNIC Approved the Security Framework Before Measuring the Baseline. The Next Control Is a Versioned Maturity Receipt
The May board record exposes a useful sequence: authorize the framework, have outside experts measure the current state, and only then choose the destination. That order is not evidence of a security failure. It is a reason to keep approval, implementation, target-setting…
CASE FILE
The Registry Marked the Version. It Did Not Supply the Meaning: RFC 9713
RFC 9713 added one small column to an IANA table and, by doing so, exposed a large operating mistake. A code point can be allocated, valid for BPv7 and safely clear of the public assignment pool while still saying nothing about whether this receiver knows its content, shares the…
Story
AFRINIC’s Holiday Notice Appeared One Day Before Closure. That Is Not a 72-Hour Verdict
AFRINIC’s public record shows a 14 September notice for a 15 September office closure. Its service commitment speaks of seventy-two hours, but on a different channel: announcement mail. The right audit separates the website, the mail record, human response time and always-on…
Story
RIPE’s RDAP Marks a Mixed AS Block Reserved at Either Boundary
RIPE’s RDAP Marks a Mixed AS Block Reserved at Either Boundary 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 follow. The…
Story
LACNIC’s Election Upload Test Reads Bytes, Not Excel or PDF
A new compatibility test in LACNIC’s open election system carries two reassuring filenames across a disk boundary. The bytes arrive intact. That is valuable evidence—but it is evidence about transport, not about whether a workbook or a result letter is a valid document, whether…
Story
ARIN Approved a Revised Strategic Plan. Its Public PDF Still Says December 2025.
ARIN’s draft minutes record an August 2026 vote on a “new” or “revised” strategic plan. The plan linked from ARIN’s public planning page, however, identifies itself as the version adopted in December 2025. That mismatch does not prove the strategy changed. It does show that the…
Story
APNIC's RDAP Use Is 20%. That Is Not an Adoption Rate.
APNIC's new survey puts RDAP at 20% among respondents asked about core registry services. The number is useful evidence about reported use; it is not a census of deployed systems, a traffic share or a verdict on whether RDAP can replace WHOIS.
Story
RIPE NCC Has 110 Sanctions Investigations. Its Table Has No Clock.
RIPE NCC’s latest sanctions report makes the size of its screening work visible: the cumulative register reached 2,172 alerts, with 110 still under investigation on 2 July 2026. What the table cannot show is equally consequential. A reader can see where cases sit, but not how…
Story
The RIR Draft Counts 1,000 Members, Not 1,000 Votes
The proposed compliance-review threshold uses legal entities, not voting weight. LACNIC’s own election figures show why an auditable denominator must come first.
Story
ARIN’s Jacksonville Workshop Has Two Start Times
Three days before the event, ARIN’s dated notice says 9:30 while its live outreach page says 10:00. One labelled schedule can make both times useful.
Story
ARIN’s NRO Appointment Guide Links to a Replaced Agreement
A current procedural page can lead readers to a historical agreement. ARIN’s September appointment announcement makes that reference boundary worth checking, without turning an old hyperlink into a finding of invalid authority.
Story
RIPE Atlas Tools’ Ten-Second Timeout Stops Before the Atlas API
A setting added in June reaches the geocoder but not the reviewed measurement-creation path. A bounded source test shows where the budget is lost, not how long any live job waited.
Story
ARIN’s Election Calendar Uses Two Membership Snapshots
The right to support a nomination petition and the right to elect a candidate are not fixed on the same date. ARIN’s 2026 calendar makes that distinction concrete: a June snapshot governs any petition, while September determines eligibility for the autumn election. A later change…
Story
APNIC’s Volunteer Leadership Has a Cost Before the Ballot
APNIC’s leadership consultation identifies a barrier that an election cannot remove: somebody must make the working day available. Published EC guidance distinguishes unpaid service from reimbursable expenses. The harder question is how to support participation without turning…
Story
AFRINIC’s Daily Filenames Advance. The Dataset Still Says 10 September
Three consecutive archive names deliver the same 491,382 bytes, the same internal serial and the same period end date. That proves repeated public content, not a registry outage. The missing distinction is between a fresh no-change release and an older result served again.
Story
LACNIC 46 Says Blocking Is Now Reactive. Its Public Agenda Does Not Show the Coding Rule
A regional result is already visible: a forthcoming LACNIC 46 session says reactive blocking now dominates where active blocking had previously been observed. The public agenda does not yet show how 18 jurisdictions, an unknown number of cases and four unlike kinds of target were…
Story
RIPE NCC Can Audit IPv6 Resources. Its Policy Does Not Link the Procedure
The registry’s authority is not the disputed point. The problem is navigational: two IPv6 clauses tell LIRs what they must produce during an audit, while the document never takes the reader to the procedure that explains why an audit starts, how far it can reach and how an…
Story
ARIN Used 199 Cleared Blocks to Fulfill 307 Requests. The Split Map Is Missing
ARIN’s July distribution closes one scarcity question and opens an accounting one: the registry says 199 cleared IPv4 blocks fulfilled 307 waiting-list requests, but its public records do not show how the input prefixes were divided into the issued prefixes.
Story
AFRINIC's Bylaws Chair Is Also CEO Designate. The Review Needs a Role-Transition Record
Mike Silber will not take office as AFRINIC’s chief executive until 1 January 2027. But the constitutional review he was appointed to chair was still working one day after his designation was announced. That overlap is not proof of a conflict. It is a reason to publish the small…
History
Elise Gerich and the Public Record Behind Private Routes
Routers could tell one network what another network could reach. They could not explain what the other network meant to announce, what it was prepared to accept, or whether the two intentions were compatible. Elise Gerich’s work around the Routing Arbiter belongs to the history…