Yandex Cloud incident

Network unavailability for new VMs and DBM nodes.

Major Resolved View vendor source →

Yandex Cloud experienced a major incident on December 15, 2025 affecting Application Load Balancer and Compute Cloud and 1 more component, lasting 9h 20m. The incident has been resolved; the full update timeline is below.

Started
Dec 15, 2025, 04:09 PM UTC
Resolved
Dec 16, 2025, 01:30 AM UTC
Duration
9h 20m
Detected by Pingoru
Dec 15, 2025, 04:09 PM UTC

Affected components

Application Load BalancerCompute CloudData ProcessingData TransferDataSphereManaged Service for Apache Kafka®Managed Service for Apache Spark™Managed Service for ClickHouse®Managed Service for GitLabManaged Service for Kubernetes®

Update timeline

  1. investigating Dec 15, 2025, 04:09 PM UTC

    No new VMs or nodes are created in the ru-central1-a zone for database clusters. Colleagues are already correcting the situation.

  2. identified Dec 15, 2025, 04:56 PM UTC

    We noticed that some of the existing VMs in the ru-central1-a zone have lost network availability.

  3. identified Dec 15, 2025, 08:22 PM UTC

    The development team is testing a repair plan in a pre-production environment. We will be back with an update before 01:00 (+3).

  4. identified Dec 15, 2025, 10:02 PM UTC

    The development team completes testing of the repair plan and proceeds to apply it. We'll be back with an update before 03:00 (+3).

  5. identified Dec 15, 2025, 11:42 PM UTC

    During the restoration work, we observe temporary problems with external connectivity.

  6. identified Dec 16, 2025, 12:08 AM UTC

    we continue the restoration work, ETA 04:00 (+3).

  7. identified Dec 16, 2025, 01:03 AM UTC

    At 03:11, network connectivity was restored, and the team continues to work to mitigate the consequences of the incident.

  8. resolved Dec 16, 2025, 01:42 AM UTC

    At 04:30, the problems were solved. If you still have questions about cloud resources, please contact technical support.