AnswersPublished31 sources
Yandex Data Center Strikes: What Went Offline—and What the Bot Data Shows
Strikes hit Yandex sites in Sasovo, Kaluga and Vladimir from October 8–11, disrupting infrastructure and services. Yandex arranged for affected cloud customers to move services to Selectel, K2Cloud and VK Cloud; the available reports do not give a firm recovery timeline or confirm specific YandexGPT damage.
Published byEdited with GPT-6 LunaImages generated with GPT Image 2
Research answer
Key takeaways
- Strikes hit Yandex sites in Sasovo, Kaluga and Vladimir from October 8–11, disrupting infrastructure and services.
- Yandex arranged for affected cloud customers to move services to Selectel, K2Cloud and VK Cloud; the available reports do not give a firm recovery timeline or confirm specific YandexGPT damage.
AI Prompt
openai.comCreate a landscape editorial hero image for this Studio Global article: What happened during the Ukrainian drone strikes on Yandex’s data centers in Sasovo, Kaluga and Vladimir between October 8 and 11, how did t. Article summary: The strikes reportedly caused substantial damage and service outages at Yandex, but the available evidence does not establish that they silenced Russian social-media influence operations or reduced support for particular. Topic tags: general, general web, user generated, documentation. Style: premium digital editorial illustration, source-backed research mood, clean composition, high detail, modern web publication hero. Use reference image context only for broad subject, composition, and topical grounding; do not copy the exact image. Avoid: logos, brand marks, copyrighted characters, real person likenesses, fake screenshots, UI text, readable text, watermarks,
Ukrainian drone strikes hit Yandex data centers in Sasovo, Kaluga and Vladimir between October 8 and 11, 2026. The attacks disrupted infrastructure and services, and Yandex arranged for affected cloud customers to move data and services to other providers. A separate claim—that the outages silenced Russian political bots—goes beyond what the available traffic data measures.
What happened at the three sites
- Sasovo, October 8: The facility in Ryazan Oblast was seriously damaged and shut down. Reports described a fire at the site.
6
17
- Kaluga, October 9: A second site was damaged, with several infrastructure modules disabled. Reports did not describe the entire facility as shut down.
9
- Vladimir, October 11: Yandex’s cloud unit said the facility suspended operations after another attack, making it the third affected site in four days.
25
Reports said the outages affected more than 80 Yandex and related services, including cloud platforms, banking apps and ride-hailing. That total is a reported figure, not an independently audited count. 3
4
What is known about YandexGPT and payment services?
Reports said Sasovo housed two of Yandex’s three machine-learning supercomputers, but the systems’ condition after the strike was unclear. The available evidence does not establish which YandexGPT training or inference systems were damaged, or whether specific supercomputers were destroyed. 2
21
Coverage also described disruptions to banking applications and related services, but the provided reports do not establish which payment services failed or how long particular functions were unavailable. 3
4
Yandex’s customer-transfer and recovery plans
Yandex arranged for affected Yandex Cloud customers to relocate data and services to Selectel, K2Cloud and VK Cloud. The providers offered additional specialist teams, simplified onboarding and flexible financial terms to help customers move their infrastructure. 17
18
That arrangement is evidence of a transfer plan—not proof that all customer migrations were completed. Reports said restoration dates for damaged equipment were not yet known. 18
What the Cloudflare traffic drop shows
Cloudflare Radar data cited in reporting showed a steep fall in automated HTTP requests from Yandex’s AS13238 network after the strikes. One report said requests reached 0.3% of the chart’s maximum at 02:00 UTC on October 11, compared with 88.2% at the same hour a week earlier. 5
11
That is a striking change in traffic from one network. It is not a count of social-media posts, political accounts or influence operations. Yandex’s own documentation identifies YandexBot as its primary search-indexing crawler, illustrating why a network’s automated web requests cannot automatically be read as political activity. 30
The data supports the conclusion that automated traffic from Yandex’s network fell sharply during the outages. By itself, it cannot show what proportion of that traffic was search crawling, whether political operators were affected, or whether influence activity elsewhere declined. 5
11
13
Why claims about political bots remain unverified
The outages prompted claims that Russian bot activity had thinned out. Volodymyr Zelensky described the strikes as a “symmetrical response” in the context of Russian attacks on Ukrainian data centers. 7
16 Tomáš Zdechovský shared claims connecting reduced Yandex-network traffic to Russian bots; a separate post about activity surrounding Germany’s AfD framed the apparent drop as conditional.
27
50
51
Other commentary said Timothy Snyder helped spread the broader claim that Russian bot armies had gone quiet. But the available reporting does not provide verified measurements of pro-Trump or MAGA activity, or establish that those political conversations changed because of the strikes. 31
The same limitation applies to claims about declining Reform UK activity: the provided evidence does not include independently verified platform measurements for that claim. A sharp decline in requests from Yandex’s network cannot, on its own, establish a decline in activity across social platforms or political groups. 5
11
13
A separate criticism focused on a circulating chart that appeared to show a data point for October 15 even though it was being shared on October 11. One source reported that computer scientist Raphael Wimmer suspected the chart was AI-generated; the apparent date inconsistency is a reason for caution, not by itself conclusive proof of how the chart was made. 43
45
The defensible conclusion
The strikes damaged three Yandex data centers, disrupted services and prompted plans to transfer affected cloud customers to other providers. Automated requests from Yandex’s AS13238 network also fell sharply. But that network-level measurement does not verify claims that Russian social-media influence operations—or support for specific political parties—declined as a result. 3
5
11
17
Studio Global AI
Continue your research
This page includes a source-backed answer you can continue inside Studio Global.
People also ask
What is the short answer to "Yandex Data Center Strikes: What Went Offline—and What the Bot Data Shows"?
Strikes hit Yandex sites in Sasovo, Kaluga and Vladimir from October 8–11, disrupting infrastructure and services.
What are the key points to validate first?
Strikes hit Yandex sites in Sasovo, Kaluga and Vladimir from October 8–11, disrupting infrastructure and services. Yandex arranged for affected cloud customers to move services to Selectel, K2Cloud and VK Cloud; the available reports do not give a firm recovery timeline or confirm specific YandexGPT damage.
Sources
tvoemisto.tvStrikes on Yandex data centers disrupted more than 80 Russian services