Yandex Cloud incident

Problems with network connectivity in the ru-central1-d zone

Minor Resolved View vendor source →

Yandex Cloud experienced a minor incident on January 26, 2025 affecting Virtual Private Cloud and ru-central1-d, lasting 11h 15m. The incident has been resolved; the full update timeline is below.

Started
Jan 26, 2025, 07:45 AM UTC
Resolved
Jan 26, 2025, 07:00 PM UTC
Duration
11h 15m
Detected by Pingoru
Jan 26, 2025, 07:45 AM UTC

Affected components

Virtual Private Cloudru-central1-d

Update timeline

  1. investigating Jan 26, 2025, 08:44 AM UTC

    We noticed problems with network connectivity in the ru-central 1-d availability zone. The developers are already aware of it and are fixing it.

  2. identified Jan 26, 2025, 09:03 AM UTC

    The network channel ru-central1-d – ru-central1-b was cut off, resulting in increased transmission. According to our data: • +50ms ru-central1-d – ru-central1-a • +100ms ru-central1-d – ru-central1-b

  3. identified Jan 26, 2025, 09:13 AM UTC

    A new route has been introduced, latensi by zones: • 5.3ms ru-central1-d – ru-central1-a • 9.3ms ru-central1-d – ru-central1-b

  4. resolved Jan 27, 2025, 04:44 AM UTC

    As of January 26, 2025, 19:00 UTC, the service team has completed the maintenance. We are not observing any deviations in the service operation.