Yandex Data Center Outage Disrupts Access to Cloud Files Following Drone Attack
Drone strikes damaged three Yandex data centers in Russia, disrupting cloud files and Yandex Cloud.
Yandex said drone strikes damaged three Russian data centers between October 7 and 11, 2026. The Sasovo site and the Vladimir site stopped operating, while Kaluga lost part of its infrastructure; no injuries were reported. Yandex Disk users saw failed downloads and HTTP 302, 500, and 504 errors, and Yandex Cloud ran in emergency mode with partial compute, AI Studio, and security services and Monium offline. The company gave no restoration timeline, urged alternate disaster-recovery plans, and reporting did not establish malware, stolen credentials, or unauthorized access.
- Sasovo, Kaluga, and Vladimir sites were struck between October 7 and 11, 2026.
- Sasovo and Vladimir stopped operating; Kaluga lost part of its infrastructure.
- Yandex Disk downloads failed; Yandex Cloud ran in emergency mode.
- No injuries were reported, and permanent file loss was not confirmed.
- Yandex told customers to use alternate disaster-recovery plans.
Full article518 words · extracted from cybersecuritynews.com · click to collapse
Yandex has confirmed a major service outage after drone attacks damaged three data centers in Russia, leaving some users unable to access cloud files. Two facilities stopped operating, while a third lost part of its infrastructure. The disruption affected Yandex Disk users and businesses running services on Yandex Cloud across the platform.
The first attack hit the Sasovo data center during the night of October 7 to 8, 2026. Yandex said the site suffered serious damage and stopped operating completely. Another attack struck its Kaluga facility on October 9, disabling part of the infrastructure. A third attack hit Vladimir overnight on October 11 and halted operations there.
Yandex reported no injuries across the three incidents. Emergency teams and company specialists were working at the damaged sites. In its statement, the company said engineers were working day and night to keep services running, but assessing the equipment remained difficult. It could not provide a reliable restoration timeline.
Cloud Files Become Unavailable
The outage has exposed problems beyond simply opening an application. That one Yandex Disk customer experienced missing thumbnails and failed downloads of previously uploaded files, with problems beginning on October 8. The customer also reported HTTP 302 redirects, HTTP 504 Gateway Timeout errors, and HTTP 500 errors while accessing files.
These reports show that some stored content could not be retrieved through normal service requests. However, failed downloads do not establish that files have been deleted. Whether any customer data has been permanently lost remains unclear, and Yandex had not addressed that question in the status updates cited by BleepingComputer.
The impact also extended to business cloud tools. The report said Yandex Cloud’s console, API, identity management, container registry, databases, S3 storage, and Kubernetes were available with some performance or availability issues. Compute, AI Studio, and security services were only partly available, while Monium remained offline. Those conditions reflected the latest update cited in the October 12 report, not a guarantee of current availability.
Yandex described its remaining cloud resources as unstable and said the platform was operating in emergency mode. It urged customers to use alternative disaster recovery plans and warned that technical support channels could also be unstable.
The incident concerns physical damage to hosting infrastructure. The available reporting does not establish a malware infection, stolen credentials, or unauthorized access to customer files.
Related coverage of a Microsoft data center power outage and the AWS outage linked to DNS problems shows how infrastructure failures can interrupt services far beyond the original fault.
For affected organizations, Yandex’s warning makes recovery planning urgent. Access to another working environment matters while damaged facilities remain offline. The immediate unanswered questions are when full service will return and whether all affected files can be recovered.
Cut every SOC alert investigation by 21 min. Power your SOC with instant IOC context for immediate response: Integrate TI Lookup into your SOC
Guru Baranhttps://cybersecuritynews.com
Gurubaran KS is a cybersecurity analyst, and Journalist with a strong focus on emerging threats and digital defense strategies. He is the Co-Founder and Editor-in-Chief of Cyber Security News, where he leads editorial coverage on global cybersecurity developments.