Skip to content

InvestIndependently confirmed4 publishers2 min readPublished

Yandex loses its 50MW Vladimir data centre to the third drone strike in four days

Yandex shut its Vladimir data centre after a drone attack, the third of its sites knocked out within days. Cloud customers absorbed outages across more than 80 services, cryptobriefing reported, and the only share-price reading, a fall of nearly 4%, came after the second strike.

The Investor · Invest desk

How we use AISend a correction

Photograph accompanying Yandex loses its 50MW Vladimir data centre to the third drone strike in four days
Photo: channelnewsasia.com
Vladimir strike disrupted more than 80 Yandex services Who the drone strike on Yandex's Vladimir data centre reaches, and how: cloud customers, users of Yandex services and local residents.

Exposure map, three groups. Cloud customers: computing, storage, databases and YandexGPT APIs affected. Service users: more than 80 Yandex services disrupted. Vladimir residents: a fire and power outages temporarily affected around 5,000 residents.

Vladimir strike disrupted more than 80 Yandex services
WhoHowKindClaim
Yandex Cloud customersAffected cloud services included computing, storage, databases and AI APIs such as YandexGPTexposure4
Yandex service usersMore than 80 Yandex cloud and consumer services were disrupted after the Vladimir strikeexposure3
Vladimir residentsStrike caused a fire and power outages that temporarily affected around 5,000 local residentscost11

What happened

  • A Ukrainian attack shut Yandex's Sasovo hub, which houses two of the three supercomputers the company uses to develop its AI model, CNA reported.
  • Yandex said Ukrainian drones struck its Kaluga data centre southwest of Moscow and put it partly out of action.
  • Outages hit cloud computing, storage, databases and YandexGPT APIs, along with Yandex Music and the Go taxi app.
  • Vladimir governor Alexander Avdeyev confirmed the strike caused a fire and power cuts that briefly hit about 5,000 residents.

Why it matters

  • cost The first cost lands on businesses running on Yandex Cloud: their compute, databases and AI APIs went down with the site, and those without workloads at another provider have to wait for Yandex.
  • constraint If Sasovo's two supercomputers went down with the site, Yandex's AI model development is left on one of its three machines until they come back.
  • precedent If the retaliation account cryptobriefing cites holds, data centres on both sides of the war are now targets, and operators within drone range have to plan capacity around losing a whole site in a day.

Fifty megawatts over up to 2,880 racks is about 17 kW per rack position [10][15]. Yandex took all of it offline at once when it shut the Vladimir site [1]. The timing made the loss harder to absorb. Sasovo had been completely shut down after an attack on October 8, and Kaluga partly disabled on October 9 [5][6], so of the three sites hit, two went fully dark and one partly [14]. A cloud operator moving work off a failed site needs its other sites intact, and by October 11 two of Yandex's were already damaged [14][1]. The reports do not include Yandex's total number of data centres, so the share of its capacity now offline cannot be worked out from them.

Yandex shares fell nearly 4% on the Moscow Exchange after the second strike, cryptobriefing reported [12]. That puts the move after Kaluga and before Vladimir closed [6][1]. Cryptobriefing wrote that the decline "suggests investors are pricing in geopolitical risk that was previously easier to treat as background noise" [13].

We think the operational half of that claim is well supported and the pricing half is thin. The damage is counted in two full shutdowns, one partial one and more than 80 disrupted services [14][3]. The price evidence is one move of nearly 4%, reported by one publisher, taken before the 50MW site closed [12][10]. The counter-case is that a fall that small, after losing one site and part of another, says holders expect repairs and failover to work. Or they were pricing the wider war: Russian air defences reportedly intercepted several hundred drones across regions over the same days [17].

Should the strikes keep coming at this rate, Yandex has to rebuild Sasovo and Vladimir, and that budget comes out of money that would otherwise add new capacity. Cryptobriefing, citing research findings, describes the strikes as Ukrainian retaliation for Russian strikes on Ukrainian data centres in late September and October [16]. If that account holds, the pace on one side may track the pace on the other. A quick return of the services Yandex said were unavailable [9] would make the 4% look like a fair price for a repairable problem.

In our view, physical attack is now a cost of running cloud capacity in Russia, and so far customers have paid it in downtime more than shareholders have paid it in the share price. A fast restoration, with the shares back above their pre-strike level, would show we overstated it.

What to watch

  • How long Yandex takes to bring back the services it said were unavailable, and whether they return from other sites before Vladimir reopens.
  • The first Moscow Exchange price for Yandex after the Vladimir closure, set against the nearly 4% fall that followed the Kaluga strike.
  • Whether new strikes on Ukrainian data centres are followed by strikes on Russian ones, the pattern in cryptobriefing's retaliation account.

Clarity's read

What the record supports and how the coverage leans. The claims behind it follow.

Reality

Evidence58
Adoption
Insufficient
Hype gap+10
Incentives
Insufficient
Confidence60
Why these scores

Claim ledger

Ranked by verification strength, evidence, and original report placement.

  1. [1]

    Yandex said on October 11 that its infrastructure had been damaged in a drone attack, resulting in the complete shutdown of its data centre in the Vladimir region.

  2. [2]

    The Vladimir data centre was the third Yandex facility hit in four days.

  3. [3]

    More than 80 Yandex cloud and consumer services were disrupted after the Vladimir strike.

Sources

4 independent publishers whose own reporting we read for this story.

  1. channelnewsasia.com

    1 article · October 11, 2026

    Russia's Yandex says data centre in Vladimir area shut down after drone attack
  2. cryptobriefing.com

    1 article · October 11, 2026

    Yandex shuts down Vladimir data centre after drone attack, third facility hit in four days
  3. independent.co.uk

    1 article · October 11, 2026

    Ukraine steps up strikes on Russia’s tech infrastructure, damaging third data center in 4 days | The Independent
  4. mezha.net

    1 article · October 10, 2026

    Третій за тиждень датацентр «Яндекса» в Росії атакували дрони – ЗМІ

Share your take

Let Clarity write the post for you.

Signed-in readers get a short post drafted on this story in the register they choose — narrative, analytical, or a direct position — editable to the last word before it goes anywhere. The share buttons at the top of this story work without an account.

Topics and entities

Follow any of these and your For You feed starts watching them — no settings page required.

Entities

Loading related stories