Rapid News Brief — Yandex Cloud said Oct. 11, 2026, that its platform remained in a restricted operating mode after damage shut down its data center in Vladimir, Russia. For customers, the immediate consequence is an ongoing recovery process, with the provider recommending alternative locations for placing and backing up resources.
The latest update does not declare recovery complete
In an update posted at 15:01 UTC Sunday, Yandex Cloud said specialists were restoring services and support staff were handling requests around the clock. The incident remained open. The company scheduled its next update for Oct. 12 at 11 a.m. Moscow time, not a promised restoration deadline.
Earlier Sunday, the provider said additional cloud-resource quotas had been suspended and warned of significant support-response delays. Those limits matter for customers considering whether they can add capacity during the disruption.
Damage and its cause are company-reported
Yandex Cloud attributed the Vladimir damage to a drone attack and said the data center had stopped operating completely. It reported no injuries. This brief reports the provider’s account; NextNow has not independently verified the attack or determined responsibility.
The company’s Oct. 9 account had already described damage at its Sasovo and Kaluga facilities. At that time, it said assessing the infrastructure was continuing and that equipment-restoration timing was difficult to specify. Those earlier incidents are context, not proof that every service or customer has experienced the same interruption.
Customers need workload-specific checks
The operational distinction is between a platform update and evidence that a particular application has recovered. A provider’s report of continuing restoration does not establish that a customer’s reads, writes, backups or dependent services are functioning normally.
That is NextNow’s interpretation of the status notice, not a claim of data loss. Organizations evaluating their next step should check their own workloads and recovery arrangements against the provider’s current notices. The published update supplies neither a complete customer-impact count nor a basis for assuming that a migration or restart will resolve every problem.