Yandex Cloud incident
Power failure in the ru-central-b availability zone
Yandex Cloud is currently experiencing a major incident affecting API Gateway and Application Load Balancer and 1 more component, which began 5d ago. The vendor's full update timeline is below.
Affected components
Update timeline
- investigating Oct 07, 2026, 10:31 PM UTC
Power outages are observed in the ru-central1-b availability zone. The team is working to fix the problem. If possible, we recommend shifting the load to other availability zones. We will keep you informed of the progress of the work.
- identified Oct 07, 2026, 11:19 PM UTC
We have taken measures to localize the problem in the ru-central1-b availability zone. The situation has not stabilized yet — the team continues to find out the reasons and work on recovery. We will share updated information in the near future.
- identified Oct 08, 2026, 01:16 AM UTC
The Yandex Cloud team continues to work on eliminating the consequences of the incident. The recovery dates are being clarified — we will inform them as soon as confirmed information becomes available.
- identified Oct 08, 2026, 01:55 AM UTC
Due to the incident in the ru-central1-b availability zone, problems may arise in other zones when creating new VMs, k8s clusters, and databases. We are continuing to address the consequences of the incident and will report on the progress of the recovery.
- identified Oct 08, 2026, 05:26 AM UTC
The unavailability of the ru-central1-b zone remains for now, we have completed all the necessary work to switch the load to other availability zones. All services in the remaining zones are operating normally. Currently, the creation of new resources in the cloud infrastructure may be limited. If you have any questions, please contact technical support. Our specialists continue to work on eliminating the consequences of the incident. We will be back with an update before 15:00 Moscow time.
- identified Oct 08, 2026, 12:19 PM UTC
The ru-central1-b availability zone remains unavailable. The cause of the incident was a fire that occurred as a result of a UAV attack on the Yandex data center in Sasovo and affected part of the Yandex Cloud infrastructure. The data center has been completely shut down. Currently, the creation of new resources in the cloud infrastructure may be limited. Our team continues to work on eliminating the consequences of the incident. If you have any questions, please contact technical support. The next update will be published at 19:00 Moscow time.
- identified Oct 08, 2026, 03:25 PM UTC
The situation with the availability of the ru-central1-b zone has not changed yet. Our specialists are continuing the restoration work, however, according to current estimates, it will not be possible to resume the work of the zone in the near future. The recommendation remains the same, if possible, to use alternative plans to restore the services. The next update will be given at 23:00 Moscow time.
- identified Oct 08, 2026, 08:05 PM UTC
The availability of the ru-central1-b zone has not yet been restored. Our team continues to eliminate the consequences of the incident. If possible, we recommend using alternative service recovery options, including dedicated physical servers Bare Metal. The next update will be published on October 9 at 12:00 Moscow time.
- identified Oct 09, 2026, 07:38 AM UTC
The ru-central1-b zone is still unavailable. The other availability zones are working. Our specialists are working around the clock to restore the previous level of infrastructure redundancy for key services in the near future and ensure the availability of additional capacities and backup components. The technical support team helps customers to resume their services. We have also agreed with other cloud providers to speed up the placement and backup of your resources on their sites. If you see a need, you can contact your colleagues directly: • Selectel • K2Cloud • VK Cloud Using the code word "CloudBro”, our colleagues will be ready to process your application as a matter of priority and provide the necessary technical assistance together with our teams. If you need additional advice, please contact technical support or your account manager. The next update will be published at 15:00 Moscow time.
- identified Oct 09, 2026, 12:42 PM UTC
The ru-central1-b zone is unavailable. Our specialists continue to work to eliminate the consequences of the incident and restore cloud services. Current status for some services: • Managed Service for Kubernetes: it is now possible to transfer the management components of regional clusters from the ru-central1-b zone to other availability zones. To restore the applications, we recommend creating node groups in other zones and transferring the load to them. • Managed Databases: in fault-tolerant clusters, it is now possible to remove hosts from the ru-central1-b zone. After deleting them, cluster management operations will become available, including changing settings and adding users. • Yandex AI Studio: since yesterday, all models and components of the platform have been operating normally. At the same time, some features of DeepSeek models related to the size of the context window are preserved. Other AI services are also operating normally. If you have any questions or need help restoring resources, please contact technical support. The next update will be published at 22:00 Moscow time.
- identified Oct 09, 2026, 06:47 PM UTC
The situation with the availability of the ru-central1-b zone remains unchanged so far. Our engineers continue to work around the clock to eliminate the consequences of the incident and restore services. The next update will be given on October 10 at 12:00 Moscow time.
- identified Oct 10, 2026, 06:00 AM UTC
At the moment, the ru-central1-b zone remains unavailable. Our engineers continue to work to eliminate the consequences of the incident. To ensure stable operation of the cloud platform for the coming weekend, we are switching to fully manual management of quotas for computing resources and disks. • All users have access to a small additional amount of resources beyond those already used. This will allow some clients, if necessary, to restore resources from backups, including for their subsequent transfer to other sites, or perform other operations. • The creation of new resources beyond the limits set by us will be limited. • Priority in expansion will be given to those whose critical services are still not restored. If you have any questions, please contact technical support or your account manager. The next update will be given on October 10 at 20:00 Moscow time.
- identified Oct 10, 2026, 05:13 PM UTC
The ru-central1-b zone remains unavailable. In the morning, we switched to fully manual management of quotas for computing resources and disks. Technical support specialists sort out each situation manually, so responses may be delayed. We will try to sort out all quota requests as soon as possible. Our team continues to work around the clock to increase the amount of available computing resources. The next update will be given on October 11 at 12:00 Moscow time.