Yandex confirmed a drone attack shut its Vladimir data centre — the third shutdown in four days after Sasovo and Kaluga. 80+ services disrupted, no repair timeline.
Published 12 October 2026 · 06:00 GMT
On Sunday morning in Moscow, taxi driver Pavel Belyavskiy stared at his phone the way sailors once stared at a dead compass. He pressed the call button for a passenger, then again. Nothing happened. Two hundred kilometres away, the Vladimir data centre running his ride was cooling down — hit, the company said, by a drone attack.
Yandex confirmed on Saturday that a drone attack had damaged its data centre in the Vladimir region, east of Moscow. "Operations completely suspended," the company said in a statement carried by the state news agency TASS. No one was hurt. Emergency services were on site, and the company said there were no casualties.
The alert sent to cloud customers was blunter than the press statement. In a post on Telegram, Yandex Cloud told clients: "As a result of an UAV attack, the infrastructure of Yandex's data center in Vladimir was damaged. The data center's operation has been completely suspended. There are no casualties." It added that "the remaining resource configuration is considered unstable", that the platform had been placed in emergency mode, and that customers should activate their disaster-recovery plans.
Three data centres in four days is not an IT incident. It is a campaign.
Vladimir was the third such strike in four days. On October 8, a drone attack on the facility in Sasovo, in the Ryazan region, started a fire that forced a full suspension of operations — the site houses two of the three AI supercomputers Yandex uses to train its artificial-intelligence models. The next day, October 9, drones hit the Kaluga data centre, knocking several modules "completely out of service" at what the company describes as its most powerful Russian facility. Then, overnight from October 10 to 11, came Vladimir — and the third complete shutdown in a row.
The numbers explain why this sequence matters. Vladimir can draw 50 megawatts of power and house up to 2,880 server racks; Kaluga runs at 63 megawatts with more than 3,800 racks; Sasovo hosts tens of thousands of servers and ranks among the company's five main hubs. Yandex is worth roughly $16 billion — its market capitalisation this month — controls about 70 percent of Russia's search traffic, and sits at the centre of the country's AI development. This is not a peripheral web host. It is the backbone of the country's consumer internet.
The strongest public claim of Ukrainian involvement came not from Kyiv's military but from its president. On Thursday, after the Sasovo strike, Volodymyr Zelenskyy said: "We always respond in mirror-like fashion... they have been hitting and continue to hit our data centres. We are responding." It is the closest thing to an attribution on the record. Russia has struck several Ukrainian data centres and telecom facilities over the past month, including sites in central Kyiv, according to Reuters and the BBC — and the mirror logic extends to Ukraine's own losses, including the earlier Russian strike on Pryluky that killed 20. But whether Ukraine carried out the Vladimir strike in particular has not been confirmed, and it should not be stated as fact.
Other circulating claims deserve the same caution. Firepoint, a Ukrainian drone manufacturer, says its FP-1 one-way attack drones were used against the Kaluga site — a company claim that has not been independently verified. The Ukrainian outlet UNN has linked the Vladimir outage to a Ukrainian strike; that is reported, not confirmed. What is confirmed is the pattern. The war's digital front is no longer confined to hackers and severed cables. It now has an aerial dimension, and it is striking civilian infrastructure on both sides.
Further than the three buildings. More than 80 cloud services and components were disrupted, including Yandex's AI model API, known as YandexGPT. The retrieval and OCR APIs, AliceAI Pro, and SpeechSense — the voice-synthesis service — were listed as unavailable, and quota increases for new cloud resources were suspended. The advice to business customers to activate disaster-recovery plans was not decoration; it was the difference between a bad weekend and a lost week.
For the businesses renting Yandex’s cloud, the weekend was a drill nobody had scheduled. Disaster-recovery plans exist in every corporate handbook; almost none were written for a scenario in which the primary site and the very idea of a safe region both fail in the same week. Yandex told customers to activate theirs — the cloud industry’s equivalent of a captain telling passengers to find their life jackets: reassuring in theory, and a sign the crew has run out of better options. Small firms on single-cloud architectures had the worst of it: no second provider, no standby region, just a status page and a Telegram post.
The consumer damage was mapped by Astra, a Russian outlet, and it was geographic: outages in dozens of Russian cities, spilling across borders into Kazakhstan, Belarus and Armenia. Taxi services stuttered, banking-adjacent tools froze, Yandex Music and Yandex Go fell silent. Belyavskiy, the Moscow driver, summed it up: "I'd press the call button to contact them, but nothing happens."
Secondary outlets describe knock-on failures in services never hit directly — T-Bank, Ozon, Wildberries, Magnit, Fix Price, Russian Railways ticketing, the 1C accounting software used across Russian business, even the news agencies RIA Novosti and Interfax — all taken offline through an infrastructure partner caught in the strikes. That full list comes from secondary reporting and should be treated as unconfirmed. What is confirmed: Vladimir's governor, Alexander Avdeyev, said the strike caused a fire and power outages that temporarily affected about 5,000 local residents. And the market noticed the sequence too — Yandex shares fell nearly 4 percent on the Moscow Exchange after the second strike, according to cryptobriefing.
It exposes the structure underneath the map. A data centre is a strange kind of infrastructure: invisible when it works, and instantly political when it doesn't. Three facilities taken offline in four days is not an IT incident — it is a campaign, and the target selection says what the campaign is about. Russia's state spent years pushing its digital life into domestic hands: domestic search, domestic cloud, domestic AI, domestic everything. The concentration that made that strategy efficient is the same concentration that made it hittable. One company, three buildings, and a country's taxi drivers find out what single points of failure feel like.
The money is blunt here. Yandex is a $16 billion business with investors, advertisers, merchants and drivers whose livelihoods run through its APIs. A strike on a data centre is, in the same week, a military act and a commercial event — shares down nearly 4 percent, quota increases frozen, taxi commissions evaporating in dozens of cities. Wars that reach the cloud do not stay in the cloud; they arrive, within hours, in the wallets of people who never consented to any of it.
History has a pattern for this. Every war that learns to reach a country's infrastructure eventually reaches its information infrastructure — telegraph wires in the 19th century, radio towers in the 20th, fibre and data centres now. What is new is the symmetry: Russia has been hitting Ukrainian data centres for a month, Ukraine is now answering against Russian ones, and both sides have discovered that the civilian internet is a legitimate-looking target once the other side hits yours first. The rule, once broken, gets broken twice. The strikes land in a week of other pressure on Russia's research establishment too — in an entirely different register, a plague death at a Siberian laboratory reminded the country that its scientific infrastructure is fragile in more ways than one.
Much remains unknown. Yandex has said nothing about whether the AI supercomputers at Sasovo were physically damaged — the hardware question that matters most for Russia's AI programme. No repair timeline or cost estimate exists. The full knock-on list stays unconfirmed. And the open question is the one Zelenskyy's mirror logic poses: if this is a campaign, not an incident, then the next strike is a matter of scheduling, not speculation. Watch the frequency — a fourth strike in the coming days would confirm the pattern — and watch whether Moscow answers by hitting Ukrainian data centres harder, or by holding something in reserve.
The Western coverage treats the three strikes as a campaign, not a coincidence. The BBC, Reuters and Al Jazeera all frame it the same way: Ukraine is deliberately degrading the domestic technology backbone of a much larger adversary — hitting the AI training capacity and cloud infrastructure that Russia's war economy and civilian life both depend on. Zelenskyy's "mirror-like fashion" remark is read as the closest thing to a claim of responsibility, and the symmetry with Russian strikes on Ukrainian data centres is presented as the motive. The phase of the war has changed: digital infrastructure is now a front like any other.
The same outlets dwell on the civilian spillover — taxis, music, banking tools — not to moralise but to illustrate reach. A campaign that knocks 80-plus services offline in a weekend is a campaign that civilians feel immediately, and that immediacy is part of the point: the pressure is meant to be felt in Moscow as well as in Kyiv. The unanswered question in the Western telling is whether the AI supercomputers were physically damaged — the difference between a temporary outage and a strategic setback for Russia's AI ambitions.
The Eastern telling is clipped and factual. TASS carries the company statement almost verbatim: infrastructure "damaged", operations "completely suspended", no casualties, emergency services on site. Governor Avdeyev's Telegram notes the fire and the power outages affecting about 5,000 residents, then moves on. There is no attribution, no accusation, no rhetoric about mirror strikes — the event is reported as an emergency-management problem: a fire to put out, a grid to stabilise, services to restore.
What the Eastern coverage does not do is theorise. The sequence — three facilities in four days — is not assembled into a campaign narrative; each strike is reported on its own terms. The restraint reads as deliberate: a government and a company declining to hand Kyiv the satisfaction of an acknowledged campaign, and declining, equally, to panic a domestic market that has just watched a $16 billion company's shares fall. The silence on the AI supercomputers is the loudest part — the question everyone is asking is the one nobody in Moscow is answering.
In the Global South telling, the striking detail is not who launched the drones but what they hit: a single country's near-total dependence on a single company's cloud. The Hindu BusinessLine and Nepal's Technology Khabar frame the three strikes as a cautionary tale about concentration — 80-plus services disrupted, taxis and banking tools frozen not just in Russia but in Kazakhstan, Belarus and Armenia. For countries building their own digital stacks, the lesson is uncomfortable: efficiency and sovereignty are both served by consolidation, until the consolidated thing becomes the target.
The Southern coverage also notes the symmetry the other frames underplay: Russia has been hitting Ukrainian data centres for weeks. This is not one side's escalation but both sides' discovery — the civilian internet as a theatre of war, entered from both directions. For the rest of the world, the takeaway is practical rather than partisan: disaster-recovery plans are not paperwork. Yandex told its own customers to activate theirs, and for once the fine print was the story.
Three facilities in four days: Sasovo in the Ryazan region on October 8, hit by a drone attack that started a fire; Kaluga on October 9, where several modules were knocked "completely out of service"; and Vladimir, east of Moscow, overnight from October 10 to 11, with operations "completely suspended". Together they represent a large share of Yandex's Russian cloud capacity.
Not directly. After the Sasovo strike, President Volodymyr Zelenskyy said Ukraine responds "in mirror-like fashion" to Russian attacks on Ukrainian data centres — the closest thing to an attribution on the record. The Ukrainian outlet UNN linked the Vladimir outage to a Ukrainian strike, but that is reported, not confirmed. Kyiv's military has confirmed none of the three attacks.
More than 80 cloud services and components, including the YandexGPT AI model API, the retrieval and OCR APIs, AliceAI Pro, and the SpeechSense voice service. Quota increases for new cloud resources were suspended. For consumers, Yandex taxi, banking-adjacent tools, Yandex Music and Yandex Go were hit across dozens of Russian cities, plus Kazakhstan, Belarus and Armenia.
Unknown. Sasovo houses two of the three AI supercomputers Yandex uses to train its AI models, which is why the strike drew so much attention. But Yandex has said nothing about physical damage to that hardware — only that the facility's operations were fully suspended. Whether Russia's AI training capacity took a lasting hit is the biggest open question of the sequence.
Investors price in disruption. Yandex shares fell nearly 4 percent on the Moscow Exchange after the second strike, according to cryptobriefing. A company worth about $16 billion, handling roughly 70 percent of Russian search and sitting at the centre of the country's AI development, had three core facilities knocked offline in four days. Markets do not need a repair bill to recognise damage.
