Yandex: the cloud has an address

The damaged centres are physical places: Reuters locates the first two strikes in Sasovo and then the Kaluga region of Russia. Its 9 October report draws partly on Yandex for attribution to Ukraine. We have not independently investigated the weapons used.^[3]

Book a ride, receive a payment, retrieve a file: an outage reaches people through ordinary actions. T-Journal describes disruption after strikes on Yandex data centres, followed by the gradual return of services. On 13 October, the company announced that payments to drivers were resuming. Recovery does not arrive as one event for every user.^[2]

The accessible 14 October account still described uneven recovery: T-Journal reported that bulk downloading on Yandex Disk remained disabled. That report cannot establish the full service position on 15 October. It does make the physical reality behind the “cloud” harder to ignore: files and earnings depend on buildings, electricity and machines that must be replaceable.^[2]

Another story spread: collapsing traffic meant the propaganda machines had disappeared. Cloudflare’s data does not establish that. The search-network decline mostly involved verified indexing crawlers; some malicious cloud activity relocated. Cloudflare’s view is limited to the network it observes.^[1]

Both points matter: physical damage has consequences, and a graph alone cannot identify what has been neutralised. For customers, the useful question is which services return and which data can be recovered. Understanding influence operations requires evidence that actually measures them.