Yandex said Sunday, Oct. 11, that a drone attack damaged infrastructure at its Vladimir data center and forced the site to stop operating. It was the third reported Yandex data center strike in four days, and the company warned that its remaining cloud resources were unstable. The reports document disruption to the facility and some services, but do not establish damage to AI systems.
What is known about the Vladimir strike?
Yandex Cloud’s incident notice says the attack damaged infrastructure at the data center and completely suspended operations there. The company also reported no casualties and said it was working to restore services.
Alexander Avdeev, the Vladimir region’s governor, reported an attack on infrastructure near the city and a fire. His account, reported by Kommersant, also described temporary power disruptions through two substations, affecting about 5,000 residents.
Together, the accounts support that a drone-related incident and fire occurred, but they do not provide an independent technical assessment of damage at the site. Neither establishes whether the data center was the intended target or what specific equipment was hit.
Who has attributed the attack to Ukraine?
The Associated Press described the incident as a Ukrainian drone attack. DatacenterDynamics also reported Ukrainian strikes, citing the BBC. Those accounts attribute responsibility; Yandex’s notice and Avdeev’s reported statements identify a drone attack but do not name Ukraine as the actor.
The available reporting does not independently establish who launched the drone. The distinction matters: confirmation of damage and a drone attack is not, by itself, confirmation of responsibility or intent.
What happened to Yandex services and local utilities?
Kommersant reported that outages on Sunday affected Yandex services as well as services that rely on its infrastructure. Yandex said later that day that services were gradually returning. DatacenterDynamics reported on Monday that some services remained unavailable.
Yandex Cloud said the configuration of its remaining resources was unstable and placed the platform in emergency mode. It advised customers to use alternative recovery plans and warned that communications with technical support might be unreliable. The company’s notice describes individual services and recovery work; it does not say that every Yandex product or customer workload went offline.
Avdeev later reported that local electricity supply had been restored to 80%, while heat and water service had been fully restored. Those figures concern the reported local utility disruption, not the data center’s recovery.
Free newsletter
Get the morning briefing
Start each day with the AI stories that matter and why — a short, free email from our newsroom.
What does the strike mean for AI computing?
The Vladimir site has a reported connection to AI infrastructure: The Insider reported that Yandex’s Galushkin supercomputer, used for machine-learning tasks, was located there. Yandex has not confirmed whether that system or any other specific computing equipment was damaged or made unavailable.
The site shutdown and cloud-service disruption show an operational impact on physical computing infrastructure. But the reports do not establish that AI training or inference workloads were affected, or that AI services were disrupted. The incident was reported as an attack on data-center infrastructure, not as an operation specifically targeting AI.
How does this fit with the earlier Yandex data center strikes?
Yandex had already reported damage at two other facilities. In a statement on Oct. 9, the company said the Sasovo data center in the Ryazan region had been completely shut down after an attack on Oct. 8, and that part of the infrastructure at its Kaluga data center was out of service after an attack on Oct. 9. The earlier report on the Sasovo and Kaluga sites noted that Yandex had not identified the affected systems or services at Kaluga.
DatacenterDynamics described Vladimir as the third of Yandex’s five large data centers to be hit. The company’s account of the earlier damage did not identify specific systems at those sites, and the available reports still do not say what equipment was damaged in Vladimir.
Yandex’s notice said restoration work was under way but gave no timetable. As of Monday, DatacenterDynamics reported that some services were still unavailable; the condition of the Galushkin supercomputer and the extent of damage inside the Vladimir facility remain unconfirmed.
Comments
Comments are written by readers. They are not reporting or opinion from AI News.
Share your view on this story. Criticise ideas and public records, not other readers.
Comments appear once a moderator approves them.
Community guidelines
More in our terms and privacy policy.
Comments close on October 19, 2026.
No comments yet. Start the conversation.