[BHS5][Storage] - Ceph volumes incident notification

Summary

[BHS5][Storage] - Ceph volumes incident notification

We are pleased to inform you that the incident affecting our Storage offering has been resolved. <b>Start time :</b> 05/08/2026 17:00 UTC <b>End time :</b> 06/08/2026 13:05 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.

• Started

  Aug 5, 2026 · 5:32 PM

• Resolved

  Aug 6, 2026 · 1:08 PM

• Duration

  19h 36m

• Severity

  Minor

• ◆

  Identified

  Aug 5 · 5:32 PM OVHcloud

  We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Storage offer on the specific BHS5 region. Here are some supplementary details : <b>Start time :</b> 05/08/2026 17:00 UTC <b>Impacted Service(s) :</b> Some Ceph volumes are experiencing temporary performance degradation in this region. <b>Customers Impact :</b> Customers may experience performance degradation and reduced data redundancy. <b>Root Cause :</b> A service disruption occurred due to an unexpected underlying infrastructure malfunction. We thank you for your understanding and patience throughout this incident.

• ◆

  Identified

  Aug 6 · 12:15 PM OVHcloud

  We have new information regarding the incident that affected your service(s). Please find below an update on the situation: <b>Update : </b> Our teams are still working to solve the incident. <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.

• ✓

  Resolved

  Aug 6 · 1:08 PM OVHcloud

  We are pleased to inform you that the incident affecting our Storage offering has been resolved. <b>Start time :</b> 05/08/2026 17:00 UTC <b>End time :</b> 06/08/2026 13:05 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.