Yandex Blocks Some 360 and Disk Features After Drone Attack on Third Data Center

Yandex has restricted some key features of its Yandex 360 platform and its Disk cloud storage. The trigger was a drone attack on the company's third data center. RBC reports that management made the emergency decision to protect its IT infrastructure from critical overload. The available materials contain no list of disabled features and no data on physical damage, so some of the conclusions below remain working hypotheses.

What is known so far

There are few facts, and they fit in a short list:

• Affected products: Yandex 360 (the company's workspace platform) and the Disk cloud storage.
• Nature of the measures: a block on some key features, not a full shutdown of the services.
• Motive: to prevent critical overload of the infrastructure.
• Source: RBC, as retold by Hi-Tech on 12 October 2026.
• Incident count: the headline refers to the third data center, which means this is not an isolated episode.

It is not disclosed how much capacity went offline, whether data replication was disrupted, or when the restrictions will be lifted.

Why overload is as dangerous as the strike itself

When part of the capacity drops out, the load shifts to the surviving sites. Clients do not sit quietly while this happens. Apps retry failed requests, Disk desktop clients try to sync files, and mail and office services hammer the same backends. The result is an avalanche that can bring down even untouched nodes.

That is why engineers use load shedding: they deliberately switch off the least critical and most expensive features to preserve basic functionality. Heavy background operations usually get cut first, such as bulk synchronization, preview generation, indexing, or large uploads. This is common industry practice. In the materials cited, the company does not say which features Yandex actually disabled.

For storage, the stakes are higher. If some replicas were hit, the system spends resources restoring data redundancy, and every extra user request takes those resources away from the most critical task: keeping files safe. In this mode, restricting features looks more like a precaution for the data than an inconvenience for users.

What is still missing for the full picture

The main questions remain open. How many sites were hit, and what share of total capacity do they represent? Are cloud services for business customers affected, or only consumer products? Does the company have backup regions with enough spare capacity to take over fully? If the headline is accurate, a third incident turns the question from a one-off failure into a design problem: physical protection and geographic distribution of data centers become as much a part of the architecture as redundant power.

It is also worth watching how the squeeze on capacity affects the company's other workloads, including cloud and ML services on shared sites. There is no direct confirmation of this, but when compute is scarce, priorities inevitably get reshuffled.

What users and companies should do

Until Yandex publishes details, it makes sense to stick to basic hygiene:

• Make a local or external copy of your critical Disk files if sync still works. Do not start a bulk export of everything: that would add load to the system.
• Check which business processes depend on Yandex 360: calendar, mail, shared documents. Prepare fallback communication channels for your team.
• Review your SLA terms and compensation procedures if you use the services under a corporate contract.
• Follow the company's official announcements: they will determine when, and in what order, the features come back.

For IT leaders, the lesson is practical: a single cloud dependency without a degradation plan becomes a single point of failure, even if the provider has several data centers.