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,399 articles

Two versions of a two-year IPv6 network plan keep the assigned units constant while changing the denominator and 75% result.

Story

ARIN’s 75% Gate Depends on a Plan That Can Change

Sixty assigned prefix units are 75% of a plan containing 80 units. The same sixty are only 60% of a revised plan containing 100. No address has moved, yet the qualification result has. Draft Policy `ARIN-2026-2` makes that possible in principle because its proposed…

Aug 27, 2026
Five-stage IPv6 allocation path across Asia Pacific with an empty prior-assignment gate and a redirected initial decision.

Story

APNIC’s First IPv6 PI Request Has No Previous Assignment

APNIC’s `prop-175-v001` offers to remove a peculiar round trip: issue a `/48`, wait for deployment, invite the applicant back, receive much the same network plan and assess the larger need a second time. Reusing the later-stage test is economical. It is also a change of state…

Aug 27, 2026
An open blue dossier marked 174 contains an attachment marked 173, beside a separate green dossier also marked 173 and a blank correction-chain receipt.

Story

Two Numbers on One Proposal: APNIC Must Correct Identity Without Rewriting History

`prop-174: Align implementation of Prop-125 in APNIC Policy (APNIC-127)` `prop-173: Align implementation of Prop-125 in APNIC Policy (APNIC-127)`

Aug 27, 2026
One translucent member-portal threshold branches into four separate textless acceptance mechanisms for AS0 routing, inter-registry transfers, abuse-contact correction and hierarchical AS-SET naming.

Story

One Portal, Four Unfinished Clocks

MyAFRINIC v2 has become more than a software project: AFRINIC's own records place four materially different policy paths behind the same portal milestone, making it necessary to prove each implementation separately rather than letting one launch announcement stand for all four.

Aug 27, 2026
A recovered glass block enters a temporary holding tray, passes through provenance records and is routed into one of four inventory pools; an amber uncertainty path joins the lowest existing pool.

Story

The Prefix Must Keep Its History: AFRINIC’s Proposed Pool Decision

Under `AFPUB-2026-IPv4-003-DRAFT01`, one recovered IPv4 block would first enter the temporary `Recovered Pool`. AFRINIC staff would trace its original source-pool category, return it there, classify a partial block proportionally, or send an uncertain origin to the…

Aug 27, 2026
Five annual folios share one continuous metal identifier rail beneath a plain six-section strategy spine; linked tokens and a transparent retired tray preserve decisions across cycles.

Story

The Commitment Must Keep Its Name: RIPE NCC’s Missing Annual Ledger

RIPE-862 offers a precise starting chain: **Internet Resilience, Scalability and Routing Security**; the service-level objective **Security**; and the key metric **Internet Number Resources covered by ROAs and ASPA**. The next links—a costed 2027 Activity Plan and Budget…

Aug 27, 2026
Four anonymous groups of geometrically tagged paper inputs pass through a transparent synthesis mechanism toward a bound strategy folio, while deferred material remains in separate trays.

Story

Between Listening and the Map: LACNIC’s Missing Input Trace

LACNIC’s public account names a collective planning process and a route from listening to SWOT and a final strategic map. What the checked documents do not expose is the privacy-safe join that would let a reviewer follow one issue from source class and channel through synthesis…

Aug 27, 2026
An analyst faces three registry clocks beside a separate map of live network routes across Latin America and the Caribbean.

Story

LACNIC’s RDAP Last Changed Event Dates the Registry Record, Not the Network Handover

A timestamp in a registration record can anchor an investigation, but it cannot substitute for the event the investigator actually needs to prove. LACNIC’s live RDAP data makes that boundary unusually visible: a network entity and the entities embedded inside it carry different…

Aug 26, 2026
A hardware access token remains tethered to a transaction folder above a gap leading to an empty receiving tray, with live network fibres behind it.

Story

The Seller’s Last Login: Why a LACNIC Deal Can Close Before Its Addresses Move

A buyer can acquire the shares, the routers and the customer contracts at midnight and still wake up without a completed registry handover. In a LACNIC transaction, the costly interval is the registry gap between legal control of the company and verified control of the number…

Aug 26, 2026
A corporate affiliation chart converges on one brass seat at a governance table over an Asia-Pacific map.

Story

APNIC's corporate-group rule turns affiliation into an electoral boundary

Before an APNIC nominee reaches the ballot, an organizational chart may already decide whether that candidacy counts as an independent choice or as a second seat for one corporate interest.

Aug 26, 2026
Editorial illustration of an AFRINIC registry key stopping at a ledger while routing signals continue through separate filters and routers.

Story

AFRINIC’s mnt-routes Attribute Grants Database Update Authority, Not Control of Live Traffic

AFRINIC lets an address-space holder delegate the maintenance of related route records through one precise registry attribute. That permission can shape what other networks accept, but it is still several operational decisions away from moving a packet.

Aug 26, 2026
A glass case holding a subnet grid sits between a sealed loan file and a chain of registry and routing checkpoints; one amber gate limits the recovery path.

Story

The Prefix in the Credit File: What a LACNIC Lender Can Actually Recover

An IPv4 block can look valuable on a market screen and still fail a lender’s recovery test. In the LACNIC region, collateral value depends on a chain that joins company authority, applicable secured-transactions law, transfer eligibility, registry recognition and uninterrupted…

Aug 26, 2026
A sealed transaction folder, a processing token and a calendar ledger sit separately beneath a transparent IPv4 registry grid.

Story

Three LACNIC Numbers an IPv4 Accounting Memo Must Not Collapse

An IPv4 transfer can produce a private price, a registry-processing charge and a recurring membership invoice. They may arrive in the same transaction folder, but each number proves something different.

Aug 26, 2026
A recovered address block crosses a timed quarantine and separate cleanup gates while a shorter path has an open lower boundary and a late objection remains preserved at handoff.

Story

AFRINIC's quarantine-floor objection crossed the Last Call boundary

A predictable Last Call cutoff and operational flexibility can both protect registry continuity. But AFRINIC's public record leaves a narrower control question unresolved: who owns a late objection when proposed discretion can shorten recovered IPv4 quarantine without a binding…

Aug 26, 2026
An abuse report passes through a chain of transparent handoff points and reaches the downstream operations desk able to respond.

Story

A Valid Abuse Mailbox Is Not Enough. APNIC Wants a Working Handoff

A mailbox can answer a validation message and still fail the incident report that matters. APNIC’s prop-171 would make the upstream holder responsible for a working path to the downstream party able to act, but the proposal has not yet said how that path will be proved.

Aug 26, 2026
A translucent registry record above a magnifying lens branching toward a company building, a server rack and user devices on an unlabeled map.

Story

RIPE's Country Field Names a Code Without Proving Where an Address Is Used

A registry can preserve a perfectly valid country code while leaving its geographic subject unresolved. The distinction matters whenever `country: NL` is copied into security, compliance, market or infrastructure decisions as though it located every address in the range.

Aug 26, 2026
Circular APNIC governance table with empty leadership chairs and concentric procedural stages against an Asia-Pacific network field.

Story

APNIC’s SIG rulebook is turning bottom-up governance into a due-process test

A rule written for quiet mailing lists now sits at the centre of a larger question: whether APNIC’s community institutions can renew leadership and close inactive forums without weakening the procedural legitimacy on which bottom-up governance depends.

Aug 26, 2026
A finite grid of dark address tiles is linked by five brass verification seals to a glass registry ledger beneath an unlabeled map of Latin America.

Story

LACNIC Turns IPv4 Value Into a Chain of Proof

An IPv4 block may attract a price, but a board cannot rely on that value until authority, eligibility and the registry change can survive diligence.

Aug 26, 2026
A protected registry card links to a separate stack of location records that pass through an independent verification lens before branching to uncertain map points.

Story

APNIC’s Geofeed Field Authenticates the Link, Not Every Location

An APNIC address record can point to a geolocation file through a maintainer-protected field. That establishes a useful chain of publication; it does not turn every place name in the separately changing file into a verified physical fact.

Aug 26, 2026
Route collectors feed a generated snapshot toward a public archive, with the delivery path interrupted after a failover.

Story

RIPE RIS Generated the BGP Snapshot. Delivery Still Failed

The 25 August incident did not begin with a failed route collector. RIPE NCC says the 16:00 UTC bview files had been generated, yet they did not reach the public archive after a failover. That distinction turns a small status notice into a useful test of where a public…

Aug 26, 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