The news
A Ukrainian drone strike on Thursday, October 8, 2026, set fire to a Yandex data center in Sasovo, in Russia's Ryazan region, according to The Moscow Times, which cited the regional governor and satellite fire data. Russian state media reported the strike, according to The Record, while Ukraine's military made no public comment.
Yandex said operations at the facility were fully suspended while emergency teams worked to contain the damage, The Moscow Times reported. The Record reported that Yandex acknowledged a power outage on Telegram but did not publicly link the disruption to a drone strike. The site is one of Yandex's five data centers and is housed in a former machine-tool manufacturing plant, The Record reported.
The outage hit Yandex's cloud business. Connectivity fell to about 70% of normal levels, and Yandex Cloud computing, storage and database services were disrupted, according to The Record. Yandex told customers that the ability to create new cloud resources might be limited and moved workloads to other facilities. Yandex Disk and Yandex Documents also had problems, and several Russian websites that depend on Yandex went offline, including a regional newspaper edition.
Downdetector logged more than 1,300 user reports about Yandex Cloud, Documents and Tables, while core search and taxi services kept running, The Moscow Times reported. Ryazan governor Pavel Malkov said the roof of a company building in the Sasovo district had caught fire, without at first naming the facility. No casualties were reported.
Yandex shares fell more than 3.4% in morning trading on the Moscow Exchange on October 8, according to The Moscow Times.
The numbers
- Yandex data centers (total)
- 5
- Connectivity after outage
- About 70% of normal
- Downdetector user reports
- 1,300+
- Yandex share move, Oct. 8 morning
- Down more than 3.4%
- Ukrainian data centers damaged in late September
- 6
Why CEOs should care
For CIOs and CISOs, the lesson is that physical attack now belongs in the data center threat model, not only power loss, floods and fire. The Moscow Times described this as the first confirmed Ukrainian strike on Russian data infrastructure since the 2022 invasion, and it came weeks after Russian strikes damaged six Ukrainian data centers, The Record reported. Ask your cloud and colocation providers how they assess geopolitical and physical risk by site, and whether your workloads can fail over to a region in a different country.
Yandex's response is a useful benchmark. It shifted workloads to other facilities but warned customers that creating new cloud resources could be limited, according to The Record. That is the failure mode to plan for: surviving services keep running, but capacity to scale or recover is constrained across the provider. Test whether your disaster recovery plan assumes spare capacity that may not exist during a regional crisis.
For boards and risk committees, insurers may revisit how they price war exclusions and business interruption cover for digital infrastructure. Review policy wording now, especially for operations or suppliers in or near conflict zones.
The bigger picture
Russia intensified attacks on Ukrainian digital infrastructure in September, and a September 23 strike left more than 100,000 households in Kyiv without fixed-line internet, The Record reported. The reported strike on Sasovo suggests both sides now treat data centers as legitimate targets because they carry government, commercial and military workloads alike.
As AI and cloud capacity become strategic assets, the concentration of compute in a few large campuses creates single points of failure that adversaries can see from the air.
What’s next
Watch for Yandex's statement on when Sasovo will return to service and how much capacity was lost, any official comment from Ukraine, and whether further strikes target data centers on either side. Cloud providers' customer guidance on regional risk will show how seriously the industry takes the shift.
What “Fact-checked” means
Fact-checking means testing a story’s facts against the evidence before it is published. This story went through at least two separate checks before this version was published.
- What we checked
- Its names, figures, dates, job titles, quotes and who said what were checked against the story’s sources, including its main source where it could be opened. The headline was checked for accuracy and overstatement.
- How
- A first check reviewed the whole story. If it passed, a second, skeptical check went back to the sources to look for mistakes in the most important facts. If a check flagged the story, it was edited to fix the problems found, and a separate re-check then reviewed the whole story again.
- Who
- The checks are made by our newsroom, as steps kept separate from the writing, under rules set by our editor, Hussein Mukhtar. A story the checks still flag is held for the editor, who decides whether it is fixed, published or dropped.
- If something is wrong
- “Fact-checked” does not mean error-free. If a material error is found after publication, we correct the story and add a note saying what changed. Report an error
