What happened

Ukrainian drones struck three Yandex data centres in three separate attacks between 8 and 11 October 2026, according to Reuters and Yandex statements. Sasovo, in the Ryazan region, was hit overnight into 8 October and shut down completely. Kaluga was struck overnight into 9 October; Yandex said “several data center modules have been completely disabled” and that no employees were injured, while the regional governor, Vladislav Shapsha, reported nine people hurt. Vladimir, roughly 170 to 180 kilometres east of Moscow, was hit overnight on 10 to 11 October; Yandex said the facility shut down completely after infrastructure was damaged. Kyiv Post reported the Vladimir site as a 40 to 50 megawatt facility.

Meduza reported users unable to reach Yandex services and sites including Avito, Ivi, Megafon, Russian Railways and T-Bank. Kyiv Post counted more than 80 disrupted services, among them object storage, Managed Kubernetes, PostgreSQL and the YandexGPT API. The Moscow Times reported knock-on outages in Kazakhstan, Kyrgyzstan, Uzbekistan and Yerevan.

Site counts differ. Meduza and The Moscow Times say three of Yandex’s six data centres were damaged; Ars Technica’s earlier 9 October coverage said two of five.

What’s confirmed and what isn’t

The strikes, their locations and the pattern of disruption are documented by Reuters, independent Russian media and commercial satellite imagery. Planet Labs imagery cited by Meduza shows the data-centre wing at Sasovo burned out completely. Other damage detail rests mainly on Yandex and Russian state-adjacent reporting.

The AI detail is thinner than some coverage suggests. Ars Technica reported that Sasovo housed two of Yandex’s three supercomputers used to train the YandexGPT model; no other publication has independently confirmed it. Satellite imagery confirms the building damage, not what equipment it destroyed, and no outlet has published an independent measurement of training capacity lost. Yandex has not confirmed any effect on YandexGPT training, and the YandexGPT API appearing in outage lists is an availability problem, not evidence about training hardware.

On the widely shared claim that the strikes silenced Russian bot networks: LetsData co-founder Ksenia Iliuk told Euromaidan Press that none of the Russia-linked networks it tracks stopped posting. Euromaidan Press also reported, citing Cybernews, that the Cloudflare chart cited with the claim measured automated web requests from Yandex’s network, including search crawlers, rather than social-media posts.

President Zelenskyy described the strikes as “our symmetrical response” in a 9 October post on X that was chiefly about Ukrainian strikes on the Omsk and Ukhta oil refineries. Russia has struck Ukrainian data centres and telecoms since late September, damaging or destroying facilities belonging to at least eight companies, according to Meduza.

Why commercial compute is a target

Nothing in the reporting describes these as AI-only sites. Yandex’s data centres are mixed-use commercial compute, hosting search, maps, taxi and food delivery, payments and cloud services alongside AI products. Yandex Cloud is a general-purpose public cloud whose disrupted services included databases and object storage. The AI framing comes from the Sasovo supercomputer detail rather than the sites’ overall role.

Striking commercial compute interrupts everyday services, and the effects travel across borders through cloud customers and dependent apps. Russia’s strikes on Ukrainian data centres and telecoms since 23 September temporarily cut internet access to about 100,000 households in the Kyiv region, according to Ars Technica.

Construction matters. Meduza’s explainer notes that modern data-centre buildings with metal frames are vulnerable to drones carrying relatively small warheads, while Soviet-era reinforced-concrete facilities are harder targets. HAKA Moscow, which built one of the Vladimir sites in 2016 and 2017, said its priorities were speed, expandability and reduced active cooling, without reinforced-concrete frame slabs.

What operators do about it

Commercial data centres are normally built for redundancy: multiple availability zones, geographic separation and failover between regions. AWS’s account of the Middle East strikes is the clearest public statement of where that design stops: “The damage to our infrastructure spanned multiple Availability Zones and exceeded what our regional and multi-AZ services are designed to withstand.”

Responses to the Yandex strikes follow similar lines. Russia’s digital development ministry helped Yandex move core systems to external backup servers; Yandex says it has run distributed infrastructure and backup capacity at independent sites for years; and Rostelecom’s Valery Yermakov has called for geographically isolated, decentralised backup data centres.

Protection costs money, and the Kremlin is pushing facility owners to pay for it. A decree lets the state temporarily take over enterprises that fail to provide their own drone defences, and companies can rent air-defence systems from the defence ministry. Ukraine has dispersed production and moved some data centres abroad, though a former deputy minister warned that “you cannot move everything underground”.

What it means if you rent compute

  • Multi-zone and multi-region design reduces risk without eliminating it: in the AWS case the provider said the damage exceeded what its design was meant to absorb, and recovery work was pushed to customers, who were told to migrate workloads to other regions and restore from remote backups.
  • Provider relief has come as billing suspensions and credits: AWS suspended billing in the affected regions and issued customer credits; Yandex waived Cloud, 360 and Pay fees for 8 to 31 October.
  • Recovery takes time. A source told Kommersant that replacement equipment for the damaged Yandex sites could take up to six months.
  • The evidence has limits. No independent measurement of AI-training capacity loss exists after the Yandex strikes, and no provider contract or insurance term covering war damage was examined.

The earlier precedent: Amazon’s sites in the Middle East

Iranian drone strikes hit AWS sites in Bahrain and the UAE on 1 March 2026, followed by a further strike on Bahrain on 1 April and an IRGC missile strike on a remaining Bahrain structure on 24 July.

In a dashboard update on 15 September, first reported by Reuters and summarised by Ars Technica, AWS said it was unable to restore access to resources and data in one of three UAE availability zones and across all three availability zones in Bahrain, a permanent loss of customer data. It suspended customer billing and directed customers to migrate workloads and restore from remote backups.

The procurement response is visible. Reuters reported on 11 September that the UAE is revising a planned 5-gigawatt AI campus in Abu Dhabi, originally a single 10-square-mile site, into a network of data centres spread across the country. Options under discussion include air-defence systems, interceptors, jamming, blast-resistant concrete, extra backup power, and underground construction. The $30bn Stargate UAE first phase remains on track.