Region
RIPE Service Region — Europe, Middle East and Central Asia
RIPE Service Region — Europe, Middle East and Central Asia regional intelligence explains how companies, people, policy moves, network operations, investment signals, data centre demand, telecom execution, and market constraints shape infrastructure delivery in the same geographic market or governance area. The page connects published coverage with evidence, regional actors, operating dependencies, market context, and customer or regulatory exposure that may otherwise sit across separate topic or company pages. Readers can compare who is active, which signals are backed by public evidence, how local execution risk connects to broader internet infrastructure strategy, and what changes may affect customers, partners, regulators, or capital planning. Readers can understand the geography, the relevant infrastructure sectors, the public evidence base, and the practical questions that make the regional page more useful than a short listing of articles.
Story
DFINFRA and AS210860: the cost of verifying a silent registry record
A German retail group's registry entry still names a contact for a network that has not announced a single prefix since March 2026, while a peering profile derived from the same network still promises ten address blocks and an open door. Every counterparty who consults these…
Story
The Mailbox That Only Has to Exist: What RIPE's abuse-c Validation Actually Tests
Every network abuse report in the RIPE service region ends up in an operator's mailbox — and the registry's entire enforcement apparatus verifies only that the mailbox can receive mail, never that anyone reads it.
Story
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.
Story
Who Controls Abuse in the RIPE Region? The Measurement Surface and the Remedy Surface
Every malformed abuse report in the RIPE service region eventually arrives at the same question: who is actually responsible for stopping abusive use of internet number resources? The RIPE NCC's own published documents give an unusually precise answer, and it is not the one…
Story
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…
Number Resource Society
RIPE NCC's 2020 Surplus Redistribution: One Recorded Resolution, One Number, and What Changed Since
When the RIPE NCC returned 11 million euros to its members, the instrument of authority was a single General Meeting resolution — and the record of how it was granted still frames how the membership controls the registry's money today.
Story
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.
Number Resource Society
How a Passkey Setup Guide Became a Directory 'Institution'
A directory card listing an organisation called "Setting up 2FA with Passkey" in Taiwan points, in reality, at a section heading inside RIPE NCC's login-security documentation. The gap between the label and the underlying entity is itself the story: it shows how automated…
Story
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…
Story
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…
Story
DFINFRA and AS210860: The Registry Says One Thing, the Routing Table Says Nothing — and Neither Has Moved
DFINFRA and AS210860: The Registry Says One Thing, the Routing Table Says Nothing — and Neither Has Moved intelligence summary explains the development, the public evidence available to readers, the organisations involved, the regional context, market exposure, and the…
Number Resource Society
A Remedy in Writing: RIPE NCC's Abuse-Contact Regime and Its Unused Last Resort
The RIPE registry's abuse-contact regime is usually described as a validation programme. Its own paperwork describes something narrower: a periodic check that a mailbox is configured correctly, backed by an escalation ladder that ends in deregistration. The first half of that…
Story
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…
Story
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…
Story
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.
Story
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…
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
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 Atlas Counts Probe Farming by a BGP Prefix. The Cohort Can Move Without the Probe
A probe can stay on the same shelf, under the same account and on the same access line, yet acquire different neighbours for an admission rule. RIPE Atlas limits software probes partly by the IP prefix “as seen in BGP”. That is a defensible way to protect a shared measurement…
Story
RIPE NCC’s K-root Refresh Needs Three Acceptance Records, Not One Batch Status
Amsterdam can be refreshed while the three-site programme remains in progress. That is not a contradiction; it is a warning about the unit of evidence. RIPE NCC has named three K-root core sites whose seven-year-old routers and servers were due for replacement. The useful public…