Bloomberg: $35/month. Financial Times: $42/month. The Economist: $17/month. Original analysis by Tatsu with 40+ footnotes: $8/month, 7-day free trial. This post is public. Share it with anyone who should see this. Everyone has been watching the oil refineries. For two years the story of Ukraine's deep-strike campaign has been fuel: Ryazan, Omsk, Yaroslavl, the long columns of black smoke that cost the Kremlin export revenue by the tanker. That campaign is real, and it is grinding, and it has never quite been the knockout blow the headlines promised. Then, over four days in October, Ukraine hit something the refineries never were. Between October 8 and October 11, Ukrainian drones struck three Yandex data centers in Sasovo, Kaluga, and Vladimir.[1] Yandex is the company that runs Russian search, maps, ride-hailing, music, cloud, and a growing share of Russian payments. Inside two of those buildings sat the machines that matter most: Yandex's supercomputers, the only frontier-scale AI training hardware the Russian private sector owns. By the morning of October 11, Ukrainian military accounts were claiming what the specs quietly confirmed. Three out of three. All three Yandex supercomputers, the entire fleet, sitting in facilities that were now either on fire or dark.[2] [3] Start a 7-day free trial to read the structural analysis when it's paid. $80/year if you stay, less than two Bloomberg sandwiches. Plywood Against Petaflops The weapon was the FP-1, a Ukrainian long-range strike drone that costs around $55,000 a unit.[4] It is a cheap airframe with a 120-kilogram warhead and a range of at least 1,600 kilometers, with upgraded versions reaching far deeper. Ukraine now builds roughly three thousand of them a month. The same family of drone flew 2,500 kilometers to shut Russia's largest oil refinery earlier this year. What it hit in Sasovo was not cheap. The Sasovo facility near Ryazan houses two of Yandex's three supercomputers, Chervonenkis and Lyapunov.[5] Chervonenkis is the company's most powerful machine: 21.53 petaflops, 1,592 Nvidia A100 GPUs, 199 nodes. When it came online in 2021 it ranked nineteenth in the world.[6] The Vladimir data center, hit three days later, houses the third machine, Galushkin, another 16 petaflops and 1,088 A100s.[7] Add just those two machines together and you are looking at more than 2,600 Nvidia A100 accelerators. Those are export-controlled chips. Russia cannot legally buy them, and the gray-market channels that smuggle a server rack at a time do not replace twenty-six hundred of them in a quarter. A refinery can be patched. A100s do not grow back. Russia's Amazon, Not Its Google Westerners hear "Yandex" and think of a Russian Google, a search box with a different logo. The better comparison is Amazon, and not the store. The cloud underneath it. Yandex Cloud is to Russia roughly what Amazon Web Services is to everyone else, the invisible utility that other people's apps are quietly built on top of. When a single AWS region in Virginia hiccups, half the world's mobile apps stop loading and most users never learn why. Yandex is that layer for Russia, plus the search box, plus the maps, plus the bank. The outage map proved it. When Vladimir went dark, more than eighty Yandex Cloud services went offline, including the YandexGPT API that Russian companies had been building on.[8] A glitch in Yandex Pay knocked out banking access for ordinary users. Shoppers could not check out at the retail chains Magnit and Fix Price. The ride-hailing app died not only across Russia but in Serbia, Belarus, Kazakhstan, and Armenia. A drone in Ryazan stranded a dinner reservation in Belgrade. Yandex's own traffic told the story in three numbers. Against its late-September baseline, main-network traffic fell about 25% on October 8, 35% on October 9 and 10, and 94% on October 11.[9] By the third strike, Yandex Cloud was telling paying customers it was running in emergency mode and advising them to fail over to their own disaster-recovery plans, which is cloud-provider language for "you are on your own." The company's reassurance to its banking users was its own small masterpiece. Your money is safe, Yandex said, because the money was never in the building. Only the ability to reach it was.[10] Bots Went Quiet, Nobody Can Prove Why Here is where the story gets interesting, and where it needs a firm hand. Within a day of the strikes, social-media users across Europe and the United States started claiming that something had changed in their feeds. The familiar swarms, the AfD amplifiers in Germany, the MAGA reply-guys in America, seemed thinner. Quieter. On October 12, at the Warsaw Security Forum, Volodymyr Zelensky said it out loud: "When our strikes reached Yandex's data centers, it suddenly became a little easier to breathe on many social media platforms. There is less hatred, less discord, fewer provocations, because the number of bots has decreased."[11] It is a seductive claim, and it should be handled like one. No intelligence agency has confirmed that Russian influence operations ran on the specific hardware Ukraine just burned, and the available network data does not actually show a measurable drop in political-bot activity tied to the outage.[12] The honest version is narrower and stranger: millions of people were willing to believe, instantly and without evidence, that Western political discourse is partly hosted in a warehouse outside Moscow. That belief is a fact even when the bot drop is not. It tells you exactly how much trust the global internet places in the integrity of its own argument. If the link is ever proven, it reframes the whole campaign. Ukraine would not have degraded a logistics node. It would have unplugged a propaganda utility, and the first customers to notice would have been voters in countries that are not at war. Compute Has a Street Address Strip away the bot intrigue and a harder lesson remains, and it is the one that should worry every government and every hyperscaler watching. For a decade the industry has talked about compute as if it were abstract, a number on a slide, a line item called "capacity." The Yandex strikes are a reminder that compute is a physical object in a specific building with a specific roof, and that the roof can be reached by a plywood aircraft built for the price of a Honda. Russia's response was a late-August decree letting the state seize critical infrastructure from operators who fail to defend it adequately, which is the bureaucratic equivalent of telling someone to stand closer to the smoke detector.[13] Russian data-center operators are now budgeting for air defense as a line item, something no cloud business anywhere priced into its margins a year ago. The timing rhymes with something I wrote about last week. Markets are starting to treat AI compute as collateral, as the hard asset underwriting hundreds of billions in circular financing. Collateral is supposed to be the safe part of the balance sheet. Collateral is not supposed to be flammable. A GPU cluster that can be deleted by a $55,000 drone is a different kind of asset than the spreadsheets assume, and the people who insure it are about to find out which kind. Ukraine spent roughly the cost of a nice car to take Russia's entire private-sector AI brain offline, strand payments in four countries, and hand half the internet a reason to believe its trolls had a mailing address. The refineries were the long war. This was the afternoon someone proved that the most valuable machines on earth sit under roofs. Coming next, paid only: the compute-as-collateral problem in full. Why the physical geography of AI training is now a strategic vulnerability, what the bot-farm claim would mean if the forensics ever confirm it, and why the people financing the AI build-out are holding an asset that can be reached from the sky. 7-day free trial. Cancel anytime. $80/year if you stay, or $8/month. Three drones, three supercomputers, four days: the war just reached the server room, and the analysis of what that means for the AI build-out is paid. Notes [1] "Russia's Yandex says data centre in Vladimir shut down after drone attack." Al Jazeera, October 11, 2026. Confirms the three-site sequence: Sasovo (October 8), Kaluga (October 9), Vladimir (October 11), the third hit in four days. [2] "Three out of three. Ukrainian FP-1 drones hit the last supercomputer of the 'Yandex' service in Russia." UNN, October 2026. Ukrainian reporting that all three Yandex supercomputers are now unavailable after the Vladimir strike; the supercomputers' operational status has not been independently confirmed by Yandex. [3] "Ukraine's Strikes on Yandex Data Centers, Explained." The Moscow Times, October 12, 2026. Overview of the strike campaign, Yandex's role in Russian digital life, and the service disruptions that followed. [4] "Ukraine's $55,000 plywood drone flew 2,500 km and shut down Russia's largest oil refinery." Tom's Hardware, 2026. FP-1 cost, range, warhead, and the earlier Omsk refinery strike at roughly 2,500 km. [5] "Ukraine strikes Yandex data center housing two of the company's supercomputers." Meduza, October 8, 2026. Confirms the Sasovo facility near Ryazan houses Chervonenkis and Lyapunov, two of Yandex's three machines used to train neural networks. [6] "Chervonenkis supercomputer." ICT.Moscow. Specifications: 199 nodes, 21.53 petaflops, 1,592 Nvidia A100 80G GPUs, 199 TB RAM; ranked 19th on the TOP500 in November 2021. [7] "Galushkin supercomputer." ICT.Moscow. Specifications: 136 nodes, 16.02 petaflops, 1,088 Nvidia A100 80G GPUs; second-fastest system in Russia, housed at the Vladimir data center. [8] "Yandex shuts third data center after drone strike, cutting 80-plus cloud services." Implicator.ai, October 2026. More than 80 Yandex Cloud services offline including the YandexGPT API; Yandex Pay failures cut banking access; outages at Magnit and Fix Price. [9] "Ukrainian drone strikes on Yandex