A reported Ukrainian drone strike on Yandex’s data center in Sasovo, Russia’s Ryazan region, caused a fire and forced the facility offline, disrupting Yandex Cloud and dependent websites, corporate systems, transportation services and media outlets. Yandex confirmed a power outage without publicly attributing it to an attack, while NetBlocks observed network connectivity falling to around 70% of normal levels. Yandex moved workloads to other facilities, but restrictions on creating new cloud resources remained.
The facility houses two Nvidia A100-based supercomputers used for AI development; Yandex has not disclosed whether they were damaged. Western export restrictions could complicate replacement of any destroyed advanced computing hardware. Ukraine has not publicly commented, and the intended target remains unclear because the data center is housed at a machine-tool manufacturing plant linked to Russia’s defense sector. The incident follows Russian strikes on Ukrainian computing and telecommunications infrastructure, which have prompted operators to move equipment underground, migrate data to the cloud and relocate infrastructure abroad, underscoring the importance of geographically separated recovery capacity.

See attribution, scope, and your downstream exposure.
10 events from the most recent confirmed update back to the earliest known activity.
The report said Yandex's larger Kaluga campus was knocked offline on October 10 and a third attack occurred that night. It also reported at least 84 Yandex Cloud services offline, with NetBlocks observing cloud traffic at 30% of its prior level and Cloudflare measuring Yandex-network bot traffic at 0.4% of its preceding two-week peak.
A reported Ukrainian drone strike caused a fire at the industrial site housing Yandex's Sasovo data center, and the facility was shut down; no injuries were reported. It remained unclear whether the intended target was the data center or the associated factory, and Yandex did not disclose whether its two onsite supercomputers were damaged.
Ukrainian officials said a September 23 attack disrupted fixed-line internet access for approximately 100,000 households in Kyiv and the surrounding region. Russian attacks also affected infrastructure belonging to Kyivstar and Ukrtelecom.
Russian strikes late in the month preceding the October report damaged at least six Ukrainian data centers, including facilities operated by MiroHost, Parkovy, Data Group, Utels and Pautina. Some affected facilities were forced to shut down completely.
The machine-tool manufacturing plant housing Yandex's Sasovo data center came under British sanctions because of its involvement with Russia's defense sector.
Yandex established operations in Sasovo on former premises of the Sasta machine-tool factory. The facility later housed the Chervonenkis and Lyapunov supercomputers.
Yandex acknowledged a power outage without publicly attributing it to a drone strike and said it had completed moving workloads to other facilities operating normally. It warned that creation of new cloud resources could remain limited and advised customers to use alternative facilities or availability zones.
NetBlocks observed Yandex connectivity falling to around 70 percent of normal levels as cloud computing, storage, databases and dependent services experienced disruption. Reportedly affected organizations included Russian Railways, T-Bank, Ozon, Wildberries and several media outlets, while a Moscow-region bus operator suspended online ticket sales.
Ukrainian officials said they were strengthening resilience by moving equipment underground, transferring data to the cloud and relocating some infrastructure abroad.
The torrent trackers 1337x and NordicQuality temporarily went offline after their hosting servers were damaged in attacks on Ukrainian infrastructure. Reporting described damage or destruction affecting data centers belonging to at least eight Ukrainian companies.
Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.
See attribution, scope, and whether this vendor sits anywhere in your supply chain.
3 references tracked. Mallory keeps watching after this page renders.
tomshardware.com
Open sourcetomshardware.com
Open sourcetherecord.media
Open sourceMap indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.