Skip to main content

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
RIR Watchdog signal visual
Governance / RIR WatchdogRIR Watchdog
Registry Nodes5 Active Regions

Single-stack monitoring for RIR governance continuity.

Primary DomainGovernance

Institution legitimacy and policy execution quality.

Core TopicsElections / ICP-2 / Transfer Policy

Decision-critical policy and control changes.

Output ModeIntelligence Briefing

Primary-source reporting plus structural interpretation.

Latest Coverage

Latest from RIR Watchdog

2,424 articles

A registry record with its local label, shown separately from a legal dossier and a network-routing graph.

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…

Sep 4, 2026
An ordered line of allocation requests between a finite IPv4 address pool and a separately protected proposed transition reserve.

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…

Sep 4, 2026
A registry object and reference enclosed in one namespace, separated from several external key systems.

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…

Sep 4, 2026
Three legacy network paths pass through separate gates and converge on a structured RDAP service path.

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.

Sep 4, 2026
An NL registry field shown separately from network paths spanning multiple regions.

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.

Sep 4, 2026
RDAP record passing through an objectClassName schema classifier, separate from network routes

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.

Sep 4, 2026
Network operator viewing abstract IPv6 address-plan blocks in a network operations centre.

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…

Sep 4, 2026
A highlighted remarks layer contained inside one RDAP entity object, separate from notices at the response level.

Story

ARIN’s RDAP Remarks Qualify This Object, 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.

Sep 4, 2026
An RDAP record and its self-retrieval pointer separated from routing, hosting, DNS and traffic infrastructure layers.

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.

Sep 3, 2026
Editorial illustration of many anonymous applications passing through transparent gates toward five selected tokens, beside a closed process ledger.

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.

Sep 3, 2026
A bounded IPv4 registry record separated from IPv6 registration, routing and service evidence layers.

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.

Sep 3, 2026
Nested address-registry records separated from a distant routing plane.

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…

Sep 3, 2026
A calibration mechanism adjusts an oversized assessment frame to match the smaller address block under review.

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…

Sep 3, 2026
Illustration of an ASN block entering a regional registry inventory while selected numbers pass through separate allocation checkpoints to networks.

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.

Sep 3, 2026
An active IP registration record separated by a bright boundary from independently observed network routes.

Story

APNIC’s RDAP Active Status Describes a Registry Object, 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.

Sep 3, 2026
Three service-notice cards float above a separate IP registration record, divided by a bright evidence boundary.

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…

Sep 3, 2026
Editorial illustration of three versioned governance documents, a comparison overlay and an unfinished institutional pathway over a network map.

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…

Sep 3, 2026
An editorial illustration traces an abuse report through delivery, filtering, triage, response and validation before a bright boundary separates it from case adjudication.

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.

Sep 3, 2026
An editorial diagram separates a LACNIC RDAP response profile from an independent BGP routing plane.

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…

Sep 3, 2026
Editorial illustration of five committee seats, a calendar and a procedural file before a network map of Africa.

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.

Sep 3, 2026

Member Unlock

Restricted Profile Intelligence

Login is required to unlock full profile briefings and deep-dive sections.

Only for Strategic Circle

Strategic Circle Briefing

Join to unlock strategic briefings after signing in.

Join Strategic Circle
Only for Leadership Alliance

Leadership Alliance Briefing

For qualified IP-asset owners and management; sign in to unlock alliance briefings.

Join Leadership Alliance

Session Map

Registry Sessions

ARIN

North America governance, transfer-market behavior, and member process monitoring.

Open ARIN

RIPE NCC

Accountability, member visibility, and implementation signals across the RIPE NCC region.

Open RIPE NCC

APNIC

Allocation pressure, policy adaptation, and Asia Pacific institutional execution.

Open APNIC

AFRINIC

Election process, legal continuity, and board legitimacy under institutional stress.

Open AFRINIC

LACNIC

Institutional adaptation and ICP-2 governance trajectory in Latin America.

Open LACNIC