Single-stack monitoring for RIR governance continuity.
Governance / RIR Watchdog
RIR Watchdog
RIR Watchdog governance intelligence tracks institutions, policy processes, standards activity, registry operations, accountability disputes, and implementation signals that affect internet infrastructure. BTW.
ARINRIPE NCCAPNICAFRINICLACNIC
Institution legitimacy and policy execution quality.
Decision-critical policy and control changes.
Primary-source reporting plus structural interpretation.
Latest Coverage
Latest from RIR Watchdog
2,386 articles
Story
The Route Was Absent. The Traffic Still Found It: APNIC 62’s BGP Neighbor Problem
A route-origin filter can leave an operator’s table clean while a downstream neighbor forwards toward the rejected destination. An APNIC 62 presentation made that uncomfortable distinction concrete. The useful response is to preserve separate evidence of received routes, local…
Story
One Revoked Certificate, Three Browser Outcomes at APNIC 62
The certificate was on the revocation list. That was not the end of the story. Geoff Huston's APNIC 62 demonstration put the same adverse record in front of three browser policies and obtained different results—a useful warning about the distance between publishing a security…
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.
Story
RIPE NCC Kept the Lameness Checks and Stopped the Emails
In 2009, RIPE NCC separated two activities that are often mistaken for one: it continued periodic checks of broken DNS delegations and ended the bulk email alerts generated from them. The decision is a useful historical operating case in what an infrastructure measurement can…
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.
Story
Presto Leaves Applications Unchanged. Its Peers Still Have Conditions
Presto’s POSIX layer can preserve the application’s familiar socket boundary. The published prototype nevertheless asks operators to condition the NIC and every peer that meets it on the wire.
Story
LACNIC’s WHOIS Shows the Origin ASNs but Not Their Authorization Boundary
LACNIC’s WHOIS Shows the Origin ASNs but Not Their Authorization 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…
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…
Story
LACNIC’s New Transfer Draft Is a Policy Map, Not a Checkbox
One sentence in LAC-2026-4 appears to ask whether two registries have compatible rules. Read closely, it asks five different questions—and leaves the most important hand-off between them undocumented.
Story
APNIC Wants Login to Read the Current IRT Email State
An account should not inherit yesterday’s lock answer when today’s IRT contact state says something else. APNIC’s 2026 roadmap proposes replacing reliance on a static account lock flag with a login-time check of continuously tracked IRT email validity. That is a small sentence…
Story
India Opened Lower 6 GHz. APNIC 62 Still Needed a Client Receipt
The band could be lawful, the access point could contain the right radio, and a device could still never see the network. APNIC 62 turned that gap between authorization and usable capacity into an operational record—but not yet a reproducible one.
Story
AFRINIC's Resource Certificate Can Be Valid Without Naming the Member
A resource certificate with a generated, apparently meaningless Common Name can be doing its job perfectly. AFRINIC’s own practice statement shows why: the public certificate proves a bounded resource authorization, while a different chain connects the request key to a…
Story
AFRINIC’s Merge Question Could Bind Two Section 3 Decisions Together
The co-chairs asked whether a meeting-calendar rule and a broad rewrite of the policy working group should become one draft. Before that happens, the community needs to know what would be combined—and what it would still be allowed to decide separately.
Story
RIPE NCC arbitration: the database lock and the ruling clock
RIPE NCC describes an interim lock on database records and a separate timetable for arbitration. For members, the crucial questions are when that timetable starts, what remains usable during review and how a ruling takes effect.
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…
Story
Rapport Counts Outcomes Only After a Requested Test Path Exists
LACNIC’s revised Rapport runner can expand several category and test selectors into a matrix. Yet a requested cell with no matching directory leaves no row in the result: it returns before a test identity is printed or any outcome counter moves.
Story
APNIC’s Two-Nameserver Run Had Fewer Repeats. The Difference Still Needs a Reproduction Receipt
APNIC measured fewer authoritative DNS queries in a later run using two nameservers than in an earlier run using one. The observation is real in the published aggregates; the cause is not settled. A reproducible decision needs the two treatments to share a clock, cohort and…
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…
Member Unlock
Restricted Profile Intelligence
Login is required to unlock full profile briefings and deep-dive sections.
Strategic Circle Briefing
Join to unlock strategic briefings after signing in.
Join Strategic CircleLeadership Alliance Briefing
For qualified IP-asset owners and management; sign in to unlock alliance briefings.
Join Leadership AllianceSession Map
Registry Sessions
ARIN
North America governance, transfer-market behavior, and member process monitoring.
Open ARINRIPE NCC
Accountability, member visibility, and implementation signals across the RIPE NCC region.
Open RIPE NCCAPNIC
Allocation pressure, policy adaptation, and Asia Pacific institutional execution.
Open APNICAFRINIC
Election process, legal continuity, and board legitimacy under institutional stress.
Open AFRINICLACNIC
Institutional adaptation and ICP-2 governance trajectory in Latin America.
Open LACNIC