The Cloud Has a Street Address

The cloud has a street address, droog. Occasionally the marketing department needs reminding.

On October 8, Reuters reported that Yandex said drones had hit its data center in Russia’s Ryazan region, causing a fire and forcing the facility to suspend operations completely. That is a report of a physical site shutting down, not evidence that every Yandex service vanished.^[1]

In a separate company statement reported by Kommersant, Yandex said nobody was hurt, the situation at its Sasovo site was under control, and its main services were operating normally. Keep that attribution attached: this is the company’s account, not an independent inspection of the damage.^[2]

The cloud customers had a less soothing morning. At our October 8, 06:44 UTC check, Yandex’s own incident page still marked services in the ru-central1-b availability zone unavailable. The outage began at 01:31 Moscow time. Other zones were described as operating normally, although the company warned that creating new virtual machines, Kubernetes clusters and databases elsewhere could also run into problems. Its latest update said load-switching work was complete; new-resource creation could still be limited.^[3]

Viddy the distinction. A consumer app can keep answering while the machinery underneath loses capacity and customers rearrange workloads. “Still online” is useful. It is a lousy damage assessment.

Cloud brochures offer frictionless abstraction. The actual product needs power, cooling, cables and a building somebody can point at. Geographic redundancy means little if nobody has checked whether the surviving locations have room for the displaced work.

We haven’t independently established who launched the drones or which part of the industrial site was the intended target. Nor does this incident establish permanent data loss. Those blanks stay blank.

For the resilience committee, though, the question is already painfully concrete: when one site disappears from the diagram, where does its work actually go? The next slide had better contain more than a cheerful little cloud.

October 9: a second address loses capacity

Yandex told Interfax that a drone attack damaged part of its Kaluga data-center infrastructure and disabled several modules on October 9. The company warned that some services could face disruption, reported no injuries at that site and said it was assessing the damage. Reuters described the center as partly disabled, following the October 8 shutdown at Sasovo.^[4][5]

The supercomputer detail needs its own date stamp. Yandex’s November 2021 announcement placed two of the three systems it announced then at Sasovo. Reuters reports that Yandex has not confirmed whether those machines were affected. That historical location record does not establish their current configuration, permanent loss or the share of today’s AI capacity taken offline.^[5][6]

The cloud now has a second street address in the incident report, droogs. Redundancy has to mean usable spare capacity somewhere else, not merely another pin on the presentation map. The new evidence adds a second damaged site; it does not establish that every service stopped, either whole facility was destroyed, or permanent data loss occurred.