Yandex Cloud incident

The problem is with Virtual Private Cloud services

Minor Resolved View vendor source →

Yandex Cloud experienced a minor incident on May 22, 2026 affecting Compute Cloud and Managed Service for Apache Kafka® and 1 more component, lasting 5h 4m. The incident has been resolved; the full update timeline is below.

Started
May 22, 2026, 09:21 AM UTC
Resolved
May 22, 2026, 02:26 PM UTC
Duration
5h 4m
Detected by Pingoru
May 22, 2026, 09:21 AM UTC

Affected components

Compute CloudManaged Service for Apache Kafka®Managed Service for Apache Spark™Managed Service for ClickHouse®Managed Service for GitLabManaged Service for Kubernetes®Managed Service for MySQL®Managed Service for OpenSearchManaged Service for PostgreSQLManaged Service for Prometheus®

Update timeline

  1. investigating May 22, 2026, 09:22 AM UTC

    We are experiencing delays in processing operations for creating and managing virtual machines. This may affect the creation time of resources in Compute Cloud, Managed Service for Kubernetes, as well as managed databases (MySQL, PostgreSQL, ClickHouse, and others).

  2. identified May 22, 2026, 11:06 AM UTC

    Due to ongoing restoration work, operations to create and manage resources in the Compute Cloud service are temporarily unavailable. This makes it impossible to create and modify resources in dependent services: Managed Service for Kubernetes, Managed Service for MySQL, Managed Service for PostgreSQL and other managed databases. Existing previously created resources continue to work.

  3. identified May 22, 2026, 11:59 AM UTC

    We have restored access to operations. Currently, there may be slight delays in processing.

  4. resolved May 22, 2026, 02:37 PM UTC

    The services have been fully restored.