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
333Stories
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…
Story
RIPE NCC Put “Public Arguments” Inside Its Sponsorship Conflict Test
RIPE-866 is designed to protect neutrality from money and influence. Its hardest line does something broader: it treats litigation, arbitration, public argument and other conflict as neighbours, then carries the test from a disputing party to anyone associated with one. That may…
Story
RIPE NCC’s Five-Year Restriction Now Turns on “Involved”
RIPE-791 attached a later application to two named roles around a former member: contact person and representative. RIPE-863 replaces those roles with a different test—whether a person provided fraudulent or misleading data or was `involved` in providing it. The five-year period…
Story
The Commitment Must Keep Its Name: RIPE NCC’s Missing Annual Ledger
RIPE-862 offers a precise starting chain: **Internet Resilience, Scalability and Routing Security**; the service-level objective **Security**; and the key metric **Internet Number Resources covered by ROAs and ASPA**. The next links—a costed 2027 Activity Plan and Budget…
Story
RIPE's Country Field Names a Code Without Proving Where an Address Is Used
A registry can preserve a perfectly valid country code while leaving its geographic subject unresolved. The distinction matters whenever `country: NL` is copied into security, compliance, market or infrastructure decisions as though it located every address in the range.
Story
RIPE RIS Generated the BGP Snapshot. Delivery Still Failed
The 25 August incident did not begin with a failed route collector. RIPE NCC says the 16:00 UTC bview files had been generated, yet they did not reach the public archive after a failover. That distinction turns a small status notice into a useful test of where a public…
Story
RIPE’s Status Field Is a Registry Class, Not a Network Health Check
A single line in an address record can look like an operational verdict. In the RIPE Database, it is nothing of the kind: `status` locates an IPv4 record inside a policy hierarchy, while routing and reachability must be observed elsewhere.
Story
RIPE Atlas Closed a Probe-Assignment Incident Without a Measurement Ledger
A missing vantage point can describe the Internet, the probe or the scheduler. On 18 August, RIPE Atlas made the third possibility explicit: measurements using an area choice other than `worldwide` had trouble receiving probes. The backend was fixed; the public record still does…
Story
RIPE's IPv6 PI Draft Has a Trigger but No Transition Receipt
Nine `/48` assignments can remain a valid deployed state while nothing changes. The next request for address space is different: it can activate a next-nibble decision, a contiguity test, a new prefix and a six-month return clock. Proposal 2024-01 names that trigger but does not…
Story
Khipu's Local Archive Preference Creates an Evidence Expiry Boundary
A historical Khipu view can reach farther back than the archive shelf available on the workstation opening it. Once the number of local `ip2asn`, `ixp`, `ip2country` and `asn2country` snapshots is a preference, reproducibility has an expiry boundary that the measurement date…
Story
RIPE's First-ASN Proposal Removes One Test but Leaves Three Records Open
RIPE's First-ASN Proposal Removes One Test but Leaves Three Records Open 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
The Signed Outage: What Orange España Revealed About RPKI Write Authority
Orange España showed how a hostile but valid ROA can pass through validators and local policy, turning account access into staggered route loss.
Story
One Document Store Put Five RIPE NCC Workflows on Hold
A resource transfer can wait because a policy question is unresolved, because evidence is incomplete, or because the filing cabinet is being upgraded. On 22 August, RIPE NCC members encountered the third case. The distinction matters: a planned administrative pause is not a…
Story
RIPE NCC Split ENUM's Future From 23 Troubled Delegations
A draft prepared for September's ITU-T Study Group 2 meeting makes a careful retreat from a system-wide question. RIPE NCC now says Public ENUM should continue while 17 non-operational and six partly faulty delegations are handled as individual registry cases. The change is less…
Story
RIPE NCC’s Dubai Company Has One Member. Where Do the Association’s Members Enter?
The member register of RIPE NCC Middle East FZ-LLC has the shortest possible answer: one corporate member, the Dutch RIPE NCC association. That clarity is useful. It also exposes the real governance question. Ordinary RIPE NCC members elect the parent association’s Executive…
Story
RIPE 93 reaches its plenary proposal date; lightning talks remain open
RIPE 93’s published call puts 14 August at the plenary threshold, while preserving a conditional late path and an open route for lightning talks.
Story
RIPE 93 plenary proposal deadline reaches 14 August, while lightning talks remain open
RIPE 93’s official call sets 14 August as the plenary proposal deadline. The meeting still lists lightning talks as open, and says later plenary proposals may be considered only if time slots remain.
Story
RIPE NCC schedules a document-management maintenance window for 22 August
RIPE NCC says its production Alfresco upgrade will make membership applications, resource transfers and requests, M&A requests, and ticket-dependent actions unavailable from 08:00 to 20:00 CEST on Saturday 22 August. It is a planned service window, not an incident.
Story
RIPE NCC listed an IPv6 Security Training Course in Oslo for 14 August
RIPE NCC’s published schedule placed a one-day IPv6 Security Training Course in Oslo on Friday 14 August 2026. The listing frames it as member training, not as a statement that every RIPE region network faces the same exposure or that the session has already produced an…
Story
RIPE NCC postmortem traces NRTM desynchronisation to invalid RPSL handling
RIPE NCC’s latest postmortem narrows an August NRTM mirroring failure to a pair of software behaviours: an invalid RPSL object could enter the database, and the stream stopped rather than passing that entity with an error record.