Skip to content
OutageDeck

Incident detail

[SBG5][Storage] - Block storage incident notification

[SBG5][Storage] - Block storage incident notification

Resolved incidentMinor0 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 in SBG5. Please find the details of this incident below : <b>Start time :</b> 10/06/2026 00:50 UTC <b>Impacted Service(s) :</b> Block storage service is experiencing degraded performance. <b>Customers Impact :</b> Customers may experience increased latency, slower response times, or intermittent errors when accessing or managing data stored on the affected Block Storage. <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. Monitoring

    Service has been fully restored since 10/06/2026 01:26 UTC. Monitoring remains active to ensure long-term stability. Here are some supplementary details : <b>Start time :</b> 10/06/2026 00:50 UTC <b>Impacted Service(s) :</b> Block Storage service experienced degraded performance. <b>Customers Impact :</b> Customers may have experienced increased latency, slower response times, or intermittent errors when accessing or managing data stored on the affected Block Storage. We apologize for any inconvenience caused and appreciate your understanding.

  3. Resolved

    We are pleased to inform you that the incident affecting our Block storage offering has been resolved. <b>Start time :</b> 10/06/2026 00:50 UTC <b>End time :</b> 10/06/2026 07:10 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.