Yandex says a drone attack damaged its data center in Vladimir early on Sunday, 11 October, and that the site’s operation has been completely stopped, according to the Yandex Cloud status page. The update, posted at 03:08 GMT, said Yandex Cloud considered the remaining resource configuration unstable and the platform was in emergency mode, and it recommended that customers activate alternative disaster-recovery plans.
It is the third Yandex data center hit in four days, after Sasovo on 8 October and Kaluga on 9 October, Reuters reported via The Moscow Times. By 15:01 GMT, Yandex Cloud said the platform was still running in a limited mode and repeated its main recommendation: consider alternative sites to host and back up resources.
The status page first flagged a problem at 01:11 GMT, saying some Yandex Cloud zones were unavailable. Yandex Cloud also said on its official Telegram channel that “There are power interruptions in the ru-central1-a availability zone,” according to the Kyiv Independent, which reports that zone as located at the Vladimir data center.
At 03:08 GMT, Yandex Cloud confirmed the attack. In Al Jazeera’s translation of the alert, Yandex said “Operations at the data centre have been completely suspended” and “The remaining resource configuration is considered unstable.” The company said no one was injured and that emergency services were on site.
Later updates gave a service-by-service status. At 08:14 GMT, Yandex Cloud listed its console and API as available, Compute as partially available, and Managed Databases as available with difficulties in its managed Apache Kafka service. It listed S3 storage as available for reading and writing with possible slowdowns, and Yandex Monium as unavailable.
The same update said Yandex Cloud had temporarily suspended the issuance of quotas for additional cloud resources. It said support channels were partly restored, with significant delays in responses still possible.
Status of Yandex Cloud’s 10 AI Studio services at 05:14 GMT on 11 October 2026, as posted on Yandex Cloud’s alerts channel after the Vladimir data center stopped: the Retrieval API, OCR API, AliceAI Pro and SpeechSense were listed as unavailable; the Responses and Chat Completions APIs, SpeechKit TTS and Image Generation as available; SpeechKit STT and the Search API as partly available.
Business Pill · EVERY DOOR COUNTS
A one-minute explainer of an attack surface: every point where a system can be reached is a point that has to be protected. It teaches the general idea only and says nothing about any company in this story.
The key insight: As we read it, the notable detail is Yandex Cloud’s own advice to customers: after the Vladimir site stopped, its status page recommended alternative disaster-recovery plans and, later, alternative sites to host and back up resources, while it suspended quotas for additional resources.
What Was Affected
Yandex Cloud’s alerts channel gave a separate status for its AI Studio services at 05:14 GMT. Of the 10 services it listed, four were marked available, two partly available and four unavailable.
The Responses and Chat Completions APIs were listed as available, including the yandexgpt-5.1 and yandexgpt-5 models alongside DeepSeek and Qwen models. The Retrieval API, OCR API, AliceAI Pro and SpeechSense were listed as unavailable.
A second post at 05:15 GMT listed 15 security services: eight available, two available with limited configuration changes, and five unavailable, including Audit Trails, Yandex SIEM and Cloud Desktop.
Kyiv Post reports that more than 80 services and components were disrupted. Its list includes the Alice voice assistant, Yandex Music, Telemost and Smart Home, and developer services such as Compute Cloud, Object Storage, Managed Kubernetes, the YandexGPT API, SpeechKit and Vision OCR.
Kyiv Post also reports user complaints of failures in banking apps, ride-hailing and the retail chains Magnit and Fix Price. The Kyiv Independent, citing the Russian outlet Ostorozhno Novosti, reports that Yandex Go users in Russia could not order taxis, with similar disruptions reported in Serbia, Kazakhstan, Belarus and Armenia.
Yandex Cloud services by status in the company’s alerts of 11 October 2026, 05:14-05:15 GMT: of 10 AI Studio services, 4 available, 2 partly available and 4 unavailable; of 15 security services, 8 available, 2 available with limited configuration changes and 5 unavailable.
Three Sites in Four Days
Reuters, via The Moscow Times, reports that the Sasovo hub, shut on 8 October, houses two of the three supercomputers used to develop the company’s AI model. It reports that the Kaluga site was partly put out of action on 9 October.
In a statement on 9 October about the first two strikes, Yandex wrote: “Data centers are the iron heart of Yandex.” It said hundreds of thousands of companies use its technology, and that “it is very difficult to say when the equipment at the data centers will be back up and running.”
On 10 October, Yandex updated its user agreement to include drone and missile attacks among circumstances of force majeure, the Kyiv Independent reports.
Kyiv Post reports that Yandex removed the locations of its data centers in four regions from its maps, and that its shares fell about 4% on the Moscow Exchange earlier in the week.
The Site and the Night
Kyiv Post, citing the ASTRA and Crimean Wind Telegram channels, describes the Vladimir site as a 40-to-50-megawatt facility in the city’s Energetik district, designed to house up to 2,880 server racks. These figures come from the Telegram channels and Kyiv Post, not from the Yandex statements quoted here.
Vladimir region governor Aleksandr Avdeev said drone strikes damaged local substations, and that heat, water and about 80% of electricity had been restored in affected areas by Sunday morning, Kyiv Post reports. Russia’s Defence Ministry claimed 479 drones were intercepted overnight across 16 regions.
After the Sasovo strike, Ukrainian President Volodymyr Zelenskyy said, as quoted by Al Jazeera, “We always respond in mirror-like fashion”, referring to Russian strikes on Ukrainian data centers.
The Structural Read
The status updates show which layers held. In Yandex’s listings the console, API and identity services stayed available, while compute and some databases ran partly, and several AI and security tools were listed as unavailable.
The accounts differ on the AI layer. Kyiv Post lists the YandexGPT API among disrupted services; Yandex’s 05:14 GMT post lists its Responses API, including yandexgpt-5.1, as available.
As we read it, the 10 October change to Yandex’s user agreement, adding drone and missile attacks to force majeure, brings the attacks into its contract terms as well as its operations.
Yandex statement, 9 October 2026
“Data centers are the iron heart of Yandex. Their operation is critical for services that have become part of peopleโs everyday lives.”
Three Implications
CLOUD CUSTOMERS Yandex Cloud told customers to activate alternative disaster-recovery plans and to consider alternative sites to host and back up resources.
CAPACITY Yandex Cloud says it temporarily suspended the issuance of quotas for additional cloud resources.
FACTS STILL THIN Yandex’s updates on 11 October gave no restart date; the capacity figures come from Telegram channels via Kyiv Post.
The framework’s starting point: “The digital economy rests on a physical foundation that most people in that economy never see.”
As we read it, the Vladimir status page makes that foundation visible: according to Yandex Cloud, one site stopping put its platform into emergency mode.
What Is Not Established
The Yandex Cloud updates we read on 11 October give no restart date for the Vladimir site; the last one said the next update would come on 12 October at 11:00 Moscow time.
The capacity, rack and service-count figures come from Telegram channels and Kyiv Post. The Kyiv Independent says it could not independently verify images of a fire near the facility or the extent of the damage.
The AI Studio and security lists are snapshots from early on 11 October. Yandex Cloud’s later updates described the overall status as unchanged, then as limited, without repeating the lists.
Business Engineer Framework
AI’s Geopolitical Chokepoint
A Business Engineer framework on the physical foundations, and the geopolitical leverage, under the digital economy.
Yandex’s own status page describes a cloudplatform running in emergency, then limited, mode after losing its Vladimir data center, with customers told to look to alternative sites. It is the third Yandex site taken offline or damaged in four days.
A note on sourcing. On 11 October 2026 we read in full the Yandex Cloud status page for incident 2136 (in Russian; paraphrases here are our translation), two posts on Yandex Cloud’s official alerts Telegram channel, and Yandex’s 9 October statement on its data centers, together with reports by Reuters (via The Moscow Times), Al Jazeera, Kyiv Post and the Kyiv Independent. Quotations of Yandex’s alert are Al Jazeera’s translation.
Capacity, rack and service-count figures are Kyiv Post’s, citing Telegram channels, and claims about the night come from the parties named. Nothing here is a forecast or investment advice.
Gennaro Cuofano is a CRO and tech executive who has worked in AI since late 2015, starting with bringing NLP, natural-language generation, voice and chatbot products to the marketing industry. His background is in law and finance: he holds a Master's degree in Law and an International MBA with an emphasis on corporate finance (LUISS Business School and the University of San Diego, 2012), and worked as a financial analyst at a real-estate investment firm in San Diego and as an assistant controller. His work focuses on business model strategy, business engineering and, more broadly, structural analysis: how companies make money, read from their own filings. He created FourWeekMBA and leads research there and at The Business Engineer, his newsletter on AI and business strategy, with over 95,000 subscribers and more than 1,000 published analyses. His writing has also appeared on Entrepreneur, HackerNoon and Search Engine People. Find him on LinkedIn and Substack. See how we source.
Scroll to Top
Discover more from FourWeekMBA
Subscribe now to keep reading and get access to the full archive.
