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
505Stories

Story
A Membership Fee Filed as an Internet Registry: The RIPE NCC Charging Scheme 2020 Record
One public entry describes a Switzerland-based internet registry that performs registry functions for internet number resources. The page that entry cites presents a numbered charging scheme. Both sentences come from the same publisher, and only one of them describes something…

Story
RIPEstat’s API Came Back. Its BGP Clock Was Still Running Behind.
A 32k file-descriptor ceiling tripped the RIS Looking Glass database. The interface recovered first; a slice of RRC25’s peer data was still catching up that evening.

Story
RIPEstat Reopened. A Tenth of RRC25 Was Still Behind.
A 32k file-descriptor ceiling shut several RIPEstat APIs. The service recovered before the Looking Glass data caught up, leaving two clocks for one incident.

Story
RIPE’s RPKI archive was fine. Its front desk forgot the publishers.
A routine Krill restart left delegated CAs outside the publication door for two hours and 43 minutes. The old records stayed put.

Story
RIPE’s RPKI Publisher Opened Before the Guest List Arrived
For 163 minutes, delegated certificate authorities met a service that was running but did not recognise them. RIPE NCC says the repository kept its old contents and publication resumed. The failure sat at the entrance: Krill started before its publisher configuration was ready.

Story
RIPE’s Spare Balancer Sent New Writes to a Read-Only Database. The Old Ones Kept Working.
An operator's first update after a failover met a closed door. An older database connection could still reach the writable primary. RIPE NCC's new postmortem explains the intermittent failure behind its October registry incident: redundancy moved the traffic, but a misconfigured…

Story
RIPE Froze Extra LIR Accounts. Twenty-Eight Survey Replies Pointed to Permissions.
The board shut the door on new extra accounts; a member survey showed why some operators kept walking through it. The answer is partly in the access controls, not the address pool.

Story
RIPE Refiled 16,384 Addresses and an ASN at 10:23. The Routes Kept Their Number.
RIPE Refiled 16,384 Addresses and an ASN at 10:23. The Routes Kept Their Number. intelligence summary explains the development, the public evidence available to readers, the organisations involved, the regional context, market exposure, and the infrastructure consequences that…

Story
RIPE Moved an ASN and Three Blocks to Elisa. One of Its Four Routes Belongs to Someone Else.
RIPE Moved an ASN and Three Blocks to Elisa. One of Its Four Routes Belongs to Someone Else. intelligence summary explains the development, the public evidence available to readers, the organisations involved, the regional context, market exposure, and the infrastructure…

Story
RIPE Has Two Receipts for AS209601. The Names Between Them Are Missing.
RIPE Has Two Receipts for AS209601. The Names Between Them Are Missing. 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
RIPE Registered ITCare’s /24. The Next /24 Reached 321 Peers; This One Reached Zero.
A Polish /24 changed hands on RIPE NCC’s transfer ledger. At the next RIS snapshot, its exact route reached no full-table peer; the numerically adjacent /24 reached almost all of them. The receipt and the route were telling different stories.

Story
LEONIX’s /24 Was on the Route. RIPE’s Transfer Receipt Came 50 Days Later
LEONIX’s /24 Was on the Route. RIPE’s Transfer Receipt Came 50 Days Later 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 Moved 243 Records to 2Connect. Two Big Routes Kept Their Numbers.
On 1–2 October, RIPE NCC put 234 IPv4 blocks, three IPv6 allocations and six ASNs under one recipient. The register moved fast. Two large sampled routes kept the same BGP origin numbers before and after the processing dates, while those numbers ended up with different registered…

Story
RIPE Moved the /22. The Two /24s Kept Their Own Names
RIPE NCC recorded a whole-block transfer to Tru Enology Investments Ltd on 3 November. Inside that block, two live /24s still carry separate registrants and separate BGP origins.

Story
RIPE’s Load Balancer Failed Over. The Portal Kept Calling the Old Connection.
A registry's address ledger can be intact while the member-facing window into it goes dark. On 3 November, RIPE NCC restored access to resource information by clearing stale database connections after a load-balancer failover. The immediate repair was specific; the design…

Story
RIPE Stamped Two Valoo Blocks at 12:59:16. Only One Can Feed Other Networks.
Two RIPE NCC transfer tables show Suomen Datasafe Oy passing an IPv4 /22 and a separate /24 to Valoo Oy on 3 November. Both exact registry entities were created at 12:59:16 UTC. The /22 is `ALLOCATED PA`; the /24 is `ASSIGNED PI`. Same clock, different authority over the next…

Story
RIPE Closed the Dashboard Ticket at 21:06. Its Status Page Kept the Dashboard Under Maintenance.
RIPE NCC's RPKI notice declared its Dashboard work complete six minutes after the start. A second live maintenance record still included that same Dashboard and remained in progress. The status page had two answers for one component at the moment an operator needed one.

Story
RIPE Changed the Holder. Ilbit Stayed on the Edit Lock.
A Russian /23 moved from Ilbit Telecom Ltd. to Tencom Ltd. on RIPE NCC's transfer ledger. The exact address card names Tencom, but its `mnt-by` still includes `ILBITTEL-MNT`. The new holder's organisation card uses a different maintainer. The receipt and the edit path are…

Story
RIPE NCC Raises the LIR Fee by €94. Its Registry Slice Falls by €4.
The approved 2027 account fee is higher. The draft budget's own fee chart assigns fewer euros to the Registry than the 2026 chart did. The big movements are technology and depreciation, not the address book.

Story
Elisa Took the Allocation; the IP Lookup Still Says NKV
RIPE NCC recorded three Finnish transfers to Elisa Oyj on 3 November. The parent records moved together. For 9,216 addresses, an ordinary address lookup still lands on older, more specific NKV cards. The registry is showing two floors of the same building.
