On November 10, 2026, Yandex said access had been restored to 97.16% of the customer data affected in Yandex Cloud; it said the remaining 2.84% could not be recovered. Those percentages refer to affected data, not the share of customers. Interfax reported the recovery figures.

Yandex attributed the unrecoverable data to critical equipment damage and affected customers not having backups on the platform, according to a Reuters report carried by Channel NewsAsia.

October’s data-center damage

An October 11 news clip covers reported damage at Yandex data centers and related network disruption.

Interfax reported damage at Yandex’s Sasovo data center on October 8 and at its Kaluga site on October 9, followed by an attack on the Vladimir center on October 11. Operations in Sasovo and Vladimir stopped completely, while several modules in Kaluga were disabled. NeoTeo covered the platform’s emergency status in an earlier report on October 12.

An October 11 KitCut video cited NetBlocks for Yandex Cloud connectivity at 30% of normal and said the service’s status page listed at least 84 services offline.

What Yandex planned for new virtual machines

Yandex said backups would be enabled by default when customers created new virtual machines, with an option to turn them off. Previously, customers had to activate backups themselves, according to Interfax. Yandex also said customers who had used its backup tools retained their data, Meduza reported.

Why a separate copy matters

Enabling a cloud service’s backup tool and keeping another copy outside a single provider or location are different ways to protect data. In the r/DataHoarder discussion of the incident, commenters recommended keeping multiple copies on separate media and in geographically separate places (community discussion). For important files, treating a provider’s backup setting as one layer—not the entire backup plan—is a practical extension of that advice.

If a file is irreplaceable, don’t make one provider’s backup setting your entire backup plan.