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,008 articles
Story
APNIC’s RDAP Registrant Role Identifies a Registration Party, Not Corporate Ownership
One word inside a nested APNIC record carries real evidentiary weight, but less than its everyday meaning may suggest. The RDAP role `registrant` identifies the entity recorded for a registration; it does not turn the response into a corporate-ownership register or a live map of…
Story
AFRINIC Deemed Two NRO NC/ASO AC Candidates Elected Unopposed. Its Linked 2026 Rulebook Now Returns 404
AFRINIC’s final 2026 candidate slate said Stephen Musa Honlue and Nitin Kelawon Sookun would be deemed elected unopposed to the NRO NC/ASO AC, while voting would still decide the duration of their terms. The Election Guidelines page linked as the basis for that procedure returned…
Story
APNIC prop-164 Turns Smaller IPv6 Allocations into a Reservation Test
APNIC prop-164 would let account holders begin with IPv6 allocations smaller than `/32` while preserving room for growth. The proposal may improve Whois and RDAP accuracy, but its durable test is whether reserved address space becomes a visible, reviewable registry commitment…
Story
ARIN’s Alternate Whois Link Is a Substitute View, Not Independent Corroboration
One ARIN RDAP record points sideways to ARIN’s older Whois REST service. That link is useful, but it does not turn two views from the same registry into two independent witnesses.
Story
LACNIC’s RDAP Name Is a Registration Label, Not a Legal or Routing Identity
A field called `name` invites more confidence than it deserves. In LACNIC’s live RDAP record for `200.0.0.0/21`, the value is simply the address interval written as a label. It identifies a registration record; it does not settle who legally owns the addresses or who operates the…
Story
APNIC's Larger IPv4 Delegations Need a Queue Rule Before a Bigger Ceiling
APNIC's prop-168 would let eligible account holders grow toward an aggregated /22 while proposing a separate /12 transition reserve. The proposal defines who may ask and how much they may receive; its own scarcity arithmetic shows why it must also define who goes first when…
Story
AFRINIC’s RDAP Handle Is a Registry Reference, Not a Global Network Identity
The string `196.216.2.0 - 196.216.3.255` looks like an address range because it is one. In AFRINIC’s current RDAP response, however, that same string also serves as the entity’s `handle`. Its meaning there is narrower than the network identity that downstream systems may be…
Story
ARIN's RDAP Transition Needs Evidence at Three Different Exit Gates
ARIN wants one standardized directory protocol in place of three older services. The destination is coherent; the operational test is whether Whois-RWS, RWhois and Port 43 can each leave on evidence suited to the users and dependencies they actually carry.
Story
RIPE NCC’s RDAP Country Code Does Not Geolocate the Network
A two-letter country code looks ready for a map. In a RIPE NCC RDAP network entity, however, it is a registration field—not a set of coordinates and not live evidence of where routers, users, traffic or services are located.
Story
APNIC’s RDAP objectClassName Defines a Schema Class, Not a Network Role
The label `ip network` appears near the top of an APNIC RDAP response. It is easy to read it as a description of what an organisation does. Its real purpose is narrower and more useful: it tells software which RDAP entity schema it is processing.
Story
APNIC prop-170 Must Price the Space Between IPv6 Need and Nibble Alignment
A technically valid IPv6 prefix is not always an easy unit to operate. APNIC prop-170 would let an LIR request the smallest nibble-aligned allocation that satisfies an already validated need. The proposal promises cleaner plans without abandoning needs-based allocation; its…
Story
ARIN’s RDAP Remarks Qualify This Entity, Not Every Registry Record
Human-readable text inside an RDAP response can look like a general registry instruction. Its location matters. In ARIN’s live entity response, Registration Comments sit inside a particular entity entity, while service terms and reporting notices occupy the response’s top level.
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…
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