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 Kept Five Services Running Without Updates. Its Service-Level Report Has No Freshness Column
A registry can answer a question and still have nothing new to say. ARIN's planned July maintenance made that distinction visible: five reader-facing services remained operational while updates were not being published. The public service-level report measures availability well…
IETF
Gavin Brown and the Successful Create That Did Not Yet Register a Domain
The server said the command had completed successfully. In the same breath, it said the action was still pending. RFC 8334 makes that apparent contradiction useful: an accepted application is evidence, but it is not yet a registered domain.
Story
AFRINIC’s News Page Canonicalizes to Its Privacy Policy
The page is reachable and visibly full of news. The contradiction sits in the same HTML response: the title, heading and structured data call it News & Announcements, while the canonical URL and social identity call it AFRINIC’s Privacy Policy.
Story
APNIC's EC Adopted Topic Shepherds. No Public Charter Says What a Shepherd Can Do
APNIC's Executive Council has chosen a sensible answer to a familiar board problem: give individual members continuing responsibility for important subjects. Its May minutes call them topic “Shepherds” and say they will lead discussions on allocated areas. The missing part is not…
ICANN
ICANN Marked Nameshop’s .IDN Application “Terminated”—Its Board Resolution Said “Withdrawn”
Nameshop’s latest reconsideration filing arrives after ICANN closed a 2012-round application that could no longer proceed. The unresolved public question is narrower than the applicant’s demand: the Board’s operative instruction used “withdrawn status,” while staff letters and…
Story
RIPE Atlas Warns of Bad NTP Offsets. Thousands of Connected Probes Still Report Firmware 5120
RIPE NCC has named the faulty field and the replacement release. Its public API also shows that the affected version remains connected at scale. What is still missing is a correction record that joins those two facts to the result rows downstream users actually analyse.
Story
AFRINIC's New-Member Portal Names Three Preflight Guides. All Three Links Return the Same 404
AFRINIC's application portal is online and unusually clear about what a prospective member should read before applying. The problem is in the handoff: process, eligibility and supporting documents are presented as three separate guides, but each link depends on the same page that…
Global Institutional Trends
VeriSign's .net wholesale fee rises 9.99% to US$12
The important distance in VeriSign's new `.net` price is one tenth of a cent. Multiplying the existing US$10.91 wholesale fee by the registry contract's 1.10 annual ceiling produces US$12.001. VeriSign has announced US$12.00, effective 1 March 2027. The increase therefore uses…
Story
RIPE NCC Began Verifying Roughly 1,600 No-Contract Legacy Holders. Its Q3 Plan Still Describes Two-Place Updates
RIPE NCC has a sensible plan to give old resource records a clearer organisational anchor. Its own quarterly plan also reveals the awkward middle of that migration: one change may still have to be performed manually in two places. The test is not whether the campaign looks…
CASE FILE
W3C's WoT Registry Requires Two Reviews—Not Necessarily Two Reviewers
A proposed Web of Things charter would turn protocol bindings into a maintained W3C Registry. Its pilot rules make a revealing distinction: moving a binding to `Current` requires one review of the underlying protocol mapping and another of its fit with WoT, but the same qualified…
Story
ARIN's Two Audit Findings Sound Opposite. They Test Different Controls
One ARIN Board record says no audited ticket was out of policy; another says inconsistencies appeared in every area examined. The difference is not a proven reversal in performance. It is a warning that audit findings become misleading when the test, standard and denominator are…
Story
LACNIC Calls Postman Its Current API. The Website Still Says ROAs Change by Serial Number
LACNIC gives an API operator two public descriptions of the same control surface. Its Registration API page says Postman holds the most current v3 documentation, while the route table beside that instruction describes modifying or removing one ROA by `serialNumber`. Follow the…
Story
APNIC Called RPKI Mirroring Marginal. Its NNIX Pilot Tests a Different Benefit
In October 2025, APNIC assessed a repository mirror as a short-lived aid during a long outage and called the benefit very marginal. Seven months later, its agreement with NNIX proposed a Hangzhou mirror pilot around latency, validation speed and data availability. The…
Story
ARIN's NET Permissions Change With the Lookup Path
One child NET, three ways to identify it, and three different questions about authority. An ARIN community suggestion reported that a direct registrant could reclaim a Detailed Reassignment and retrieve it through an exact address range, but could not use the same API key to GET…
Story
APNIC Counted 2,974 IDNIC Allocations. Its Three Completed NIR Reviews Have No Public Denominator
APNIC can show, with unusual precision, how one preliminary review began: 2,974 IDNIC allocations, a fixed date window and 1,216 records requiring more investigation. It can also say that three other NIR reviews are complete. What the public record cannot do is connect those…
Story
AFRINIC's Current RPKI CPS Says It Manages Asia-Pacific
The Certification Practice Statement linked from AFRINIC's current resource-certification page is version 3.0 from May 2020. In its CA-termination clause, the registry assigns itself the Asia-Pacific region. AFRINIC and IANA assign that region to APNIC and place AFRINIC in Africa…
Story
AFRINIC Has 3,573 Address Objects Pointing to Geofeeds. Its Schema Still Has No Geofeed Field
AFRINIC’s public database already carries geofeed pointers at material scale, but it carries them as prose. The fallback is valid and useful. The missing question is whether a convention used by thousands of address records should remain a string that the schema cannot identify…
Story
RIPE NCC Reports a 467-Day IPv4 Wait. The Queue Needs a Flow Ledger
RIPE NCC’s August member update says 757 LIRs were waiting for IPv4 space and the first LIR had been in line for 467 days. Its public chart records the queue’s size and its oldest wait, but those two stocks cannot show whether movement came from allocations, new requests…
Story
RIPE NCC Needed 394 Supporters Before a Member Resolution Could Reach the Agenda
The number 394 was not a vote result. It was the price of admission to the vote: a cycle-specific calculation deciding whether a member-authored subject and its verbatim resolution would enter the General Meeting agenda. The rule has a sound institutional purpose. The public…
Story
LACNIC Published a 98% Outreach Score. The Response Count Is Missing
LACNIC says more than 330 organizations attended its 2025 member gatherings and that 98% of the feedback it received fell in the highest satisfaction levels. Both statements may be accurate. The public post does not disclose the number of responses, so the percentage cannot be…