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,388 articles
Story
RIPE NCC’s K-root Refresh Needs Three Acceptance Records, Not One Batch Status
Amsterdam can be refreshed while the three-site programme remains in progress. That is not a contradiction; it is a warning about the unit of evidence. RIPE NCC has named three K-root core sites whose seven-year-old routers and servers were due for replacement. The useful public…
Story
AFRINIC Says It Belongs to All of Us. Its SGMM Notice Draws a Smaller Corporate Boundary
AFRINIC’s anniversary message speaks to members, stakeholders and the wider Internet community in one generous voice. Six days later, the meeting named in that message operated through a narrower set of corporate roles. Both can be legitimate. The governance test is whether a…
Story
LACNIC’s Autonomous-Network Ladder Needs a Scenario Ledger, Not a Company Badge
Two operators can both call themselves level three while describing entirely different machines. One may automate fault diagnosis in a radio network; the other may automate service fulfilment but leave every consequential configuration change to a person. The number sounds…
Story
RIPE NCC Says Its 2027 Invoicing Changes Are Complete. The Bill Still Waits for 31 December
RIPE NCC has finished the applications work for its 2027 charging scheme before the data that will determine the first bills exists. That is sensible project management. It is also why “complete” needs a second, more operational meaning in January: can each charge be reproduced…
Story
ARIN’s RPKI Constraint Is Only as Current as the Package That Ships It
A trust boundary can be carefully designed, correctly signed and still arrive too late. ARIN’s planned RPKI constraint work makes that mundane distribution problem part of routing-security policy.
Story
ARIN’s Open 1,024-Character Ticket Is Really About a Private Routing Grammar
An open ARIN suggestion asks for more room in an IRR remarks field. Its motivating case is not really about storage. Lumen documents a parser that can turn a marked remark into the effective membership of an AS-SET, overriding the field that ordinary RPSL readers expect to carry…
Story
RIPE ABUSE: Who Controls the Next Step After a Report?
RIPE ABUSE is often described as a contact point. That is accurate, but incomplete. The published abuse-c field creates a route into a responsibility chain: a report can be addressed to a resource holder or designated organisation, the mailbox can be tested by RIPE NCC, and a…
Story
APNIC and NIXI Cannot Close India’s ROV Plan With One Percentage
On 8 September, APNIC Labs could describe India’s observed ROV filtering as 1.14% or 6.03%. Both figures came from the same dated record. The difference was the window—and it is exactly why a national routing-security promise needs a receipt, not a headline number.
Story
RIPE NCC Finished the RIS Bare-Metal Move. That Does Not Close the Pipeline
RIPE NCC’s newest RIS plan uses “finished” and “in progress” in the same paragraph, without contradicting itself. The data moved; processing assurance, storage choices, Kafka renewal and a consumer’s latency response sit on different clocks. The useful public record is not one…
Story
A Scan Found 4,611 Exposed BGP Routers in APNIC. It Cannot Say Why They Were Open
At APNIC 62, researchers put a regional number on a quiet control-plane problem: 4,611 routers across 1,343 APNIC-region autonomous systems answered an unsolicited BGP OPEN exchange in a February IPv4 scan. That is firmer evidence than a port banner, but it is neither a breach…
Story
AFRINIC’s Two-Day Service Clock Opens on Three Different Maps
AFRINIC promises an effective response within two working days. Yet a correspondent choosing where to send a request meets twelve queue labels, sixteen specialist addresses, or three broad contacts and a general form. The commitment needs a public map between the front door and…
Story
AFRINIC's 8 September Snapshot Returned Four Old Resources to “Allocated.” It Cannot Say Why
Three ASNs and one /19 crossed AFRINIC’s public boundary together between two signed daily files. Their 2006 dates came back with them. That is evidence of a current state change, not evidence of a new allocation—and the distinction deserves a small public receipt.
Story
LACNIC’s Abuse-Contact Lockout Sits Outside the Policy Manual
LACNIC’s policy manual says when an abuse contact becomes noncompliant. A separate help page says the consequence is blocked access to MiLACNIC. The missing entity is not another reminder email. It is the public record that joins a rule to the administrative control it activates.
Story
DATAMATIX and AS210973: What Public Routing Evidence Can—and Cannot—Prove
DATAMATIX and AS210973: What Public Routing Evidence Can—and Cannot—Prove 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 Atlas's Upgrade Reminder Still Needs a Maintenance Route
The planned notices put old software versions in front of probe hosts. They do not make every host's installation path the same.
Story
ARIN's Smaller Slate Keeps the Withdrawals in View
The September candidate list offers a useful governance test: account for the people who leave the field without inventing the reason they left.
Story
ARIN’s RPKI Failover Test Left the Dependency Question Open
ARIN blocked access to its RPKI repositories for an hour, restored it, confirmed redundancy five minutes later and reported a return to baseline after another fifteen. That is unusually concrete resilience evidence. It is also narrower than the dependency question ARIN had…
Story
RIPE Database 1.124.1 Fixed Certificate Selection. Its “No Evidence” Finding Needs a Search Boundary
RIPE NCC was right to ship a reported authentication vulnerability without waiting for a routine test interval. The next duty is different: show members what time, traffic and registry history were actually examined before “no evidence of exploitation” became the public…
Story
APNIC’s WHOIS Archive Reports Two Totals for the Same Hour
The latest completed hour says APNIC received 3,192,583 WHOIS queries. Add the seven query types printed beside that total and the answer is 3,183,463. The missing bridge is not a rounding error; it is the meaning of the measurement.
Story
A LACNIC Telecom Essay Moves Voice to IP. It Leaves Backup Power Unassigned.
A new LACNIC Blog essay catches the most consequential detail in the retirement of traditional telephony: the call may look unchanged, but its power supply has moved. That observation deserves a more exact public answer about who keeps an IP call alive when the lights go out.
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