Skip to content
OutageDeck

Incident detail

[BHS1][Storage] - Block Storage incident notification

[BHS1][Storage] - Block Storage 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 Block Storage offer on the specific region BHS1. Here are some supplementary details : <b>Start time :</b> 29/06/2026 14:07 UTC <b>Impacted Service(s) :</b> The block storage service is temporarily unavailable for some customers in BHS1 region. <b>Customers Impact :</b> Some customers are unable to access and use their block storage loacted in the specified region. <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> The majority of the block storage hosts in BHS1 region are no longer impacted by this incident. <b>Ongoing Actions :</b> Our teams are currently working on the last impacted block storage hosts. We will keep you updated on the progress and resolution. We apologize for any inconvenience caused and appreciate your understanding.

  3. Identified

    We have new information regarding the incident that affected your service(s). Please find below an update on the situation: <b>Update : </b> Customers are now able to access their block storage and normal operations have largely resumed. <b>Ongoing Actions :</b> Our teams are continuing to work on the remaining block storage hosts that were impacted by this incident. As this work is ongoing, customers may experience some temporary degradation in performance. We will keep you updated on the progress and full resolution. We apologize for any inconvenience caused and appreciate your understanding.

  4. Identified

    We have new information regarding the incident that affected your service(s). Please find below an update on the situation: <b>Impacted Service(s) :</b> The block storage service was again unavailable for some customers in BHS1 region between 29/06/2026 17:00 UTC and 29/06/2026 18:00 UTC. <b>Ongoing Actions :</b> Our teams are continuing to work on the remaining block storage hosts that were impacted by this incident. As this work is ongoing, customers may experience some temporary degradation in performance. We will keep you updated on the progress and resolution. We apologize for any inconvenience caused and appreciate your understanding.

  5. Resolved

    We are pleased to inform you that the incident affecting our Block Storage offering in BHS1 region has been resolved. <b>Start time :</b> 29/06/2026 14:07 UTC <b>End time :</b> 29/06/2026 18:40 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.