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 Database Now Composes Unicode. The Text Chain Needs a Normalisation Receipt
One visible name can arrive as two different code-point sequences. RIPE Database release 1.123 deliberately makes those sequences converge before the value passes through its remaining UTF-8 controls. That is good interoperability. It is also the moment when an evidentiary chain…
Story
The root KSK rollover makes resolver readiness the real continuity test
A DNS service can be healthy while users behind a stale validating resolver see failure. That is the operational paradox of a root key-signing-key rollover: the cryptography changes centrally, but continuity is decided across distributed resolver fleets.
Story
AFRINIC Named a PDWG Co-Chair by Consensus. The Published Notice Does Not Show the Consensus Record
AFRINIC recorded the name, method and duration of a 2026 PDWG leadership selection, while leaving the underlying consensus determination outside the two frozen public pages reviewed here.
Story
LACNIC’s reverse-DNS anycast turns registry continuity into a distributed control
Reverse DNS is easy to overlook until it stops answering. LACNIC’s use of anycast for delegated reverse zones shows why registry continuity is not a single-server property, but an operating discipline built from placement, routing, synchronization and observation.
Story
RIPE RPSL aut-num Policies Declare Intended Routing, Not Observed BGP Behaviour
An import or export line in a RIPE Database aut-num entity is valuable evidence of a registered policy statement. It is not a measurement of what routers are doing now.
Story
LACNIC’s measurement commons turns regional latency into operating evidence
A latency chart is not a verdict on a country’s Internet. It becomes useful when operators can see the probes, time window and comparison behind it—and when the result leads to a question that can be tested again.
Story
AFRINIC Reported Unauthorised Routes from Reserved IPv4 Space. Full Withdrawal Was Not Yet Confirmed
AFRINIC described route announcements involving parts of 102.224.0.0/12 and several response actions; its notice did not close the record on full withdrawal.
Story
AFRINIC's Monitoring Button Is Deployed and Disabled
AFRINIC's deployment monitor contains the control announced in its August release, but not the address that would make the control usable. The public code handles that absence carefully: it leaves the button hidden. That is good failure behaviour. It is also evidence that a…
Story
LACNIC’s RPKI controls make route origin authority operable
LACNIC’s RPKI controls make route origin authority operable 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…
Story
AFRINIC Offered In-Person Registry Checks at AfPIF. The Frozen Page Does Not Report Outcomes
AFRINIC promoted face-to-face help with registry records, identity checks and open requests at AfPIF 2026; the frozen source set does not show what was completed.
Story
AFRINIC Invited Members and Stakeholders to a Survey. Results-Publication Status Is Unknown in the Frozen Source Set
AFRINIC published a survey invitation to members and stakeholders, but the frozen source set does not establish whether results were published or what decisions followed.
Story
LACNIC’s IPv6 allocation rules make scale plannable
**BTW analysis:** IPv6 offers a vast address space, but abundance alone does not tell a network operator what it may request, how need will be assessed, or what obligations follow an allocation. In Latin America and the Caribbean, those practical questions meet LACNIC’s published…
Story
A TTL Jump Can Make a RIPE Atlas Trace Invent an AS Link
A traceroute can place a destination directly after one visible network even when several unseen routers still forwarded the packet. The missing segment is not always silence or a tunnel. New RIPE Atlas research shows that an on-path device can raise the probe's TTL and let it…
Story
LACNIC’s 2025 Path Study Does Not Date Its Measurements
A year in a report title tells readers when an edition belongs on the shelf. It does not tell a network operator when the packets behind its charts crossed the wire. LACNIC’s regional path study offers a useful view of routes and latency, but leaves that second clock unstated.
Story
LACNIC 46's Machine Records Still Say LACNIC 39 and LACNIC 45
The closing entry in LACNIC 46's current agenda belongs to the right event when read through its canonical taxonomy and presentation title. Three other fields still name LACNIC 45. A separate homepage field goes further back, to LACNIC 39. This is a small data-integrity problem…
Story
ARIN’s IRR Objects Keep the Channel That Created Them
An IRR object migrated from ARIN’s email service can be deleted in ARIN Online but not edited there. The asymmetry is defensible as a record of provenance. The trouble begins when the web remedy—delete and recreate—changes that provenance without a visible continuity receipt.
Story
ARIN's SMS Country List Is Now an Attack-Cost Boundary
A request to make SMS authentication more convenient ended with a security-cost decision. ARIN says the limited numbers it supported outside its service region created a costly attack vector; the public record explains the boundary it chose, but not the attack it measured.
Story
APNIC’s Resource Quality Check Is Not an Address Attribute
APNIC made a careful change in 2019: “assurance” became “check”. The distinction matters because a registry can observe routes, filters and reputation signals, but it cannot make thousands of other networks carry the result forward.
Story
A Locally Served DNS Root Has a Refresh Bill
Serving the root zone beside a recursive resolver removes many outward queries, but it does not remove network traffic. A new measurement highlighted by APNIC shows that the bill moves into the update loop—and that software behaviour can matter more than the name of the…
Story
APNIC proposal tests a one-/24 IPv4 bridge for IPv6-only networks
APNIC prop-165 version 4 would let an organisation eligible for an initial IPv6 allocation request one IPv4 `/24` for transitional functions in an IPv6-only deployment. The proposal is still under discussion: its practical significance lies less in the size of the grant than 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