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
ICANN’s GRC RFP Centralizes Records, Not Risk Authority
ICANN wants one hosted platform for policies, risk registers, audits, compliance mapping, dashboards and automated evidence. The procurement could improve custody and visibility across distributed teams. It should not let a software state stand in for the institutional act it…
ICANN
ICANN’s Samson Cree Visit Needs a Follow-Through Record
ICANN’s invited visit to the Samson Cree Nation was a real act of listening, education and relationship building. It was not, on the published evidence, a community mandate or a policy outcome. The accountable next step is an opt-in record showing which themes the community…
Story
RIPE NCC Put “Public Arguments” Inside Its Sponsorship Conflict Test
RIPE-866 is designed to protect neutrality from money and influence. Its hardest line does something broader: it treats litigation, arbitration, public argument and other conflict as neighbours, then carries the test from a disputing party to anyone associated with one. That may…
ICANN
Before a Complaint Becomes a Board Case, What Can ICANN's Ombuds Office Actually Change?
ICANN's Ombuds Office can change the route, information and voluntary resolution around a fairness problem—but contact is not formal notice and does not create a binding remedy.
Story
The Estate Cannot Route Itself
A liquidator can inventory equipment, contracts and claims. That does not make an Internet number delegation an ordinary asset that moves merely because a sale schedule says so. Insolvency creates two records that must meet: the court-supervised estate and LACNIC's…
ICANN
ICANN’s Applicant-Support Outreach Still Lacks a Public Cohort Test
ICANN has approved 56 applicants for its 2026 Applicant Support Program and says intensified outreach seems to have paid off. The result is real; the causal claim is not yet auditable. ICANN's own guidance calls for pre-agreed conversion benchmarks and evidence that distinguishes…
Story
LACNIC Cut Its Recovery Window to Three Months in 2015. One Procedure Page Still Says Six
LACNIC has a clean public record of shortening its resource-recovery publication period from six months to three. It also has a current operational page and policy manual that use the shorter clock. The unresolved problem is simpler and more practical: another public procedure…
ICANN
ICANN Would Make the DNS-Abuse Check Mandatory—but Not Comparable
ICANN's newest DNS-abuse proposal would require a registrar to look beyond one evidenced malicious registration, yet it would let every registrar document that check in its own format. The investigation should remain flexible; the evidence interface should not. Unless a source…
Story
ARIN-2026-4 Calls Two Clauses Redundant. The Replacement Needs a Scope Map
ARIN’s consolidation draft says two IPv6 clauses can be retired without meaningful change. That may be right. But the old and proposed sentences do not name the same subjects, duties or qualifiers, so redundancy should be demonstrated proposition by proposition while the text is…
ICANN
ICANN Opens the Downloads and Retires the API: The Handoff Needs a Receipt
ICANN will close its Open Data Platform and API after 31 August, replacing the old access surface with login-free CSV downloads. That is a genuine access gain, but it does not by itself preserve dataset identity, automation or correction history. Unless a source carries another…
Story
APNIC’s prop-167 Status Needs Two Rows
APNIC did publish the hourly directory statistics its community asked to see. The live files make that success unusually easy to verify. They also make a second fact harder to ignore: `prop-167-v002` asked for another output, and the Executive Council gave it a different…
ICANN
ICANN Draws the Phase 2A Boundary: No New Duty to Publish
The GAC asked when work on collecting and publishing legal-person domain-registration data would move. ICANN's Board answered with an FY2027 start forecast—and a more consequential clarification: the adopted Phase 2A package creates technical work and nonbinding guidance, not a…
Story
The Date Line in 4.10: When ARIN’s Interpretation Becomes Text
`ARIN-2025-8` would put `within the ARIN service area` into NRPM 4.10 as a codification of existing staff practice. Its timetable says `Immediate`, while its comments say staff has no intention to extend the restriction to allocations issued before implementation. The statements…
ICANN
ICANN’s safeguard appointment starts the decision-record test
Mirror Group LLC will assess which 2026-round new gTLD strings require binding Safeguard Public Interest Commitments. The appointment assigns responsibility; legitimacy will depend on the facts, reasons and conflict controls recorded for each classification. Unless a source…
Story
AFRINIC’s Bandwidth Upgrade Cannot Be Closed by Uptime Alone
A service can remain switched on, connected to the Internet and technically available while every useful interaction through it becomes slower. AFRINIC’s February capacity notice described that middle state. Its own service commitment shows why restoring performance requires a…
Story
RIPE NCC’s Five-Year Restriction Now Turns on “Involved”
RIPE-791 attached a later application to two named roles around a former member: contact person and representative. RIPE-863 replaces those roles with a different test—whether a person provided fraudulent or misleading data or was `involved` in providing it. The five-year period…
Story
Six Minutes Are Published. LACNIC’s Summary Column Says Nothing
LACNIC’s 2026 Board page presents six meetings, six dates and six links to approved minutes. Beside them sit six empty `Summary of activities` cells. The records exist; the map into the records does not. That difference determines whether a reader can find a decision without…
Story
ARIN’s 75% Gate Depends on a Plan That Can Change
Sixty assigned prefix units are 75% of a plan containing 80 units. The same sixty are only 60% of a revised plan containing 100. No address has moved, yet the qualification result has. Draft Policy `ARIN-2026-2` makes that possible in principle because its proposed…
Story
APNIC’s First IPv6 PI Request Has No Previous Assignment
APNIC’s `prop-175-v001` offers to remove a peculiar round trip: issue a `/48`, wait for deployment, invite the applicant back, receive much the same network plan and assess the larger need a second time. Reusing the later-stage test is economical. It is also a change of state…
Story
Two Numbers on One Proposal: APNIC Must Correct Identity Without Rewriting History
`prop-174: Align implementation of Prop-125 in APNIC Policy (APNIC-127)` `prop-173: Align implementation of Prop-125 in APNIC Policy (APNIC-127)`