> ## Content Index
> Fetch the complete content index at: https://espresso.cafecito.tech/llms.txt
> Use this file to discover other available public pages before exploring further.

# Yandex Cloud Runs Degraded After Drone Strikes
- URL: https://espresso.cafecito.tech/yandex-data-centre-drone-strikes-degraded-cloud/
- Published: 2026-10-14T13:31:04.000Z
- Updated: 2026-10-14T13:31:03.000Z
- Description: Three Yandex data centres were struck between Oct. 8 and Oct. 11, degrading cloud and consumer services across several countries. Recovery is expected to hinge on procuring replacement hardware, a process one analyst and Yandex Qazaqstan each put at roughly six months.
- Author: Barista @ Cafecito
- Tags: Cybersecurity, Technology, Cybersecurity Incident, Threat Intelligence, Security Vulnerability

Yandex's cloud has been running degraded since drone strikes hit its data centres in Sasovo (Ryazan Region), Kaluga and Vladimir between Oct. 8 and Oct. 11\. The first blow landed Oct. 8 at Sasovo, where a fire broke out. The second strike, reported Oct. 9, hit Kaluga. A third, on Sunday morning Oct. 11, shut down the Vladimir site. Ukrainian forces flew the drones, according to reporting attributed to Reuters, alongside Ryazan governor Pavel Malkov's accounts of the Sasovo damage and Yandex Qazaqstan's confirmation of technical issues.

The blast radius shows in the product list: Yandex Cloud, Yandex.Go, Yandex.Eda, Yandex.Pay, Yandex Music and the Telemost video service all took hits, and the Alice voice assistant was reported offline. Search degraded for regional users, and the taxi-ordering API broke transport logistics integrations. Customers in Kazakhstan, Belarus, Armenia, Serbia, Uzbekistan and Kyrgyzstan were among those affected. Yandex stock dropped roughly 4% on the Moscow Exchange after the second strike, then partly recovered.

One reported casualty stands out: Yandex's supercomputers — named in Russian reporting as Chernovenkis, Lyapunov and Galushkin — were described as knocked completely offline.

### No Patch for Arriving From Above

There's no failed validation step to fix here, no zero-day to roll back. The access prerequisite is airspace, not credentials. Kinetic drones with explosive fragmentation meet a building; physical hardening — access control, generator redundancy, fire suppression — was designed around the wrong threat model. The trust boundary that broke was the assumption that a hardened facility is hard to reach.

That also means the usual incident-response reflexes don't apply. You can't segment a network against a warhead. A figure cited in Russian reporting puts the hit to core compute at roughly 75%, though that's a reported estimate, not a measurement Yandex has published.

### The Long Pole Is Spare Parts

Sergei Kudryashov of Strategy Partners told Russian media on Oct. 12 that supplying replacement equipment could take up to six months, with global shortage and AI-accelerator demand pushing hardware and cloud prices higher. Yandex Qazaqstan pointed to the same timeline, saying full recovery of replaced equipment is expected within roughly six months. That's what outlasts the news cycle: the strikes lasted days, but the constraint on restoring capacity is procurement.

That six-month figure is a forecast, not a scheduled date. Earlier reporting said service is unlikely to be restored before early November, with partial degradation continuing.

### What's Confirmed, What Isn't

Confirmed: three sites struck across Oct. 8–11, at least two knocked offline, a fire at Sasovo, service interruptions across cloud and consumer apps, a stock dip, and the roughly 75% core-compute loss as reported. Yandex reportedly said work was redistributed among surviving capacity and that no employees were injured, though the company hasn't published the restoration timeline.

Not confirmed: cumulative financial loss, the exact capacity still available, and per-customer restoration timelines. Claims that the strikes represent a deliberate campaign to target communications networks as primary defense infrastructure remain an inference drawn from the strike pattern, not something the dates alone establish.

There's a structural detail worth separating from the outage itself. Kazakh rules require local data storage, which Yandex meets, but compute sits outside the country's borders — so local compliance didn't buy local redundancy. A Yandex Cloud region in Karaganda, launched in 2024, exists but was described as insufficient to absorb the load.

The unresolved question is the one outage estimates can't answer: how much of Yandex's total capacity those three sites carried, and whether the survivors can hold while repairs stretch into next year.

[![Beans](https://beans.cafecito.tech/favicon.ico)Explore more coverage on BeansSearch this story across publishers→](https://beans.cafecito.tech/?q=Yandex%20Cloud%20Runs%20Degraded%20After%20Drone%20Strikes&utm%5Fsource=espresso.cafecito.tech&utm%5Fmedium=referral&utm%5Fcampaign=cafecito&utm%5Fcontent=yandex-data-centre-drone-strikes-degraded-cloud)