Yandex Cloud remains disrupted after drone strike shuts Vladimir data centre
Yandex Cloud remained in limited operation on Monday, October 12, after a drone strike damaged the company’s data centre in Vladimir, Russia, and forced the site to suspend operations. The latest disruption followed damage to two other Yandex facilities earlier in the week, adding to difficulties for businesses and users dependent on the company’s infrastructure.
The BBC reported that a Ukrainian drone strike hit the Vladimir facility, east of Moscow, overnight into Sunday. Yandex said operations at the site had been completely suspended and no one had been injured. The company was working to restore connectivity, but some services remained unavailable.
Cloud services are operating unevenly
In its latest available Yandex Cloud status update, posted at 08:17 UTC on October 12, the operator said its platform was still working in a limited mode. Restoration work continued around the clock, while a higher volume of support requests could mean longer response times. It continued to recommend alternative platforms for hosting resources and providing redundancy.
That is not an all-clear. The update did not give a time for complete restoration. Yandex said its next status update would be published at 19:00 Moscow time, equivalent to 16:00 UTC; that scheduled notice should not be mistaken for a promise that services would recover by then.
The operator’s Sunday updates showed a mixed picture rather than a uniform shutdown. In an 08:14 UTC snapshot, Yandex said its console and application programming interfaces were available, while computing resources were only partly available. Object storage supported reads and writes but could be slower. Kubernetes services were available with possible issues in individual clusters, and difficulties persisted with its managed Apache Kafka service. Yandex also said increases in quotas for additional cloud resources remained suspended.
Those component-level updates describe conditions at their stated times. They do not establish that every customer application using those components had recovered, or that all workloads faced the same level of disruption.
Effects extend beyond cloud customers
The Record’s October 12 reporting described disruption extending to payments, deliveries and other online services, alongside Yandex Cloud. It reported problems involving email, taxi bookings, food orders and some connected-home functions, as well as third-party businesses using Yandex infrastructure. The full extent of the interruption remained unclear, and Yandex had not disclosed how many cloud customers were affected.
The Vladimir incident came after strikes on Yandex’s Sasovo facility in the Ryazan region on October 8 and its Kaluga facility on October 9. Those earlier disruptions form the background to the latest outage; they do not mean every Yandex product is completely offline or that users across all regions are experiencing identical problems.
Yandex’s Sunday notice described the remaining resource configuration as unstable and urged customers to consider other disaster-recovery plans. For dependent businesses, the immediate issue is whether their own services can operate, not simply whether a cloud management console is accessible. A restored dashboard and a fully functioning customer service are different recovery milestones.
Restoration remains in progress
As of the Monday morning operator update, the appropriate status was limited operation with restoration continuing, not fully restored. The reported cause was physical damage to infrastructure following a drone strike; the sources reviewed did not describe this event as a ransomware or software-intrusion incident.
Follow current service signals through Status Is Down’s real-time dashboard and browse the News archive for other verified disruptions. Website owners can explore Status Is Down plans and create an account to follow the services their operations depend on.
Image credit: ID 76688877 © Ralwel | Dreamstime.com