Yandex Cloud incident

The issue with network connectivity in the ru-central1-b zone.

Minor Resolved View vendor source →

Yandex Cloud experienced a minor incident on February 11, 2025 affecting Virtual Private Cloud and ru-central1-b, lasting 55m. The incident has been resolved; the full update timeline is below.

Started
Feb 11, 2025, 03:35 PM UTC
Resolved
Feb 11, 2025, 04:30 PM UTC
Duration
55m
Detected by Pingoru
Feb 11, 2025, 03:35 PM UTC

Affected components

Virtual Private Cloudru-central1-b

Update timeline

  1. investigating Feb 11, 2025, 04:04 PM UTC

    We have noticed a network connectivity issue in the ru-central1-b zone. Colleagues are already working on resolving the problem.

  2. identified Feb 11, 2025, 04:13 PM UTC

    Since 18:47, network issues are no longer occurring. At the moment, all services are operating normally. The team is investigating the causes and continues to monitor the situation.

  3. identified Feb 11, 2025, 04:20 PM UTC

    All Cloud services are functioning correctly. Virtual machines are being created with some delay.

  4. identified Feb 11, 2025, 04:44 PM UTC

    Until 19:30 in zone ru-central1-a and until 19:23 in zone ru-central1-b, there might have been delays in connecting the virtual network when creating new virtual machines.

  5. resolved Feb 11, 2025, 04:46 PM UTC

    All Cloud services are operating in standard mode. The impact on network connectivity unavailability occurred between 18:40 and 18:47.