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.
Europe and Middle East Institutional Trends
Your bank says paid. RIPE NCC may still see an unpaid invoice.
A bank transfer and a registry receipt are different records. RIPE NCC says an unclear payment reference can leave an already paid invoice showing as outstanding. Its current procedure stops new and open service requests and suspends a member at 60 days without received payment.…
Story
RIPE’s Policy Kitchen Has 24 Regulars. The Registry Keeps Reading the Recipes.
At RIPE 93, a veteran policy entity counted a small active discussion core and proposed a manual that initially changes no rule. The argument is about who supplies meaning when the community leaves gaps: the authors, the readers, or RIPE NCC staff trying to run the registry…
Story
RIPE Lets PI Holders Manage ROAs on Screen. Its API Still Sends Them Away.
RIPE NCC gives sponsored resource holders a Dashboard for routing certificates and ROAs. Its automation interface refuses their certificate authorities. The promised replacement for an old, never-expiring key could finally bring those holders through the API door, but the public…
Story
RIPE NCC Has 8,000 Undeliverable Addresses. If Every Recipient Fails, No Notice Gets Through.
A RIPE Database update can be acknowledged while every designated watcher misses the notice. RIPE NCC's own transcript names the hard edge: when all notification recipients fail, nobody is left to warn.
Story
NIS2’s ENISA Registry Is Growing. Its Access Clause Still Names the Old List.
The Commission wants ENISA’s registry to include essential and important entities, then gives competent authorities an access sentence that names a narrower set of service providers and air carriers. That is a small drafting seam with a large consequence: the proposal says who…
Story
RIPE Wants New Voices. First, Take the English Course and Pass a Quiz.
The Fellowship’s new call puts a two-hour RIPE 101 course and a quiz before the application form. The course page lists English; RIPE publishes no quiz pass rate.
Story
RIPE NCC Named Six Arbiters. Its Published Vote Report Leaves Out the Count
The October result report names each winner and seat, then stops before the numbers that would show how an instant-runoff election reached those six outcomes. The arbiters’ announced terms run through the Autumn General Meeting in 2031.
Story
RIPE’s database failed for eight hours. No reverse-DNS delegation changed.
RIPE NCC’s first alert said database failures were affecting reverse DNS. Two days later, its investigation drew a sharper line: every failed request either asked for no change or failed a validation check. The outage interrupted the write path; the published delegation stayed…
Story
RIPE Re-Elected Both Plenary Gatekeepers. The Vote Count Stayed Offstage.
RIPE 93 gave two committee seats to their incumbents again. The public result named the winners, but not how many people cast a vote for the committee that selects the meeting’s plenary agenda.
Story
RIPE Found 37% of ROA Definitions Off BGP. Who’s Cleaning Up?
RIPE NCC says about 37% of AS-prefix definitions in ROAs were not seen in BGP. Some are deliberate backups. Others may be old permissions that outlived the route, and the incentive to create them is stronger than the incentive to retire them.
Story
RIPE’s Invoice Portal Stumbled. The Billing Clock Starts at Each Invoice
On 29 October, invoices intermittently disappeared from the LIR Portal and payment confirmations were delayed for 4 hours 19 minutes. RIPE NCC restored invoicing after maintenance the previous day, but its notice did not say how many invoices were affected or how members should…
Story
RIPE Put the Version Trail on the Web. Its Manual Still Sends Users to the CLI.
RIPE NCC has brought version history and comparisons to the RIPE Database query page for selected entities. Its official guide still describes those history commands as a command-line job, while the real limits of the record sit elsewhere.
Story
The Deficit Rule Passed. It Drew 24 Points Less Support Than RIPE’s Articles Changes.
RIPE NCC members approved both resolutions at the October General Meeting. The measure that could put a 2026 deficit on members’ 2027 bill won a much narrower weighted majority than the amendments to the association’s Articles.
Story
The Rob Blokzijl Award Missed 2026. The Board Admitted It Let Volunteers Down.
The Foundation had named a 2026 ceremony, called for volunteers and assigned the award committee to solicit nominations and choose a recipient. At RIPE 93, its secretary said the Board failed to give that committee enough support. The 2027 restart now needs a calendar, not…
Europe and Middle East Institutional Trends
RIPE NCC Members Put Any 2026 Surplus in Reserve—and Any Deficit on the Membership
The October General Meeting approved a one-year settlement rule: any excess contribution paid in 2026 goes to RIPE NCC reserves, while any 2026 deficit is covered by members in 2027. The decision assigns the downside before it assigns a collection formula.
Story
RIPE NCC Shut Four Public Sites. They Returned in 45 Hours.
Four public hostnames used by RIPE NCC, NRO and ASO went offline during a critical PHP response. The status log records a 44-hour, 55-minute path from shutdown to full restoration.
Leaders
Alena Muravska’s 57 out of 107: RIPE Labs counts articles, not voices
Alena Muravska’s 2025 review gives RIPE Labs a concrete outside-contribution figure: 57 of 107 articles came from community authors. The count says how many pieces appeared. It leaves the more consequential count—how many people returned—off the page.
Story
RIPE Atlas Wants Your Spare Raspberry Pi. It Still Has to Find the Missing Networks.
RIPE NCC is exploring a flashable image that would turn a volunteer's own device into an Atlas hardware probe. The box is easier to find than the network vantage point that makes it useful.
Story
RIPE NCC Contacted the Holders. 51.7% of Legacy Ranges Still Await a Reply.
The registry says it has contacted all roughly 1,500 legacy holders. Its new range-level tally shows how much verification work remains before anonymous records go public in 2027.
Story
RIPE NCC Wants Two Independent Data Centres. The Switch Between Them Is the Story.
The registry plans to replace a shared network stretched across two nearby facilities with autonomous sites in Western Europe. Inside each site, systems would run active-active. Between sites, one would stand by. That last handoff will decide whether the rebuild delivers…