Public Cloud incident

[EU/CA][Storage] - Object Storage S3 incident notification

Major Resolved View vendor source →

Public Cloud experienced a major incident on October 7, 2026 affecting BHS and GRA and 1 more component, lasting 50m. The incident has been resolved; the full update timeline is below.

Started
Oct 07, 2026, 01:11 PM UTC
Resolved
Oct 07, 2026, 02:02 PM UTC
Duration
50m
Detected by Pingoru
Oct 07, 2026, 01:11 PM UTC

Affected components

BHSGRADERBXSBGSGPSYDWAWYYZLIM

Update timeline

  1. investigating Oct 07, 2026, 01:11 PM UTC

    We are currently investigating an incident affecting our Storage offering, which is causing temporary availability issue in the EU and CA regions. Here are some supplementary details : Start time : 07/10/2026 09:24 UTC Impacted Service(s) : For these regions, you might have issues to access your S3 buckets and objects. Your compute and volume services already running are not impacted. Customers Impact : Customers are temporarily facing 503/500 errors when trying to access their S3 buckets and objects. Ongoing Actions : Our teams are investigating to determine the origin of the incident and fix it. We will keep you updated on the progress and resolution. We apologize for any inconvenience caused and appreciate your understanding.

  2. monitoring Oct 07, 2026, 01:43 PM UTC

    Service has been fully restored since 07/10/2026 13:41 UTC. Monitoring remains active to ensure long-term stability. Here are some supplementary details : Start time : 07/10/2026 12:36 UTC Impacted Service(s) : No more issue observed for Object Storage S3. Customers Impact : Customers are no longer facing 503/500 errors when trying to access their S3 buckets and objects We apologize for any inconvenience caused and appreciate your understanding.

  3. resolved Oct 07, 2026, 02:02 PM UTC

    We are pleased to inform you that the incident affecting our Object Storage S3 offering has been resolved. Start time : 07/10/2026 12:36 UTC End time : 07/10/2026 13:41 UTC Root Cause : A service disruption occurred due to an unexpected underlying infrastructure malfunction. We apologize for any inconvenience caused and appreciate your understanding.