Skip to content
OutageDeck

Incident detail

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

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

Resolved incidentMajor0 affected services

Timeline window

to

Timeline

Incident updates

Updates are normalized from the official source chronology so timeline changes remain easy to scan.

  1. Identified

    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 : <b>Start time :</b> 28/05/2026 08:00 UTC <b>Impacted Service(s) :</b> Some instances in the GRA5 / GRA7 / GRA9 / GRA11 regions are unreachable. <b>Customers Impact :</b> Some customers are temporarily unable to access instances located in the specified regions. <b>Root Cause :</b> A service disruption occurred due to an unexpected underlying infrastructure malfunction. <b>Ongoing Actions :</b> 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

    We have new information regarding the incident that affected your service(s). Please find below an update on the situation: <b>Update : </b> Some instances in the GRA5 / GRA7 / GRA9 / GRA11 regions remain temporarily unavailable. <b>Ongoing Actions :</b> 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

    <b>Ongoing Actions :</b> 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

    Please find an update of this incident below: <b>Ongoing Actions :</b> 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

    We have new information regarding the incident that affected your service(s). Please find below an update on the situation: <b>Update : </b> The configuration of private networks on some instances is temporarily unavailable since 28/05/2026 15:00 UTC. <b>Ongoing Actions :</b> 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

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