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
RIPE NCC’s new risk register starts with the whole organisation
A top-down view of high-impact risks changes where the discussion begins; the September Board minutes tie some treatments to the right budget.
Story
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.
Story
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…
Story
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…
Europe and Middle East Institutional Trends
RIPE’s Abuse-Contact Check Stops at Mailbox Reachability
A registry can make an abuse address easier to find and test whether its technical path looks configured. Those signals matter. They still leave a separate question unanswered: what happens after a real complaint arrives?
Story
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.
Story
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.
CASE FILE
The Operator That Isn't On Its Own Network: Testing almazcloud.network's Delivery Claims Against AS210328
The DIAMOND-branded cloud operator behind almazcloud.network sells priced products built on a single promise: direct physical connections to Russia's largest networks. Its own published footprint — the routing table, the RPKI state, the registry — tells a smaller story, and the…
Story
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.
Story
Two tiers of EDEKA: where the frozen registry ends and live routing begins
Two tiers of EDEKA: where the frozen registry ends and live routing begins 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
RIPE NCC October 2026 General Meeting: The Board Structure Vote and What It Says About Member Control
The RIPE NCC has published a draft agenda for its October 2026 General Meeting that goes beyond routine housekeeping: alongside the 2027 budget discussion, an Arbiter Panel election and a surplus-distribution vote, members will be asked to approve Articles of Association…
CASE FILE
Three Names on One Netblock: How Custody of Svea's Legacy Abuse Contact Split Across a Merger
When a Swedish bank merges, its internet number resources do not disappear — they inherit. The RIPE Database record for 193.105.138.0/24 is a rare case where you can read the aftermath directly in a public registry entity: three distinct legal parties, one dissolved predecessor…
Story
The Svea Abuse-Role Record: Validated Contactability, No Documented Processing
The abuse contact recorded and mirrored for Svea's legacy netblock 193.105.138.0/24 is a carrier-era inherited mailbox on the Verizon Business/UUNET lineage — registry-validated for technical deliverability but never documented to have received, answered, escalated or remediated…
Number Resource Society
The nomination funnel behind RIPE NCC's Executive Board election: what the May 2025 record actually shows
Every three years, the RIPE NCC membership nominates, supports and elects the people who sit on the body that governs the world's largest regional internet registry by membership count. The May 2025 election left a complete public record: a call for nominations under Article 9.1…
Story
The Ladder That Has Not Fired: What the Public Record Shows About Enforcement on the Svea Abuse-Contact Surface
When Svea Ekonomi AB merged into Svea Bank AB on 3 January 2022, the RIPE Database inherited a problem that no merger clause can settle by itself: the group's registered abuse-contact surface. Nearly four years later, that surface still carries the dissolved company's identity in…
Story
One Upstream, Frozen Paperwork: What AS51035's Stable Shape Says About ER-Telecom's Ufa Branch
The network that carries the name "Network Operation Center JSC ER-Telecom Holding Ufa branch" has not changed its declared routing policy since September 2018, its registry role entity since October 2019, or its announcement set since December 2019. Its entire external…
Number Resource Society
RIPE NCC's Excess-Contribution Redistribution: A Codified Remedy, Not a Gesture
When the RIPE NCC returned EUR 8,365,249 to its members in 2020, the money moved under a written procedure that predates the decision — and the October 2019 General Meeting vote that authorised it was split hard enough to reveal how contested the choice between reserve and…
Story
The abuse chain that validates its first link and stops there
Every year the RIPE NCC proves that tens of thousands of abuse-contact mailboxes work. Nothing it publishes measures whether a single third-party abuse report ended in verified remediation. This report traces that gap to the policy text that created the validation mandate, and…
Story
DFINFRA and AS210860: what changes after a registry record outlives its network
DFINFRA and AS210860: what changes after a registry record outlives its network 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…
Europe and Middle East Cloud Services
The Registry Says One Company, the Records Say Another: Inside AS210328's Identity Gap
The Registry Says One Company, the Records Say Another: Inside AS210328's Identity Gap intelligence summary explains the development, the public evidence available to readers, the organisations involved, the regional context, market exposure, and the infrastructure consequences…