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
331Stories
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.
Story
RIPE NCC arbitration: the database lock and the ruling clock
RIPE NCC describes an interim lock on database records and a separate timetable for arbitration. For members, the crucial questions are when that timetable starts, what remains usable during review and how a ruling takes effect.
Story
RIPE’s RDAP Marks a Mixed AS Block Reserved at Either Boundary
RIPE’s RDAP Marks a Mixed AS Block Reserved at Either Boundary 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
RIPEstat Explains 12859:4000 With 12859:4xxx. The Wildcard Is Evidence
RIPEstat’s Looking Glass can place a useful sentence beside an opaque BGP community. In one frozen response, however, the observed value `12859:4000` received the description “customer routes” from the broader expression `12859:4xxx`. The explanation may be right. The missing…
Story
RIPE NCC Has 110 Sanctions Investigations. Its Table Has No Clock.
RIPE NCC’s latest sanctions report makes the size of its screening work visible: the cumulative register reached 2,172 alerts, with 110 still under investigation on 2 July 2026. What the table cannot show is equally consequential. A reader can see where cases sit, but not how…
Story
RIPE WHOIS Gives Invalid API Keys an Audit Identity
A failed credential usually looks like absence: no user, no permission, no successful update. In the current RIPE WHOIS source, however, the failure path can carry one durable-looking fact into its audit representation—the API key ID supplied as the Basic-auth username—even when…
Story
RIPE’s Plain-Text History Needs Its Request Context
Whois 1.124 made historical entities easier to read as plain text. The returned body is still filtered history, while the structured response carries a separate revision label. Saving the text is not the same as saving what identifies it.
Story
Sagan Can Mark a Traceroute Successful Without a Reply From the Destination
One Python flag tests a non-error reply at the end of the supplied trace. Another tests the destination address. Keeping those answers separate is the difference between reading a measurement and awarding it a meaning it has not earned.
Story
RIPE Atlas Tools’ Ten-Second Timeout Stops Before the Atlas API
A setting added in June reaches the geocoder but not the reviewed measurement-creation path. A bounded source test shows where the budget is lost, not how long any live job waited.
Story
Starla Uses RIPE Atlas Version Numbers. They Do Not Name Its Executable.
A Rust implementation can speak the probe’s language without becoming the same measuring instrument. Starla makes the distinction visible in source: its own package version, its compatibility numbers and its registration identity answer different questions.
Story
RIPE NCC Is Running Four Security Programmes at Once. Their Handoffs Need a Public Map
RIPE NCC’s quarterly plan puts audit work, risk management, application security and monitoring on four adjacent lines, all marked “In progress”. That is useful disclosure, but not yet a view of how evidence moves between them. A small public handoff map would let members…
Story
RIPE NCC Can Audit IPv6 Resources. Its Policy Does Not Link the Procedure
The registry’s authority is not the disputed point. The problem is navigational: two IPv6 clauses tell LIRs what they must produce during an audit, while the document never takes the reader to the procedure that explains why an audit starts, how far it can reach and how an…
Story
RIPE NCC Lets Operators Sign ASPAs Without Showing the Providers It Sees
RIPE NCC has made ASPA signing possible and tells operators to list every real upstream. Its public guide also says the Dashboard offers no BGP-derived hint about who those upstreams might be. The missing interface is not an automatic answer but an evidence receipt that helps a…
Story
RIPE’s NRTMv4 Source Gate Reads a Replica. Its Fallback Does Not Cover the Gate
A three-file code change gives RIPE NCC’s NRTMv4 service a sensible read path and leaves one unusually precise question behind: when a source is new, what proves the catalogue reached that path before the service begins treating it as authoritative?
Story
RIPE Atlas Put Reconnects and Liveness Through One Event Processor. A Slow Backend Blocked Both.
A RIPE Atlas software probe could have working Internet access on 8 June and still be shut out of the measurement network after a routine disconnect. The public incident record explains why: reconnect work and controller-liveness evidence passed through the same event processor.…
Story
RIPE NCC’s Four Stale IPv6 Glue Records Are Now Three. Root Repair Was Never a Batch.
One of four old IPv6 glue mappings identified after RIPE NCC’s AuthDNS renumbering has aligned with the nameserver’s current address. The other three have not. That split result reveals the real unit of root-zone maintenance: one delegation, one authorised decision and one…
Story
RIPE Atlas Firmware 5130 Added an OpenWrt Hardware Architecture. The Rollout Needs More Than a Version Number
Firmware 5130 gives RIPE Atlas a new `openwrt-hwprobe` architecture for next-generation firmware on existing hardware probes. That is a concrete engineering change, not merely a roadmap line. Yet the number 5130 can identify a release without proving which source, toolchain…
Story
A Space IPv6 Draft Gives Every Planet Up to Five RIR Prefixes. It Never Defines the Region.
The appealing part of a new space-address proposal is that it does not start a sixth registry from scratch. The harder part is hidden in two words. Applicants would use their “appropriate RIR”, but a moving spacecraft has no obvious place on a map built for terrestrial service…
Story
RIPE NCC’s AuthDNS Ledger Counts 43 Nodes but Not the Eyeball Coverage They Deliver
RIPE NCC has made the objective unusually clear: put AuthDNS where poorly served networks can actually reach it. Its public inventory can show that 43 hosted instances are operational. What it cannot yet show is whether each new map pin changed the anycast catchment that matters.
Story
RIPE’s IPv6 PI Draft Reserves Growth Space. Partial Transfers Can Make It Unusable.
RIPE’s current IPv6 PI proposal tries to make future growth easier by reserving a larger nibble-boundary envelope around a new assignment. Its own impact analysis identifies the catch: if the assigned block can be transferred in pieces, the untouched reservation may no longer be…