RIPE NCC · RIR Watchdog
Story
BTW reporting and context linked to this RIR. For the proposal-by-proposal history, the people involved and their changing positions, start with Policy.
Story
Latest stories
330Stories
Story
The Four Days That Secured a Network: How AS210328 Acquired Its RPKI Cover in Late August 2026
The Four Days That Secured a Network: How AS210328 Acquired Its RPKI Cover in Late August 2026 intelligence summary explains the development, the public evidence available to readers, the organisations involved, the regional context, market exposure, and the infrastructure…
Story
Who Answers When the Registry Names a Company That No Longer Exists: The Svea Remedy Path in the RIPE Record
Who Answers When the Registry Names a Company That No Longer Exists: The Svea Remedy Path in the RIPE Record intelligence summary explains the development, the public evidence available to readers, the organisations involved, the regional context, market exposure, and the…
Story
RIPE-NONAUTH’s 0.006% Query Share and 20% of NRTM Requests Measure Different Things
RIPE NCC has published two statistics about RIPE-NONAUTH that describe different access paths, not one utilization rate. As its Q4 cleanup proposal moves to “Starting,” the distinction matters: neither number identifies dependent operators or proves that removal is safe or…
Story
Who Controls Abuse in the RIPE Region? The Measurement Surface and the Remedy Surface
Every malformed abuse report in the RIPE service region eventually arrives at the same question: who is actually responsible for stopping abusive use of internet number resources? The RIPE NCC's own published documents give an unusually precise answer, and it is not the one…
Story
RIPE NCC’s Geneva Briefing Invoked Measurable Progress, Without Naming a Measure
At a 17 September session co-hosted with the ITU and the Permanent Mission of Lebanon in Geneva, the RIPE NCC placed the RIR function between digital-policy goals and operational delivery. Its post-event account describes partnerships, capability and capacity building as routes…
Story
DFINFRA and AS210860: the lifecycle ledger of a silent network
DFINFRA and AS210860: the lifecycle ledger of a silent network 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
RIPE NCC’s October Vote Sends Surplus and Deficit in Opposite Directions
The draft resolution for RIPE NCC’s October General Meeting assigns a 2026 surplus to reserves but a deficit to members in 2027. If members reject it, the agenda describes the reverse allocation; the 2025 meeting approved that alternative.
Story
RIPE ABUSE 2025-2026: The Enforcement Record That Still Never Fires
The RIPE NCC's abuse-contact regime ran at full volume through 2025, and the numbers are now on the record: 2,320 validation investigations, 86,959 validated email addresses, 2,825 assisted registry checks. What the same 2026-dated documents do not show is a single enforcement…
Story
RIPE Withdrew Its IPv6 PI Rewrite. The Rule an Operator Uses Did Not Move
An organisation planning an IPv6 PI request has two RIPE records to read. One, the proposal page, still showed a draft in Review Phase when checked on 27 September. The other, a working-group chair's message dated three days earlier, said that draft had been withdrawn. Neither…
Story
RIPE’s Central Asia Path Comparison Needs a Sample Ledger
Three maps can show change only if the rows behind them stay countable. RIPE NCC’s CAPIF 5 report presents an encouraging direction for Central Asian Internet paths across 2022, 2024 and 2026. The next useful publication is not a more confident adjective. It is a compact receipt…
Story
DFINFRA and AS210860: Running the Commercial Half of a Test BTW Defined but Never Executed
DFINFRA and AS210860: Running the Commercial Half of a Test BTW Defined but Never Executed intelligence summary explains the development, the public evidence available to readers, the organisations involved, the regional context, market exposure, and the infrastructure…
Story
Where Registration Ends and Operation Begins: Inside the AS216429 Case File
Where Registration Ends and Operation Begins: Inside the AS216429 Case File 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
AS210764: a root-server ASN that no global router can see
AS210764: a root-server ASN that no global router can see 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
The Last Resort That Has Not Fired: RIPE NCC's Documented Escalation Ladder and Its Unpublished Enforcement Record
A mailbox can pass every automated check the RIPE NCC runs against it and still never answer a single abuse report. That gap — reachability versus responsiveness — is now well documented. What the registry's own paperwork adds is a second, quieter gap: the escalation ladder that…
Story
DFINFRA and AS210860: The Registry Says One Thing, the Routing Table Says Nothing — and Neither Has Moved
DFINFRA and AS210860: The Registry Says One Thing, the Routing Table Says Nothing — and Neither Has Moved intelligence summary explains the development, the public evidence available to readers, the organisations involved, the regional context, market exposure, and the…
Story
RIPE Fellowship Offers Full Support. Travel Feasibility Sits Outside the Published Score
RIPE NCC has opened its Fellowship for two 2027 meetings with a clear promise of coaching, training and full support. Its detailed programme page also describes visa, cross-border travel and reimbursement constraints that may leave part of the journey with the applicant. The…
Story
RIPE NCC's Signed Checklist Is Waiting Behind Two Other Jobs
A standard can exist, a community can ask for a service, and a registry can still have no date for delivering it. RIPE NCC's September RPKI plan puts Resource Signed Checklists behind identity and assurance work, with an API as the possible first product. The distinction matters…
Story
RIPE NCC Closed the Test API Incident. The Recovery Join Is Missing
Four status updates show a pilot service moving from investigation to resolution in 37 minutes. They do not show the small set of facts that would let a user connect that green status to a particular test operation, a checked isolation boundary and a completed reconciliation.
Story
RIPE NCC Kept the Lameness Checks and Stopped the Emails
In 2009, RIPE NCC separated two activities that are often mistaken for one: it continued periodic checks of broken DNS delegations and ended the bulk email alerts generated from them. The decision is a useful historical operating case in what an infrastructure measurement can…
Story
RIPE’s IPv6 PI Draft Has a 24-Month Plan but No Post-Plan Decision
Proposal 2024-01 can ask an applicant what it expects to use over the next two years. It does not yet say what evidence, judgment or proportionate response should follow when those two years are over.