Public Cloud incident

[BHS1/3][Compute - Instance] - Some instances incident notification

Major Resolved View vendor source →

Public Cloud experienced a major incident on March 31, 2026 affecting BHS1 and BHS3, lasting 43m. The incident has been resolved; the full update timeline is below.

Started
Mar 31, 2026, 02:24 PM UTC
Resolved
Mar 31, 2026, 03:07 PM UTC
Duration
43m
Detected by Pingoru
Mar 31, 2026, 02:24 PM UTC

Affected components

BHS1BHS3

Update timeline

  1. identified Mar 31, 2026, 02:24 PM UTC

    We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Compute - Instance offer in the specific regions. Here are some supplementary details : Start time : 30/03/2026 13:58 UTC Impacted Service(s) : Some instances in BHS1 and BHS3 are temporarily unreachable. Customers Impact : Some customers are temporarily unable to access and use their instances 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. resolved Mar 31, 2026, 03:07 PM UTC

    We are pleased to inform you that the incident affecting our Compute - Instance in BHS1 and BHS3 regions has been resolved. Start time : 31/03/2026 13:58 UTC End time : 31/03/2026 15:00 UTC Root Cause : A service disruption occurred due to an unexpected underlying infrastructure malfunction. We apologize for any inconvenience caused and appreciate your understanding.