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
APNIC Deferred Its Singapore Subsidiary. Its Public Record Still Lacks a Payment Baseline
APNIC did something institutions often find difficult: it investigated a proposed remedy and stopped when the assessed costs and risks exceeded the likely benefit. The unresolved question is not why Singapore was rejected. It is how the Member payment problems that started the…
Story
LACNIC’s TAL Page Shows Two URLs and Links to Two Others
LACNIC’s trust-anchor page presents two addresses as TAL downloads. A reader who clicks them reaches distinct, valid TAL files through legacy Innovaportal targets. A reader or script that copies the addresses printed on the page instead receives the same HTML application shell…
Number Resource Society
A ROA Change Needs an Authorization-and-Withdrawal Ledger
A route can be Valid while the organization behind it has already forgotten who approved the authorization, what changed, or how to reverse it. ROA governance needs evidence that joins intent, publication, observation and withdrawal—not another screenshot of a green status.
Story
RIPE NCC’s Two Voting Codes Need a Credential Map
RIPE NCC tells October’s voters to expect two codes in two emails. That is a useful instruction, but it is not yet an account of the control. The names “Code 1” and “Code 2” describe a user journey; they do not show what each credential proves, who can recreate it, or when a…
Story
ARIN’s 29 August Stats Pair Split Across Two 2023 Filenames
ARIN’s public statistics directory contained a small but unusually legible publishing error on 29 August. The current data and checksum were available under their correct 2026 names, yet current-period artifacts also appeared through two extra paths dated 2023—and those two paths…
Story
AFRINIC Is Shrinking Its Data-Centre Footprint. Recovery Now Crosses a Cloud Boundary
AFRINIC's 2025 infrastructure report describes a sensible modernisation: retire obsolete equipment, use a smaller physical estate, place backups off site and test restoration every quarter. The harder question begins after the backup succeeds. Can the registry show that an…
ICANN
ICANN Tests Two-Character gTLDs Against Two-Letter ASCII Codes. What Does That Gate Actually Protect?
A two-character label can be valid enough to enter the 2026 Round and still be stopped because it resembles a two-letter ASCII code. The important question is not simply whether ICANN says no. It is which gate said no, which label or variant caused the comparison, and whether the…
Number Resource Society
A RIR Representation Mandate Needs a Scope-and-Revocation Ledger
A public member list can show who has appointed a representative, but it cannot by itself show what that representative may do today. When the subject is Regional Internet Registry governance, authority needs a versioned record of scope, time, action and revocation rather than an…
Story
APNIC's Firewall Reboot Put Registry Writes and Repository Reads Under One Clock
APNIC says a network firewall detected a hardware fault and rebooted on 28 August, interrupting six named service surfaces for an incident window of eight minutes. The short duration is reassuring. The single clock is not a complete recovery statement, because the list stretches…
ICANN
ICANN Can Stop a String Without a Competing Applicant. What Does a Blocked Name Actually Do?
In the 2026 new gTLD round, a protected or reserved label can stop an application without becoming a rival applicant. The decisive governance question is whether the public record shows the exact exclusion boundary, comparison and challenge clock.
Story
AFRINIC's 2028 Draft Would Rank Votes Across Eight Different Board Seats
AFRINIC's proposed Constitution contains an elegant-looking way to rebuild staggered Board terms: give three years to the three candidates with the most valid votes, two years to the next three and one year to the final two. The difficulty sits one clause earlier. Those…
Story
AFRINIC's New ASN and /24 Share a Holder ID, Not a Transaction ID
AFRINIC's New ASN and /24 Share a Holder ID, Not a Transaction ID 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
RIPEstat Wants Better AS Names—and a Map of Which ASNs Are One Entity
RIPEstat Wants Better AS Names—and a Map of Which ASNs Are One Entity 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.…
Story
RIPE 93 Dropped Childcare. “Low Demand” Has No Public Denominator
RIPE 93 will not provide organised childcare. The meeting team gave a concise reason on 28 August: demand and participation had been low in recent years. That may be a sound operational judgment. The public record does not yet let a reader test it, because the offer itself…
Story
LACNIC's Delegation File Declares 49,894 Records. It Contains 48,214
A daily file built for machines fails the counting rule printed in its own specification, while its automatic alias and its dated signature offer two different paths to trust. The discrepancy is not evidence of missing Internet resources. It is a test of whether a registry…
Story
LACNIC’s Revocation List Shows a /23 in 2023 and a Nested /24 in 2026
The same first address appears twice in LACNIC’s public revoked-resources table, first as a 512-address block and three years later as its lower 256-address half. That visual repetition invites the wrong question: was the same resource revoked twice? Six official daily snapshots…
IETF
A Temporary IANA Registry Needs More Than an Expiry Date
The IETF is considering a way to publish an IANA registry before the RFC that creates it has been approved. A visible two-year clock is a useful warning, but the harder governance question is what happens to the authority behind every entry when the registry is renewed, closed…
Story
ARIN Accepts Non-Human Service Accounts. Its Guide Still Says to Use an Individual Email
ARIN closed a four-year request on 29 July after removing the account-creation restriction on non-human service accounts. The implementation gives network operators a proper principal for automation. The public instructions have not yet made the same transition: the account guide…
Story
ARIN’s ROA Alerts Follow Deletion, Not the Change in Routing Authority
ARIN can commit several routing authorizations in one transaction, yet its documented alert boundary still follows a single verb: delete. Two public suggestions expose the resulting choice between inbox noise and silence. A safer design would report the net change once.
Story
APNIC Sold 6 Cordelia. Its RPKI CPS Still Says APNIC Owns the Building
Five days after APNIC announced that it had sold its South Brisbane office, two prominent registry contacts acquired fresh modification times and the unchanged post-office-box address. Yet the RPKI practice statement served from APNIC’s long-lived URL still says the registry owns…