Drone strike shuts Yandex Vladimir data hub

On Oct. 11, 2026, a Ukrainian drone attack struck a Yandex data centre in the city of Vladimir, east of Moscow. The strike forced the facility to be shut down, with Yandex confirming that operations at the site had been completely suspended. The company reported that there were no injuries at the Vladimir location following the attack.

Yandex described the situation at the Vladimir hub as severe enough to halt all activity. The facility’s closure removed a significant part of the company’s computing capacity from service while teams began assessing the extent of the physical and technical damage.

Following the Vladimir strike, Yandex warned that its remaining resource configuration was unstable. Customers were advised to activate their disaster‑recovery plans as a precaution while the company evaluated the situation. The use of contingency arrangements was presented as necessary to maintain continuity of operations for those relying on Yandex infrastructure.

The instability affected a range of Yandex services. Users in dozens of Russian cities, as well as in neighbouring countries, experienced outages and could not access some services. The disruptions highlighted the dependence of both individual users and corporate clients on the company’s distributed data‑centre network.

Among the services affected were key everyday applications such as taxi ordering. Many users were unable to book rides as normal while systems were disrupted. The interruption underscored how data‑centre outages can quickly translate into visible problems for transport and logistics services.

Some banking functions that rely on Yandex infrastructure were also disrupted. Customers in affected areas faced difficulties accessing these services until systems could be stabilised or rerouted. These issues illustrated the role Yandex plays as a backbone provider for various financial and transactional processes.

The Vladimir incident was reported as the third attack on Yandex data infrastructure in roughly a week. Earlier drone strikes had targeted Yandex facilities in the Ryazan and Kaluga regions. There had also been a previous hit on the company’s Sasovo hub.

With multiple sites affected over a short period, Yandex said its teams were operating in emergency mode. Engineers were working to stabilise services, reconfigure remaining capacity, and explore options to restore systems. The sequence of strikes demonstrated the vulnerability of distributed data‑centre assets during sustained attacks.

In response to the Vladimir shutdown and prior incidents, Yandex focused on damage assessment and service restoration. The company signalled that recovery efforts would involve both technical repairs at the affected data centres and reallocation of workloads across surviving infrastructure.

While no timeline for full restoration was provided, the guidance to activate disaster‑recovery plans indicated that disruptions could persist. The situation placed a premium on redundancy and failover capabilities for Yandex’s customers as the company continued to manage operations under heightened risk.