Yandex Disk Files Become Partially Inaccessible After Sasovo Data Center Incident

A detailed user report reveals that approximately one percent of files stored on Yandex Disk are currently unavailable for download following reported incidents at the Sasovo data center. The problems manifest in three distinct states: missing thumbnails with downloadable originals, visible thumbnails with inaccessible originals returning 504 Gateway Time-out errors, and cases where both thumbnails and originals fail to load. Technical analysis using curl requests traced the failures to specific storage nodes such as s418klg.storage.yandex.net, indicating that some data shards may reside in affected infrastructure while others remain operational. Yandex support requested original files for diagnosis but closed the ticket without providing an official explanation or confirming data integrity. The author emphasizes that the issue affects files across both the Photos and Files sections and recommends maintaining offline backups due to the lack of guaranteed availability during data center failures.

HabrTranslated from Russian

Read at source

A user investigating backup procedures after news of an incident at the Sasovo data center discovered that a portion of files on Yandex Disk had become inaccessible. The problems appeared in three separate states affecting both the Photos and Files sections of the service.

In the first state, thumbnails failed to load in the photo gallery while the original files remained downloadable. The user observed that the downloader service redirected requests to storage nodes that were still operational, suggesting that thumbnail generation infrastructure was impacted while primary data remained available.

The second and more concerning state showed visible thumbnails, yet attempts to download the originals resulted in 504 Gateway Time-out responses from nodes such as s418klg.storage.yandex.net. Detailed curl tracing confirmed that the downloader.disk.yandex.ru service issued redirects to affected storage hosts that subsequently timed out.

The third state combined both issues, with neither thumbnails nor originals accessible. The user estimated that roughly one percent of their stored data, totaling about 21 GB out of 1.9 TB, exhibited these symptoms as of the night of October 10.

Support requests submitted to Yandex, including screenshots and direct file links, were closed after the company asked for original copies of the affected files without offering further diagnosis or confirmation of data loss. The author advises all users to verify their own Yandex Disk contents and maintain at least one offline backup copy.

Meridian digestThe week's most consequential security stories, distilled into one briefing.See the digest

More in Other

Mail.ru Reduces Lifetime 1TB Cloud Storage Promo to Standard 8GB Quota for Select Users
Kimi K3 Open Model Surpasses Closed AI Leaders with Million-Token Context and 896 Experts
Innostage Completes Functional Testing of PT NGFW 1.10.3 Across 156 Criteria