Russia says a drone disrupted a Moscow data centre after Ukraine's strikes on two Yandex sites

Two-thirds of Yandex's AI supercomputers sat at Sasovo ^[15], alongside tens of thousands of servers ^[4], and the fire took both supercomputers offline ^[13]. The hub opened in 2014, so it had run for about 12 years when it burned [c5, d2]. Kaluga is the newer and bigger site, at roughly 130,000 square metres and in service for about three years [c6, d3]. Yandex had built its largest data centre by then and still kept most of its supercomputers in the older building [c13, c6].

The fall in Yandex shares ^[9] prices the two strikes. Investors may expect the AI work to be moved or rebuilt, though Kaluga, the obvious destination, was struck the next day ^[6]. A second reading is that the market values Yandex mainly on search and maps ^[11], and the reported damage fell on cloud and AI work ^[7]. The third is that holders priced two strikes and assumed the run would end there. The Moscow report, which came right after the Yandex hits, tests that assumption [c1, c12].

Crypto Briefing wrote that the Moscow strike suggests server farms are becoming targets in the war ^[14]. We think the evidence supports that much [c10, c3, c6], though it falls short of showing a routine. The Moscow account comes from Russian authorities, who did not disclose the facility's operator or how long service was affected [c1, c2].

In our view the exposure the record shows most clearly sits inside one company's layout. A share fall of under 4% ^[9] does not price a second loss on the scale of Sasovo ^[13]. The counter-case is that the Moscow event stays a disruption, Sasovo returns to service and no further server site is hit. If that happens, the markdown was the right price and we were wrong to call it light.