- RIPE NCC’s proxy deadline appears as 4 October and 14 October
One RIPE NCC notice lists 4 October as the proxy-vote deadline; the General Meeting and proxy pages list 14 October. The Articles’ two-week rule points to 14 October for a meeting that begins on 28 October, but the published mismatch remains unexplained.
Primary articlePublished 2026-10-11
- RIPE Database incident stayed under monitoring for 24 hours after fix notice
RIPE NCC said some web-application requests were failing with 502 responses on 7 October. A fix moved the incident to monitoring one minute after the first public report; resolution was posted 24 hours and 34 minutes later. That interval measures status states, not the length or scale of user impact.
Primary articlePublished 2026-10-10
- RIPE NCC makes chair support open-ended; its public procedure still cites 2026
The RIPE NCC Executive Board has removed the scheduled sunset from support for Working Group Chairs’ physical attendance at RIPE Meetings. Yet the published procedure still says the previous extension ends in 2026. Before the next application window, the organisation needs one current, dated account of who decides, what is covered and when the rule can be reviewed.
Primary articlePublished 2026-10-10
- RIPE NCC’s August IPv4 rows barely changed as address volume fell 74%
September’s 1,253,632 matches the POLICY subtotal in four public tables; another 285,184 addresses are labelled MERGER_OR_ACQUISITION.
Primary articlePublished 2026-10-09
- RIPE Recovered RRC12’s Files; Its Restart Bug Still Needs a Structural Fix
RIPE NCC says it has regenerated RRC12’s missing BGP files since 2 October. The same incident update says the configuration has been corrected, but the latent restart bug behind the repeated timeouts still awaits a structural fix.
Primary articlePublished 2026-10-07
- RIPE NCC designates two Foundation board members after Falk’s notice
The RIPE NCC Executive Board has named two people for the Rob Blokzijl Foundation board after Falk von Bornstaedt said he would step down. The Foundation’s own rules keep a separate appointment decision with its board.
Primary articlePublished 2026-10-07
- RIPE NCC members face a CEO Board-vote decision in October
The proposed Articles would keep seven member-elected non-executive seats and place the CEO on the same Board as an executive member with a vote. The Executive Board has approved the text for member consideration; it is not yet in force.
Primary articlePublished 2026-10-06
- RIPE NCC’s €10.5m infrastructure plan enters member review
The proposed 2027 budget lifts capital expenditure to €10.5 million for a renewal programme running through 2028. The Board has approved publication of the draft, not the final plan; members are being asked to discuss it and provide feedback before a December version is approved.
Primary articlePublished 2026-10-06
- RIPE NCC’s LIR pause also covers pending requests
RIPE NCC’s temporary restriction on acquiring additional Local Internet Registry accounts took effect from 29 September and includes requests already in progress. The decision pauses an intake route; it does not order the closure or consolidation of accounts already held, and it leaves future IPv4 Waiting List eligibility to the community policy process.
Primary articlePublished 2026-10-06
- RIPE NCC Reversed a Package Update After Its RPKI rsync Service Went Offline
RIPE NCC restored the named RPKI repository service by reverting an rsync package on 2 October. Its incident record explains the recovery, but does not measure how many relying parties were affected.
Primary articlePublished 2026-10-06
- RIPE’s RRC12 Output Stalled After a High-Volume DE-CIX Peer
RIPE NCC says an unusually large stream of BGP messages from one DE-CIX peer repeatedly timed out the process that turns RRC12 updates into public files. Its archive still ended at 01:00 UTC on 2 October when checked 18 hours later.
Primary articlePublished 2026-10-02
- RIPE NCC is changing the RPKI key. The harder question is what it can touch
RIPE NCC is moving its RPKI dashboard and API credentials towards OpenID Connect. The more consequential disclosure sits lower on the same planning page: a proposed routing beacon was held back because its API could edit ROAs across all RIPE NCC space. Together, the two items set a useful test for infrastructure leadership—modern identity is not yet least authority.
Primary articlePublished 2026-10-01
- 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.
Primary articlePublished 2026-09-29
- 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.
Primary articlePublished 2026-09-28
- RIPE-NONAUTH’s 0.006% Query Share and 20% of NRTM Requests Measure Different Things
RIPE NCC has published two statistics about RIPE-NONAUTH that describe different access paths, not one utilization rate. As its Q4 cleanup proposal moves to “Starting,” the distinction matters: neither number identifies dependent operators or proves that removal is safe or unsafe.
Primary articlePublished 2026-09-28
- RIPE NCC’s Geneva Briefing Invoked Measurable Progress, Without Naming a Measure
At a 17 September session co-hosted with the ITU and the Permanent Mission of Lebanon in Geneva, the RIPE NCC placed the RIR function between digital-policy goals and operational delivery. Its post-event account describes partnerships, capability and capacity building as routes to “measurable progress”, but names no project, baseline or follow-up test. The release records a framework, not a demonstrated outcome.
Primary articlePublished 2026-09-28
- RIPE NCC’s October Vote Sends Surplus and Deficit in Opposite Directions
The draft resolution for RIPE NCC’s October General Meeting assigns a 2026 surplus to reserves but a deficit to members in 2027. If members reject it, the agenda describes the reverse allocation; the 2025 meeting approved that alternative.
Primary articlePublished 2026-09-27
- RIPE Withdrew Its IPv6 PI Rewrite. The Rule an Operator Uses Did Not Move
An organisation planning an IPv6 PI request has two RIPE records to read. One, the proposal page, still showed a draft in Review Phase when checked on 27 September. The other, a working-group chair's message dated three days earlier, said that draft had been withdrawn. Neither record hands the organisation a larger prefix or changes how it may serve another party. The operative answer is in the published policy that the draft never replaced.
Primary articlePublished 2026-09-27
- RIPE’s Central Asia Path Comparison Needs a Sample Ledger
Three maps can show change only if the rows behind them stay countable. RIPE NCC’s CAPIF 5 report presents an encouraging direction for Central Asian Internet paths across 2022, 2024 and 2026. The next useful publication is not a more confident adjective. It is a compact receipt showing which measurements, probes, successful traces and classification rules produced each comparison.
Primary articlePublished 2026-09-27
- RIPE Fellowship Offers Full Support. Travel Feasibility Sits Outside the Published Score
RIPE NCC has opened its Fellowship for two 2027 meetings with a clear promise of coaching, training and full support. Its detailed programme page also describes visa, cross-border travel and reimbursement constraints that may leave part of the journey with the applicant. The missing element is not another benefit list. It is a visible state connecting a merit decision to a support plan that can actually be delivered.
Primary articlePublished 2026-09-24
- RIPE NCC's Signed Checklist Is Waiting Behind Two Other Jobs
A standard can exist, a community can ask for a service, and a registry can still have no date for delivering it. RIPE NCC's September RPKI plan puts Resource Signed Checklists behind identity and assurance work, with an API as the possible first product. The distinction matters to anyone designing a workflow around a signature that is meant to leave the global RPKI repository altogether.
Primary articlePublished 2026-09-24
- RIPE NCC Closed the Test API Incident. The Recovery Join Is Missing
Four status updates show a pilot service moving from investigation to resolution in 37 minutes. They do not show the small set of facts that would let a user connect that green status to a particular test operation, a checked isolation boundary and a completed reconciliation.
Primary articlePublished 2026-09-20
- RIPE NCC Kept the Lameness Checks and Stopped the Emails
In 2009, RIPE NCC separated two activities that are often mistaken for one: it continued periodic checks of broken DNS delegations and ended the bulk email alerts generated from them. The decision is a useful historical operating case in what an infrastructure measurement can prove—and what it cannot prove about delivery, operator attention, repair and user impact.
Primary articlePublished 2026-09-20
- RIPE’s RDAP Marks a Mixed AS Block Reserved at Either Boundary
A new unit test makes an old classification rule unusually easy to see: a candidate AS-BLOCK needs only to overlap a configured reserved interval for the whole object to receive the `reserved` status. That is a cautious registry rule, but a poor substitute for the status of every ASN inside the block.
Primary articlePublished 2026-09-15
- 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 distinction is how it became applicable: an observed route attribute, a matched rule and the rule’s provenance are three different facts.
Primary articlePublished 2026-09-14
