Yandex Cloud incident

Incorrect charge of funds.

Major Resolved View vendor source →

Yandex Cloud experienced a major incident on June 5, 2026 affecting Yandex Cloud Billing and ru-central1-a and 1 more component, lasting 8h 30m. The incident has been resolved; the full update timeline is below.

Started
Jun 05, 2026, 12:25 PM UTC
Resolved
Jun 05, 2026, 08:55 PM UTC
Duration
8h 30m
Detected by Pingoru
Jun 05, 2026, 12:25 PM UTC

Affected components

Yandex Cloud Billingru-central1-aru-central1-bru-central1-dru-central1-e

Update timeline

  1. investigating Jun 05, 2026, 01:13 PM UTC

    An error was found in calculating charges for some of the resources. Billing processing has been temporarily stopped to prevent incorrect charges. After the cause is eliminated, the necessary accrual adjustments will be made. No additional user actions are required.

  2. identified Jun 05, 2026, 01:42 PM UTC

    The team is engaged in unblocking previously stopped resources. As soon as availability is restored, users will need to manually launch these resources. We will inform you about the completion of the process additionally.

  3. identified Jun 05, 2026, 02:56 PM UTC

    Most of the clouds that were mistakenly blocked earlier have already been restored, and users will need to manually start the stopped resources themselves. The team is also working on unblocking mistakenly blocked billing accounts and displaying the details correctly; we expect the details to start displaying correctly by the end of the day.

  4. identified Jun 05, 2026, 03:12 PM UTC

    All cloud accounts and billing accounts that were mistakenly blocked have now been unblocked. We ask users to manually restart any resources that should be active. We are also continuing to work on restoring the correct display of billing details and expect it to be displayed correctly by the end of the day. Separately, the team is handling erroneous charges: lists of affected cases are currently being compiled, and refunds will be issued shortly. We will provide an additional update on this matter.

  5. identified Jun 05, 2026, 03:34 PM UTC

    We have already started processing refunds; the actual time it takes for the funds to be credited may depend on the card-issuing bank.

  6. identified Jun 05, 2026, 04:02 PM UTC

    The detail has been fixed. Erroneous charges have been canceled and no longer affect your personal account balance.

  7. identified Jun 05, 2026, 06:01 PM UTC

    We have refunded the funds that were mistakenly debited. The actual transfer of the refund may depend on the bank that issued the card.

  8. resolved Jun 05, 2026, 08:56 PM UTC

    The billing systems have been restored.