What happened
In a company news post dated 28 October 2026, Yandex said its engineers had restored access to 96% of the data stored on Yandex Disk. The figure covers documents, photographs, audio and video recordings, and other files. It is an aggregate measure: the company cautions that the share available to any particular user may differ. Some users have all their files back, while others are still missing some.
Yandex said it is distributing capacity across independent third-party sites and returning files gradually to support stable service operation. It expects more files to become available to users each day, but the post does not give a completion date or describe how the remaining data is prioritized. It also does not say whether availability differs by file age. The announcement presents recovery as ongoing rather than complete.
The service's basic functions are available, including uploading, downloading, and synchronization. The browser version still cannot download folders and albums or multiple files at once. Yandex advises users who need those operations to use the desktop Disk app or the API. The company says all capabilities are expected to return eventually, including in the mobile app, but gives no date for that restoration.
Yandex also said other Yandex 360 services are operating and that their main functions are available, with remaining capabilities being restored gradually. Yandex Disk is part of the Yandex 360 virtual office. The announcement directs users to a recovery progress page, but the supplied material does not include a more detailed restoration schedule, affected-user count, or technical account of the recovery process.
What the archive adds
This is a new recovery fact in a known disruption story, not a new incident. A prior Field Note, “Ukrainian drones shut down Yandex's Vladimir data center, the third hit in four days, disrupting Yandex Cloud and YandexGPT”, framed repeated facility disruption as a service-continuity risk. An earlier note on the Vladimir data-center shutdown covered the regional outage as a recovery-plan test.
Trend signal
The update supports the pattern that physical infrastructure concentration can become a continuity risk, and that recovery is operationally distinct from restoring a service's basic interface. The supplied pattern list has no directly matching pattern page, so this is a concrete example adjacent to earlier coverage rather than a link to a formal pattern.
Why now
The company published this update while access restoration was still underway. The 96% aggregate figure and explicit browser limitations help users distinguish between basic service availability and full recovery of their own files and workflows.
Connections to other events
An earlier Telegram post dated 10 October described damage to Yandex's Sasovo data center overnight on 7–8 October and disruption at the Kaluga facility on 9 October. The current company update adds a later user-facing measure of recovery for Disk; it does not independently detail the attacks or quantify their individual contribution to the remaining inaccessible data.
Why it matters
For teams using cloud storage as part of AI workflows, “the service is up” and “the required artifacts are available” are different operational states. A workflow may depend on retrieving a whole folder, a batch of files, or a synchronized local copy; the browser restrictions Yandex lists can therefore matter even while upload, download, and sync are functioning. The availability of desktop-app and API workarounds is useful, but teams should verify that those routes meet their own access and automation needs.
The 96% figure should not be treated as a guarantee that any particular account is 96% restored. Yandex explicitly says user-level availability varies. Teams with important datasets should check their own files and maintain recovery options that do not depend on a single provider or site. This announcement is a status update, not evidence of the full resilience or redundancy of Yandex's underlying infrastructure.
Limits and uncertainty
The company does not state how many users or files remain affected, how it calculates the 96% figure, or when recovery will be complete. It does not break the figure down by file type, region, or account, and it gives no explanation of which files are being restored first. The post also does not establish the precise cause of each remaining limitation or independently quantify the impact of attacks on specific data-center facilities. The browser restrictions and suggested alternatives are described as current, while full restoration is promised without a timeline.
Reader takeaway
Yandex reports substantial but incomplete recovery: 96% of Disk data is accessible in aggregate, while individual users may still lack files and browser bulk downloads remain unavailable. For operational planning, check actual account-level access rather than assuming the service-wide percentage describes your own recovery, and test the desktop app or API if a blocked browser operation is needed.
Open question
How long will Yandex take to restore the remaining files and browser capabilities, and will it publish account-level or service-level measures that make completion verifiable?