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 frozen stack: what DFINFRA's address footprint can and cannot prove
The frozen stack: what DFINFRA's address footprint 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 follow.…
Story
The company behind the dormant network: what the Hamburg register can prove that AS210860's registry layer cannot
The company behind the dormant network: what the Hamburg register can prove that AS210860's registry layer cannot intelligence summary explains the development, the public evidence available to readers, the organisations involved, the regional context, market exposure, and the…
Story
RIPE NCC October 2026 General Meeting: The Board Structure Vote and What It Says About Member Control
The RIPE NCC has published a draft agenda for its October 2026 General Meeting that goes beyond routine housekeeping: alongside the 2027 budget discussion, an Arbiter Panel election and a surplus-distribution vote, members will be asked to approve Articles of Association…
Story
The contractual tail: how African LIRs stayed RIPE NCC members while AFRINIC served them
The handover of Africa's internet number registry is usually told as a single act of recognition. The dated instruments tell a more layered story: for over ten months after AFRINIC began operating, African members were legally RIPE NCC members under the RIPE NCC Standard Service…
Story
The 2019 Excess-Contribution Redistribution: How the RIPE NCC's Own Instruments Authorised and Applied a Contested Remedy
When the RIPE NCC returned EUR 8,365,249 to its members in 2020, the money did not move by improvisation. It moved under Standard Service Agreement Article 7, a Clearing House Procedure that predates the decision, and a General Meeting vote that split hard enough to show how…
Story
AS210860 without a first-party witness: what the registry's unreadable endpoint means for DFINFRA
AS210860 without a first-party witness: what the registry's unreadable endpoint means for DFINFRA intelligence summary explains the development, the public evidence available to readers, the organisations involved, the regional context, market exposure, and the infrastructure…
Story
Call for Nominations to the RIPE NCC Executive Board: What the 2026 Record Actually Publishes
The RIPE NCC has run a complete Executive Board nomination cycle for its May 2026 General Meeting. Reading the registry's own instruments — the call for nominations, the candidate and nomination procedure pages, and the document submission guidelines — shows a process that is…
Story
The Svea Abuse-Role Record: Validated Contactability, No Documented Processing
The abuse contact recorded and mirrored for Svea's legacy netblock 193.105.138.0/24 is a carrier-era inherited mailbox on the Verizon Business/UUNET lineage — registry-validated for technical deliverability but never documented to have received, answered, escalated or remediated…
Story
Control Split: Who Held Prevention and Detection on the Svea Abuse-Contact Surface
Svea Ekonomi AB merged into Svea Bank AB on 3 January 2022, but the RIPE registry entities that describe the group's abuse-contact surface have barely moved since 2021 and 2022. A timestamp-by-timestamp reading shows that recent maintenance in this chain fell almost entirely on…
Story
The Ladder That Has Not Fired: What the Public Record Shows About Enforcement on the Svea Abuse-Contact Surface
When Svea Ekonomi AB merged into Svea Bank AB on 3 January 2022, the RIPE Database inherited a problem that no merger clause can settle by itself: the group's registered abuse-contact surface. Nearly four years later, that surface still carries the dissolved company's identity in…
Story
The First October General Meeting Under RIPE NCC's New Board Structure
On 28 October 2026, at 16:00 (UTC+2), the RIPE NCC membership convenes for the October 2026 General Meeting — held online over 22–24 October and running alongside RIPE 93. By the draft timetable, the formal members-only section begins on Wednesday 28 October, electronic voting…
Story
One Upstream, Frozen Paperwork: What AS51035's Stable Shape Says About ER-Telecom's Ufa Branch
The network that carries the name "Network Operation Center JSC ER-Telecom Holding Ufa branch" has not changed its declared routing policy since September 2018, its registry role entity since October 2019, or its announcement set since December 2019. Its entire external…
Story
AS210328 Today: What the Live Record Shows — and Fails to Show — About AO ALMAZ's Cloud Network
AS210328 Today: What the Live Record Shows — and Fails to Show — About AO ALMAZ's Cloud Network intelligence summary explains the development, the public evidence available to readers, the organisations involved, the regional context, market exposure, and the infrastructure…
Story
The abuse chain that validates its first link and stops there
Every year the RIPE NCC proves that tens of thousands of abuse-contact mailboxes work. Nothing it publishes measures whether a single third-party abuse report ended in verified remediation. This report traces that gap to the policy text that created the validation mandate, and…
Story
DFINFRA and AS210860: what changes after a registry record outlives its network
DFINFRA and AS210860: what changes after a registry record outlives its 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…
Story
DFINFRA and AS210860: the cost of verifying a silent registry record
A German retail group's registry entry still names a contact for a network that has not announced a single prefix since March 2026, while a peering profile derived from the same network still promises ten address blocks and an open door. Every counterparty who consults these…
Story
The Corroboration Ledger: What the Public Record Can — and Cannot — Confirm About almazcloud.network
The Corroboration Ledger: What the Public Record Can — and Cannot — Confirm About almazcloud.network intelligence summary explains the development, the public evidence available to readers, the organisations involved, the regional context, market exposure, and the infrastructure…
Story
RIPE NCC’s 2027 Fees Count Accounts and Resources Separately
The annual fee is attached to an LIR account; several other charges attach to particular resource registrations. Reading the schedule by its units makes the 2027 change clearer—and exposes what public totals still cannot tell an operator.
Story
The Mailbox That Only Has to Exist: What RIPE's abuse-c Validation Actually Tests
Every network abuse report in the RIPE service region ends up in an operator's mailbox — and the registry's entire enforcement apparatus verifies only that the mailbox can receive mail, never that anyone reads it.
Story
RIPE Labs’ RIPE 93 winners came after the publication gate
The contest named two winners on 22 September, but its rules put ordinary editorial review first. The 11-entry page records published entrants, not every submission made.