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
332Stories
Story
RIPE Atlas Warns of Bad NTP Offsets. Thousands of Connected Probes Still Report Firmware 5120
RIPE NCC has named the faulty field and the replacement release. Its public API also shows that the affected version remains connected at scale. What is still missing is a correction record that joins those two facts to the result rows downstream users actually analyse.
Story
RIPE NCC Began Verifying Roughly 1,600 No-Contract Legacy Holders. Its Q3 Plan Still Describes Two-Place Updates
RIPE NCC has a sensible plan to give old resource records a clearer organisational anchor. Its own quarterly plan also reveals the awkward middle of that migration: one change may still have to be performed manually in two places. The test is not whether the campaign looks…
Story
RIPE NCC Reports a 467-Day IPv4 Wait. The Queue Needs a Flow Ledger
RIPE NCC’s August member update says 757 LIRs were waiting for IPv4 space and the first LIR had been in line for 467 days. Its public chart records the queue’s size and its oldest wait, but those two stocks cannot show whether movement came from allocations, new requests…
Story
RIPE NCC Needed 394 Supporters Before a Member Resolution Could Reach the Agenda
The number 394 was not a vote result. It was the price of admission to the vote: a cycle-specific calculation deciding whether a member-authored subject and its verbatim resolution would enter the General Meeting agenda. The rule has a sound institutional purpose. The public…
Story
Four Counterparty Pairs Made 89% of RIPE NCC's July IPv4 Transfer Total
RIPE NCC's August member update says 5,935,616 IPv4 addresses were transferred in July, 4,159,744 more than in June. The public transfer tables reproduce both numbers exactly. They also change the meaning of the headline: four repeated from-to pairs account for 5,299,712…
Story
RIPE NCC’s Two Voting Codes Need a Credential Map
RIPE NCC tells October’s voters to expect two codes in two emails. That is a useful instruction, but it is not yet an account of the control. The names “Code 1” and “Code 2” describe a user journey; they do not show what each credential proves, who can recreate it, or when a…
Story
RIPEstat Wants Better AS Names—and a Map of Which ASNs Are One Entity
RIPEstat Wants Better AS Names—and a Map of Which ASNs Are One Entity 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 93 Dropped Childcare. “Low Demand” Has No Public Denominator
RIPE 93 will not provide organised childcare. The meeting team gave a concise reason on 28 August: demand and participation had been low in recent years. That may be a sound operational judgment. The public record does not yet let a reader test it, because the offer itself…
Story
RIPE NCC’s Twelve Arbiter Candidates Need a Rule for Six Places
Passing an eligibility test is not the same thing as winning an appointment. RIPE NCC’s 2026 call for arbiters was written as a nomination followed by member approval. Twelve volunteers then qualified for six available places. That changed the practical question from “may these…
Story
RIPE NCC's New CTO Inherits a €12.2m Estimate, Not a Mandate
Sjoerd Wolthers becomes RIPE NCC's permanent chief technology officer on 1 September. The appointment settles who will lead the technology function. It does not settle a separate question left open in the latest public Board minutes: whether, how and on what evidence RIPE NCC…
Story
RIPE Marked the Upgrade Complete. Retrieval Failed Twice Afterward
At 17:56 CEST on 22 August, RIPE NCC marked its Alfresco maintenance complete. On Monday afternoon, document creation still worked but some files could not be viewed or downloaded. On Wednesday, a second incident began; RIPE NCC later changed the document system’s configuration…
Story
RIPE NCC's One-Tier Board Needs an Authority Migration Table
RIPE NCC wants its legal structure to catch up with the way it says the organisation already works. The proposed one-tier Board would put the Managing Director on the Board as an executive director and recast the elected Executive Board members as non-executive directors. That…
Story
ACSK-RIPE and AS210263: A Contact Handle Is Not a Control Title
ACSK-RIPE and AS210263: A Contact Handle Is Not a Control Title 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's Appointed NRO Seat Needs a Decision Receipt
RIPE NCC has opened a public door into one of its three NRO Number Council seats: nominations, eligibility checks and support statements are visible. The final passage is different. The Executive Board will appoint the member without a community vote, while the published election…
Story
RIPE NCC's 708 Extra Accounts Need a Migration Ledger
RIPE NCC has identified a rare simplification window. Only 410 members now operate more than one Local Internet Registry account, yet their 708 additional accounts keep complexity embedded across registry, billing, compliance and portal systems. Closing an exception is not the…
Story
K-root Says It Meets Every Expectation. The Evidence Is Uneven
RIPE NCC has answered the root-server community's operating expectations one by one. That makes K-root easier to question than a service hidden behind a general assurance of competence. Yet RIPE-859 also reveals a governance gap: a public metric, a control description and the…
Story
RIPE's NRTMv3 Stream Can Skip an Invalid Object. A Moving Serial Is Not a Completeness Receipt
RIPE Database release 1.124 made a small change with a large evidentiary consequence: the NRTMv3 server should skip invalid objects. Keeping a replication stream alive may be the right operational choice, but continuity alone can no longer answer the mirror operator's most…
Story
RIPE-861 Recommends Off-List Nominations. The Candidate List Needs a Receipt
RIPE's new guide gives a quiet volunteer a private way to approach a continuing working-group chair. That can widen participation. It also moves the first step outside the public archive, making the later conversion from interest to a complete candidate list the part that needs…
Story
Where Member Notice Stops: RIPE-865 and the Burden of a Public Record
RIPE-865 preserves the general position that RIPE NCC members are informed when authorities seek their data or registry action, unless notice is expressly prohibited. Its eEvidence section creates a different notification state: confidentiality applies, and the RIPE NCC cannot…
Story
RIPE’s CoC Draft Joins Final Appeal and Team Removal
A second RIPE Code of Conduct draft would let the RIPE Chair appoint, continue and remove community reviewers at discretion. The current appeal process already names that office as the final assessor. Neither power proves interference. Their combination does create a hard…