Yandex said on October 11, 2026, that a drone attack had damaged its infrastructure and forced a full shutdown of its data center in Russia's Vladimir region, Reuters reports. It is the third Yandex data center knocked out in four days. Some Yandex services are unavailable. Early reports say more than 80 cloud services and components were affected, including the company's AI model API. For anyone who runs software in the cloud, it is a rare case of one provider losing data centers to physical attacks, one after another.
What Yandex said
Yandex said its infrastructure had been damaged in a drone attack on Sunday, according to Reuters, in a report published by The Moscow Times. Its Vladimir-region data center was completely shut down, and some services are unavailable to users. No one was injured, the report says.
Yandex is one of Russia's largest technology companies, sometimes called "Russia's Google," Reuters notes. The agency adds that Yandex is heavily involved in Russia's AI development.
Reuters does not say who carried out the Vladimir attack. The Ukrainian outlet UNN links the outage to an attack by Ukrainian forces on a "third Yandex data center." UNN presents that link as reported, not confirmed.
Which services went down
Yandex Cloud is the company's cloud computing business. It rents servers, storage, databases and AI models to other companies. UNN, citing preliminary reports, says more than 80 of its services and infrastructure components were affected. It names these, among others:
| Group | Services named by UNN |
|---|---|
| Cloud computing | Compute Cloud, Virtual Private Cloud, Managed Service for Kubernetes, Cloud Functions, load balancing |
| Storage and databases | Object Storage, PostgreSQL, ClickHouse, MySQL, YDB, OpenSearch |
| AI and analytics | YandexGPT API, SpeechKit, Vision OCR, DataLens, Yandex AI Studio |
| Work tools | Tracker, Wiki, Forms, Cloud Desktop |
| Consumer apps | Yandex Music, Yandex Home, Telemost |
UNN says the extent of the damage, the length of the outage and its link to the attack still need independent confirmation.
Three data centers in four days
| Date | Site | What was reported |
|---|---|---|
| October 8 | Sasovo, Ryazan region | A fire after the strike; Yandex fully suspended the site |
| October 9 | Kaluga region | Several data center modules completely disabled |
| October 11 | Vladimir region | The data center fully shut down |
The first strike hit Yandex's data center in the Ryazan region, southeast of Moscow, according to Reuters, as published by NBC News on October 8. The fire forced Yandex to fully suspend the site. Yandex Cloud reported power supply problems in one data center "zone" and told customers to use other zones. The Moscow Times says the site houses two of the three supercomputers Yandex uses to develop its AI model. Reuters said there had been no previous confirmed major Ukrainian drone attack on a Russian data center.
The next day, Yandex told the news agency Interfax that its Kaluga data center had been hit. "Several data center modules are completely disabled," the company said. "Our teams are working day and night to do everything possible to keep services running," it added, as quoted by The Moscow Times.
Why the attacks are happening
Ukrainian President Volodymyr Zelensky told reporters on October 8 that the attacks on Yandex were retaliation, The Moscow Times reports. He pointed to Russian missile strikes on Ukrainian server facilities in Kyiv. "We always respond symmetrically," he said.
The Moscow Times says Russia has run a strike campaign against Ukrainian data centers and telecom networks over the past month. Reuters also describes the first Yandex strike as following a wave of Russian attacks on Ukrainian data centers.
What this means for developers
The outages show that a cloud zone can vanish for reasons no backup plan inside one building can cover. A few lessons apply to any team, on any cloud:
- Spread across zones and regions. After the first strike, Yandex Cloud told customers to use other zones. Workloads already running in more than one zone could keep going. When three sites can be hit in four days, a second region matters too.
- Keep a second AI provider ready. The YandexGPT API was among the services reported down. An app that calls a single model provider stops when that provider stops. Wire in a fallback model and test it.
- Back up outside your provider. Copy critical data to a different provider or location, and practice restoring it.
- Add physical risk to the threat model. Data centers can now be targets, not just victims of bad weather or power cuts. Teams choosing a region should weigh that risk alongside price and speed.
Two things are worth watching next. One is how quickly Yandex restores the Vladimir site and whether it publishes a report on the outage. The other is whether data center operators near conflict areas change how they protect their sites.
This article was first published on Tech AI Wire.
Also available in
Deutsch · 日本語 · Français · Español · Português
Sources
- Russia's Yandex Says Data Center in Vladimir Shut Down After Drone Attack - The Moscow Times
- Russia reports a major Yandex Cloud outage following an attack on a Yandex data center - UNN
- Ukraine Drones Hit Second Yandex Data Center in Two Days - The Moscow Times
- Drones hit Yandex data center in first major attack on Russian data hub - NBC News
Top comments (1)
Sự cố này nhắc nhở rõ rệt về rủi ro vật lý mà kiến trúc phân tán thường bỏ qua: data center vẫn là điểm lỗi đơn lẻ (SPOF) nếu không có multi-region active-active thực sự. 80+ dịch vụ sập cùng lúc cho thấy phụ thuộc chặt chẽ vào một site — điều mà các pattern như cell-based architecture hay blast-radius isolation nhằm giải quyết.
Bài học thực tế: DR plan cần test thường xuyên, không chỉ trên giấy. Failover tự động giữa các region, data replication sync/async tùy SLA, và capacity headroom tại site backup mới giữ được uptime khi site chính bị down vật lý. Các team đang chạy single-region hoặc chỉ có warm standby nên xem đây là cảnh báo để ưu tiên investment vào multi-region resilience PS: the tool I meant is on labagent .tech