Yandex Cloud incident

Partial network resources unavailability in ru-central1-b

Minor Resolved View vendor source →

Yandex Cloud experienced a minor incident on July 14, 2022 affecting Virtual Private Cloud and ru-central1-b, lasting 9h 55m. The incident has been resolved; the full update timeline is below.

Started
Jul 14, 2022, 02:47 AM UTC
Resolved
Jul 14, 2022, 12:42 PM UTC
Duration
9h 55m
Detected by Pingoru
Jul 14, 2022, 02:47 AM UTC

Affected components

Virtual Private Cloudru-central1-b

Update timeline

  1. investigating Jul 14, 2022, 06:14 AM UTC

    We noticed some problems with network availability in ru-central1-b zone. Some users may not be able to access some recourses. The developer team is notified and currently investigating this issue.

  2. identified Jul 14, 2022, 09:04 AM UTC

    We have localized the problem and are working to fix it. At this point in time, problems with external connectivity are possible for a limited proportion of network flows. We recommend removing the workload from the ru-central-1b zone to the other two zones, as regressions are possible. We have raised the unavailability level of the incident to unavailable.

  3. identified Jul 14, 2022, 11:13 AM UTC

    At 13:30 Moscow time, the problem was fixed. We continue to monitor the situation.

  4. identified Jul 14, 2022, 12:03 PM UTC

    At 14:16 Moscow time, the level of unavailability was reduced. We are not closing the incident. We continue to work to eliminate the consequences.

  5. resolved Jul 14, 2022, 01:53 PM UTC

    At 15:42 Moscow time, the work on fixing the problem was completed. We are investigating the causes of its occurrence.

  6. postmortem Jul 20, 2022, 01:50 PM UTC

    Incident report is coming soonIncident report is coming soon