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.
ICANN
When a Rejection Action Expires: the ASO, ICANN's FY27 Plans and the Limits of an Empowered Community Check
Two attempts to use the Empowered Community's rejection power against decisions of the ICANN Board were opened and closed in 2026, and neither reached a vote. One concerned money: the ICANN FY27–31 Operating and Financial Plan, the ICANN FY27 Operating Plan and Budget and the…
Number Resource Society
RIPE ABUSE: The Escalation Ladder Is Documented, Its Use Is Not Counted
RIPE NCC publishes the steps it can take when an abuse contact fails validation, including closing a member and deregistering its resources. What it does not publish is how often the last step is reached. The only figures the registry has attached its name to are from 2017 to…
Story
ARIN’s Draft Defines “Out of Region” Without Defining the Unit
ARIN’s Draft Defines “Out of Region” Without Defining the Unit 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…
Number Resource Society
Reachable Is Not Responsive: Inside RIPE NCC's Abuse-Contact Validation
RIPE NCC now validates the abuse-mailbox attributes published in its database at least once a year — first with automated checks that send no email, then through a graduated escalation that can end in the closure of a member and the deregistration of internet resources. The…
ICANN
Who Can Stop a New gTLD Application, and What an Applicant Can Actually Win
ICANN can refuse, defer or condition a new generic top-level domain application — but the two remedies an unsuccessful applicant can pursue do not hand it the string. One returns the question to the same Board. The other produces a declaration about whether the Board kept to its…
IETF
RFC 9812: A Stricter Review Gate Does Not Allocate IPv6 Space
Most of the IPv6 address space remains marked “Reserved by IETF.” RFC 9812 changed the rule for any major future release of that reserve from IESG Approval to IETF Review. That is a consequential transfer from an exceptional gate to a public, documented process. It is not an…
IETF
RFC 9876: A CoAP Registry Number Is Not an Interoperability Verdict
The smallest number in a protocol can carry the largest institutional misunderstanding. A CoAP Content-Format identifier lets a constrained device say, compactly, what representation it is sending. RFC 9876 makes the allocation of that number much harder to get wrong. It does not…
Story
ARIN’s IPv6 CSV Has a Spelling Problem, Not a New Address
An uppercase letter in an IPv6 export does not allocate a second network. It can still give a spreadsheet, log search or text-based join a second name for the same one. An ARIN customer asked for lowercase in the Manage Networks CSV; ARIN agreed that the change would be more…
Story
AFRINIC’s IPv6 Draft Changed What 95% Means
Draft 3 keeps the comfort of a familiar percentage while changing the thing being counted. A future result can be comparable only if it travels with the policy version, denominator and measurement method that produced it.
Europe and Middle East Datacenter
AZUR DATACENTER SAS: what a RIPE NCC membership listing actually proves
A French company named AZUR DATACENTER SAS appears in the RIPE NCC public member directory. That single record is the entire verified signal behind the company's presence in BTW's directory — and it is a narrower signal than its name suggests.
Story
ARIN Closed the Grant Total. Its Final-Report Clock Still Has Two Dates
ARIN’s 22 September notice names two 2026 Community Grant recipients and $37,350 in awards. The same program page still gives September and October 2027 as the final-report deadline, so the public schedule cannot yet be treated as one authoritative clock.
Story
APNIC’s Survey Asked for More Training—and Proof It Reached the Network
The 2026 APNIC Survey does not say technical training has failed. It says something harder to measure: respondents value skills development, yet want the journey from a lab to a working network to remain connected, observable and locally supported.
Story
RIPE NCC Closed the Test API Incident. The Recovery Join Is Missing
Four status updates show a pilot service moving from investigation to resolution in 37 minutes. They do not show the small set of facts that would let a user connect that green status to a particular test operation, a checked isolation boundary and a completed reconciliation.
Story
APNIC’s Twin 28-Minute Incidents Need a Correlation Receipt
Two MyAPNIC incidents ended after exactly 28 minutes within roughly 49 hours. APNIC gave each a bounded explanation; it has not publicly said whether their dependency paths were compared.
ICANN
ICANN's 15-Day Verification Dialogue Became a Briefing. The Binding Route Is Still Unchosen
The most revealing part of ICANN's latest exchange about domain-registration accuracy is not whether contact checks should happen before a name resolves. It is what happened to the meeting meant to discuss that question: a proposed webinar and trilateral dialogue became an…
Story
LACNIC’s New Legacy Draft Makes Four Facts Share One Trigger
A legacy block can have current contacts, working reverse DNS and a documented right of use while disappearing from the public routing view. LAC-2026-5 would put those different facts on one path to a Board recovery decision.
ICANN
The autistici.org Hold Has a Timestamp but No Public Decision Receipt
PIR’s RDAP service records exactly when `autistici.org` changed and which registry controls remain applied. It cannot tell the public who connected a US sanctions designation to that domain-wide action, which rule governed the choice, why it happened before a wind-down licence…
Story
RIPE’s IPv6 PI Draft Has a 24-Month Plan but No Post-Plan Decision
Proposal 2024-01 can ask an applicant what it expects to use over the next two years. It does not yet say what evidence, judgment or proportionate response should follow when those two years are over.
Story
ARIN’s Legal RPSL Still Produced a Partial Mirror Answer
A recursive query returned seven ASNs. The reference described in ARIN’s public suggestion contained far more. Nothing in that contrast required the routing policy to be invalid: the failure could sit in the journey from a logical set, through one very long physical line, into a…
IETF
The Card Passed Two Profiles. The Protocol Still Had a Question: RFC 10050
A profile can prove that a JSContact card belongs to a named, versioned subset. It cannot prove that a protocol should accept the card, or even tell a receiver which profile the sender intended. RFC 10050 makes that boundary explicit and turns profile identity, recursive property…