Disruption across three Yandex data-centre locations has left recovery work ongoing. For affected customers, the urgent question is whether critical workloads can run somewhere else before the provider finishes restoring services. Yandex's corporate notice separates three events. Its Sasovo site stopped operating after serious damage during the night of 7 to 8 October. Part of the Kaluga infrastructure failed after another attack on 9 October. The Vladimir site stopped operating after an attack during the night of 10 to 11 October. The notice was published on 9 October and revised on 11 October. In its 18:44 GMT+2 update on 13 October, Yandex Cloud incident 2136 said the platform's status had not changed and that teams were continuing to restore services. An earlier update described Yandex Cloud as operating in limited mode. The record gives no reliable restoration time. Another update advised customers to use alternative sites for hosting and reserving resources. The latest update points readers to separately maintained guidance for individual services. That matters because the incident record does not show that every service or workload has the same impact. Each team still needs to establish which dependencies are working, degraded or unavailable. A 13 October update also said current customers would not be charged for Yandex Cloud services used in Russian availability zones from 8 through 31 October, with the adjustment applied automatically. That reduces incident costs, but it does not prove an application can recover elsewhere. Recovery begins with a usable copy of state A recovery environment…