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
1,996 articles
Story
LACNIC’s RDAP Self Link Locates the Record, Not the Network’s Serving Infrastructure
A URL inside a registry response can look like an infrastructure clue. In LACNIC’s RDAP output, however, `rel: self` tells a client where to retrieve the registration entity; it does not say where the registered network’s traffic, applications or authoritative services run.
Story
AFRINIC Named Five Fellowship Recipients from a Pool Above 1,700. The Selection Record Is Not Public
AFRINIC’s announcement identifies five people and describes a highly competitive programme. It does not publish the exact applicant total, the scoring method, the assessors or the decision record, so the notice proves an outcome without making the selection reproducible.
Story
AFRINIC’s RDAP ipVersion Describes This Record, Not IPv6 Readiness
An IPv4 lookup naturally returns an IPv4 entity. That simple fact becomes misleading when `ipVersion: v4` is promoted from a property of one AFRINIC record into a verdict on an organisation’s entire network.
Story
RIPE’s RDAP Type Classifies a Registration, Not the Route Origin
RIPE’s RDAP Type Classifies a Registration, Not the Route Origin 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
APNIC's IPv4 Needs Test Should Match the Delegation Under Review
APNIC prop-169 would replace a fixed `/23` reference in an IPv4 LIR usage-plan test with the delegation actually being assessed. It is a narrow wording repair, but it matters because evidence should measure the request an applicant is making, not a larger block the policy no…
Story
AFRINIC Received 1,024 ASNs. The Public Record Separates Inventory from Allocation
IANA recorded a new 1,024-number block for AFRINIC on 25 February 2026, and AFRINIC announced the addition to its inventory on 27 March. Those records establish upstream custody, not downstream allocation of every number to operators.
Story
APNIC’s RDAP Active Status Describes a Registry Entity, Not Route Reachability
The word `active` looks like an operational verdict. In an APNIC RDAP response, however, it belongs to the registered entity—not to a live measurement of routes, packets or services.
Story
ARIN’s RDAP Notices Describe the Lookup Service, Not the Network’s Operating Policy
The warning labels attached to a registry lookup travel with the answer, but they do not belong to the network named inside it. ARIN’s top-level RDAP notices tell a reader how the lookup service may be used, where suspected inaccuracies can be reported and who claims copyright in…
Story
The RIR Governance Draft Is Public. Its Approval Path Is Still Unfinished
The 1 September release changes the evidence state around the proposed RIR governance framework: readers can now inspect version three, compare it with version two and read the stated rationale. Publication is a verifiable milestone, but it is not approval, adoption or legal…
Story
APNIC prop-174 Turns an Abuse Mailbox into a Policy Control Surface
APNIC’s prop-174 would move abuse-mailbox operations from implementation practice into explicit policy. That can make contact duties measurable, but it also makes delivery, filtering, triage and response records part of a chain that may eventually reach membership consequences.
Story
LACNIC’s RDAP Conformance List Identifies Response Specifications, Not Network Authority
An RDAP response can look like a compact certificate of power: it carries a registry name, a range, a handle, a hierarchy link and a row of terse technical tokens. But the tokens in `rdapConformance` answer a narrower question. They describe the specifications used to build the…
Story
AFRINIC Constituted Its Appeal Committee. The Appointment Record Now Has a Fixed Term
AFRINIC’s 28 August announcement names five Appeal Committee members and gives their appointments an immediate effective date and a 31 December 2026 endpoint. That creates a defined public mandate, while leaving future case handling to the committee and the applicable PDP rules.
Story
A Failed RIPE Database Update Can Still Change Records
RIPE NCC's documentation describes an update message whose entities can finish differently. The useful response is therefore not just a verdict on the message: it is an account of the changes already made, those rejected and those the caller still cannot confirm.
Story
LACNIC’s IPv4 transfer market and the price of scarcity
IPv4 exhaustion does not end allocation politics. It changes the place where they happen: from the distribution of a free pool to the rules governing transfers of resources that are already held.
Story
AFRINIC's IPv6 Monitor Shows What Its 54% Contains
A routing dashboard now distinguishes an advertised allocation prefix from routes to smaller pieces of it. Its South Africa data show why that distinction is useful—and why neither the combined total nor the narrower category is a service-quality score.
Story
RIPE's Flip Chart Experiment and the Work After the Introduction
A paper board helped researchers and network operators find one another. RIPE NCC's new account points to a useful next test: whether a promising introduction becomes a question both sides can afford to pursue, without silently committing either to data access or production…
Story
One Prefix, Two Countries in LACNIC’s Geofeed
A public location feed repeats 23 prefixes, four with conflicting country codes. The useful repair is narrower than deciding where the networks are: stop a loading rule from masquerading as geographic evidence.
Story
LACNIC’s Voice Primer and the Bandwidth Beyond the Codec
An 8 kbit/s voice encoder can send a 24 kbit/s stream before Ethernet, security and control traffic enter the calculation. LACNIC’s latest telephone explainer points to a distinction that matters when operators turn compression into a capacity budget.
Story
ARIN’s Reverse-DNS Controls Follow the Parent Block
A customer’s address range does not tell an operator where the reverse-DNS handoff belongs. ARIN’s direct-allocation rules put the editing boundary higher in the tree than a downstream inventory may suggest.
Story
What Comes After ARIN’s Empty Whois Replies
ARIN resolved a problem with some Whois queries in August. For anyone whose tools retained a suspect result, the next task is different: checking the local copy without turning a failed observation into a registration verdict.
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