Public Cloud incident

[GRA5/7/9/11][Compute - Instance] - Some Instances Incident Notification

Major Resolved View vendor source →

Public Cloud experienced a major incident on May 28, 2026 affecting GRA5 and GRA7 and 1 more component, lasting 1d 3h. The incident has been resolved; the full update timeline is below.

Started
May 28, 2026, 10:14 AM UTC
Resolved
May 29, 2026, 01:21 PM UTC
Duration
1d 3h
Detected by Pingoru
May 28, 2026, 10:14 AM UTC

Affected components

GRA5GRA7GRA9GRA11

Update timeline

  1. identified May 28, 2026, 10:14 AM UTC

    We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Compute - Instance offer on the specific GRA5 / GRA7 / GRA9 / GRA11 regions. Here are some supplementary details : Start time : 28/05/2026 08:00 UTC Impacted Service(s) : Some instances in the GRA5 / GRA7 / GRA9 / GRA11 regions are unreachable. Customers Impact : Some customers are temporarily unable to access instances located in the specified regions. Root Cause : A service disruption occurred due to an unexpected underlying infrastructure malfunction. Ongoing Actions : The incident has been identified and our teams are mobilised to restore service as quickly as possible. We will keep you updated on the progress and resolution. We apologize for any inconvenience caused and appreciate your understanding.

  2. identified May 28, 2026, 12:30 PM UTC

    We have new information regarding the incident that affected your service(s). Please find below an update on the situation: Update : Some instances in the GRA5 / GRA7 / GRA9 / GRA11 regions remain temporarily unavailable. Ongoing Actions : The incident has been identified and our teams are mobilised to restore service as quickly as possible. We will keep you updated on the progress and resolution. We apologize for any inconvenience caused and appreciate your understanding.

  3. identified May 28, 2026, 03:10 PM UTC

    Ongoing Actions : Some instances are impacted by this incident. Our teams are currently performing checks and replacing components where necessary. We will keep you updated on the progress and final resolution. We apologize for any inconvenience caused and appreciate your understanding.

  4. identified May 28, 2026, 06:59 PM UTC

    Please find an update of this incident below: Ongoing Actions : Our teams are continuing to work on resolving this issue. We will keep you updated on the progress and final resolution. We apologize for any inconvenience caused and appreciate your understanding.

  5. identified May 28, 2026, 08:51 PM UTC

    We have new information regarding the incident that affected your service(s). Please find below an update on the situation: Update : The configuration of private networks on some instances is temporarily unavailable since 28/05/2026 15:00 UTC. Ongoing Actions : The incident has been identified and our teams are mobilised to restore service as quickly as possible. We will keep you updated on the progress and resolution. We apologize for any inconvenience caused and appreciate your understanding.

  6. resolved May 29, 2026, 01:21 PM UTC

    We are pleased to inform you that the incident affecting our Compute - Instance offering has been resolved. Start time : 28/05/2026 08:00 UTC End time : 29/05/2026 13:19 UTC Root Cause : A service disruption occurred due to an unexpected underlying infrastructure malfunction. We apologize for any inconvenience caused and appreciate your understanding.