Between October 8 and 16, 2026, Ukrainian long-range drones did something that hasn’t happened since the war began: they physically bombed Russia’s internet infrastructure. The target was Yandex — the company people call “Russia’s Google” — and in the space of about a week, three of its major data centers were knocked out or badly damaged, followed by a strike on a massive data center belonging to Sberbank, Russia’s biggest bank.
If you caught this story on social media, you probably heard one version of it: “Ukraine bombed the data centers, and suddenly the Russian bots went silent.” That version is mostly wrong — and untangling it is a useful lesson in how fast a viral claim can outrun the actual data.
This is a plain-language rundown of what we actually know, and what we don’t.
What happened: the timeline
The strikes came fast, and each one landed on a different key facility. Here’s the sequence, with the basic confirmed facts:
October 8 — Sasovo (Ryazan Oblast, southeast of Moscow). A drone attack ignited a fire at a Yandex data center, forcing the company to suspend operations entirely. This was the first confirmed strike on Russian data infrastructure since the 2022 invasion, and it came weeks after Moscow had begun hitting Ukrainian data centers[^1]. The site housed two of Yandex’s three AI supercomputers[^2].
October 9 — Kaluga (southwest of Moscow). A second strike damaged Yandex’s largest data center; several server modules were taken out of service[^3].
October 11 — Vladimir (east of Moscow). A third strike damaged infrastructure and forced a complete shutdown. Yandex’s cloud platform lost power in a core availability zone, and services began failing not just in Russia but in neighboring countries[^4]. At the low point, Yandex’s network traffic collapsed by roughly 99% from baseline[^5].
October 14 — Balakovo (Saratov Oblast). Ukrainian drones hit a data center under construction for Sberbank, Russia’s largest bank. The project is valued at 122.2 billion rubles (about $1.4 billion), and was intended to host Russia’s biggest supercomputer and parts of the state’s “GosTech” digital platform[^6].
October 16 — Vladimir, again. Residents reported another round of explosions near the Yandex facility, and monitoring services logged a fresh ~10% outage rate across Yandex products[^7].
The “why now” is important context and easy to miss: Kyiv has repeatedly framed these strikes as “mirror” retaliation. In late September, Russia bombed multiple Ukrainian data centers — including Kyivstar’s headquarters and a Vodafone facility — knocking out internet access for roughly 100,000 households around Kyiv[^8]. Ukraine’s message was effectively, “you hit our internet, so we’ll hit yours.”
Why Yandex matters (in 30 seconds)
You can’t understand the impact without first grasping how much of Russia runs through this one company.
Yandex is more than a search engine (where it holds roughly 72% market share). It’s maps, ride-hailing (Yandex Go), food delivery (Yandex Eda), digital payments (Yandex Pay, the de-facto replacement for Apple Pay after Visa/Mastercard left), music, email, and a smart-home assistant called Alisa. In Russia, one company plays the role that Google, Uber, DoorDash, and Apple Pay play separately in the West[^9].
Crucially, there’s also a hidden business-to-business layer: Yandex Cloud, which serves more than 64,000 corporate clients. When Yandex’s data centers go down, it’s not just consumers who lose access — it’s retailers, banks, apps, and companies that quietly run on Yandex infrastructure[^10].
The hard numbers
A quick “by the numbers” snapshot of the confirmed scale:
| Metric | Figure | Source |
|---|---|---|
| Yandex data centers knocked out/degraded | 3 in 4 days | DCD |
| Peak drop in Yandex network traffic (Oct 11) | ~99% below baseline | Cloudflare |
| Services affected at the Vladimir site | 80+ (company’s own count) | Charter’97 |
| User outage complaints (≈24-hour window) | ~435,000 | UNITED24, citing Verstka |
| Yandex market-cap loss (2 days) | 77bn rubles (~$918.5m), −5.4% | The Moscow Times |
These are the confirmed numbers. Notice that the eye-popping “99% drop” and the “bots went silent” chart are the same underlying data — and that’s exactly where the story got messy.
What it felt like on the ground
The stats only tell half of it. The accounts from inside Russia are startlingly concrete, and they’re the strongest evidence that this wasn’t an abstract infrastructure story.
Consider the people caught in it:
A Moscow taxi driver described “phantom orders” — the system sending four different cars to the same passenger — and, more seriously, being unable to withdraw his earnings, which made it impossible to keep paying for his rental car and fuel. He ultimately returned the car because he couldn’t afford to keep driving while not earning[^11].
A Moscow woman saving for a car woke up to find 1.5 million rubles (about $17,830) no longer visible in her Yandex Pay account. “The panic got the better of me, and I cried my eyes out,” she told CNN. Yandex insists the money itself was never at risk — the balances were stored elsewhere — but the display of it disappeared[^11].
A St. Petersburg resident came home to a dark apartment because his smart light bulbs, controlled through Yandex’s Alisa assistant, had stopped working. “It felt like a power outage,” he said, “just for a rather unusual reason.”[^11]
A travel-agency founder feared she had lost a website she’d built over ten years, along with its databases, photos, and reviews[^12].
None of this is a war-crimes story. It’s a reminder that “the cloud” — a word we treat as abstract — is a handful of actual buildings, and that a lot of ordinary life is wired into a very small number of them.
The part everyone got wrong: the bots
And now the correction, because this is where most of the early coverage went sideways.
Within days of the strikes, a specific claim went viral: Ukraine had destroyed the servers hosting Russia’s propaganda bot networks. Ukrainian President Volodymyr Zelensky himself fed it, telling the Warsaw Security Forum that social media had “suddenly become a little easier to breathe” — and pointing at the drop as proof of where the bots lived[^13]. Garry Kasparov and other high-profile accounts reported their feeds suddenly felt free of pro-Russia, pro-Trump, and pro-AfD accounts. A dramatic Cloudflare chart showing automated traffic from Yandex collapsing to near zero got shared everywhere.
The problem: the chart didn’t show what people said it showed.
Here’s what the data actually revealed, laid out step by step:
It was mostly search crawlers, not trolls. Cloudflare’s own analysis found that the traffic that vanished was overwhelmingly Yandex’s legitimate search crawler — the software that indexes web pages so Yandex Search can find them. When the data centers went down, Yandex simply stopped crawling the web. News and publishing sites that relied on Yandex indexing saw a 44% drop in traffic from Yandex networks[^5].
Malicious bots didn’t die — they moved. The genuinely suspicious automated traffic (vulnerability scanning, plugin probing) initially fell, but Cloudflare found it quickly migrated to other hosting providers within hours. Traffic targeting gambling sites from Russia-origin bots was essentially flat over the strike week. A data center going dark stops the servers, but workload is portable — if you’re running a bot operation, you just spin it back up somewhere else[^5]
Independent researchers found no evidence of silenced troll farms. Graphika, an influence-tracking firm, tested the viral claims directly and found no drop in active accounts or top posters in the AfD, MAGA, and Reform UK communities people claimed had “gone quiet.” Russian-language Telegram posting fell only 5–15% — consistent with ordinary internet disruption, not destroyed influence operations[^14].
A fabricated chart made things worse. Deutsche Welle documented a fake, doctored graph circulating alongside the real Cloudflare chart — further muddying the water for anyone trying to figure out what actually happened[^15].
The deeper reason the “bots silenced” story was always unlikely: sophisticated influence operations don’t need to run from identifiable Russian servers. They use foreign hosting, VPNs, and proxies specifically to obscure their location — meaning their activity would never show up in Yandex-origin traffic in the first place[^16]. As one disinformation researcher put it plainly: “We can’t simply bomb the bots out of existence, however appealing that might sound.”[^17]
Bottom line: the bombings were real and the infrastructure damage was real. But the “Russia’s bots went silent” narrative was largely a misreading of a traffic chart, turbocharged by wishful thinking. That distinction matters — because in a story this fast-moving, the correction is what separates an explainer from a meme.
Where things stand
As of this writing, Yandex is still limping: the company waived cloud and software fees through the end of October, added a force-majeure clause to its user agreement (explicitly covering drone and missile attacks), and has said engineers are working around the clock but cannot give a firm restoration timeline[^18].
The Kremlin has publicly acknowledged the problem is serious — a rare admission — while leaving the burden on private companies to protect their own infrastructure[^19].
In Part 2, we’ll look at who actually pays when the cloud goes down: the banks, the delivery networks, the gig workers, and the small businesses that bet their operations on Yandex’s concentration. In Part 3, we’ll get into the technical and strategic questions — whether you can rebuild a data center in a war zone, how long it really takes, and what this means for the worldwide data-center industry.
Sources
[^1]: The Moscow Times, “Ukrainian Drones Hit Yandex Data Center, Industrial Facilities Across Russia,” (Oct. 8, 2026). Link
[^2]: Data Center Dynamics, “Yandex data center hit in drone attack in Russia,” (Oct. 8, 2026). Link
[^3]: BBC News, “Ukraine strikes Yandex data centre in third attack on Russian tech giant,” (Oct. 11, 2026). Link
[^4]: Data Center Dynamics, “Third strike on Yandex data center in Russia,” (Oct. 12, 2026); The Register, “Ukrainian drone strikes on Yandex datacenters knock cloud and payments offline,” (Oct. 12, 2026). Link
[^5]: Cloudflare, “Yandex outage: data shows that instead of going dark, malicious bots went on the move,” (Oct. 14, 2026). Link
[^6]: The Moscow Times, “Ukrainian Drones Hit Sberbank Data Center After Yandex Attacks,” (Oct. 14, 2026); POLITICO, “Ukrainian drones strike data center of Russia’s biggest bank,” (Oct. 14, 2026). Link
[^7]: Charter’97, “In Vladimir, Drones Launched Another Attack On The Yandex Data Center,” (Oct. 16, 2026). Link
[^8]: The Guardian, “Russia strikes Ukraine’s digital economy with attacks on ISPs and datacentres,” (Sept. 26, 2026); The Moscow Times (via Reuters), “Russia Hits Ukraine’s Largest Mobile Provider, Strikes Data Centers,” (Sept. 27, 2026). Link
[^9]: The Moscow Times, “Ukraine’s Strikes on Yandex Data Centers, Explained,” (Oct. 12, 2026). Link
[^10]: Ibid.; Habr, “Yandex Cloud работает в аварийном режиме после атак на три дата-центра Яндекса,” (Oct. 12, 2026). Link
[^11]: CNN, “Ukraine targets Russia’s ‘Google’ as the internet becomes a new front line,” (Oct. 17, 2026). Link
[^12]: The Independent, “Broken dating apps and delayed takeaways: How Ukrainian strikes on data centres are upending daily life in Russia,” (Oct. 15, 2026). Link
[^13]: Euronews, “Did Ukrainian strikes on Yandex data centres cause Russian bot activity to plummet?,” (Oct. 12, 2026). Link
[^14]: Graphika, “Did the Yandex Data Center Strikes Silence Russian Bots? What the Data Shows,” (Oct. 13, 2026). Link
[^15]: Deutsche Welle, “Fact check: Fake graph on alleged Russian bot activity,” (Oct. 14, 2026). Link
[^16]: Lawfare (Renée DiResta), “The Russian Bots Went Silent. Or Did They?,” (Oct. 14, 2026); BBC Verify, “Is Zelensky right to say data centre strikes have taken down Russian bots?,” (Oct. 13, 2026). Link
[^17]: The Guardian, “Did Ukrainian strikes on Russian datacentres reduce online disinformation?,” (Oct. 13, 2026). Link
[^18]: The Moscow Times, “Yandex Waives Cloud and Software Fees After Ukrainian Drone Attacks on Data Centers,” (Oct. 13, 2026); Habr, “Yandex Cloud работает в аварийном режиме после атак на три дата-центра Яндекса,” (Oct. 12, 2026). Link
[^19]: Reuters, “Kremlin says government is discussing Yandex’s problems after Ukrainian strikes,” (Oct. 13, 2026). Link
2 thoughts on “Part 1 – Russia’s Google Went Dark — Here’s What We Actually Know”