Wasabi outage, 16 July 2025

System Errors in EU-CENTRAL-1

Started
Resolved
16 Jul 2025, 10:51 UTC (after 2 h 3 min)
Impact
Minor
Affected
EU-Central-1 (Amsterdam)

Last update from Wasabi

On 16 July 2025 from 07:35 UTC to approximately 9:14 UTC, Wasabi's eu-central-1 \(Amsterdam\) region began to see degraded performance for some customers as multiple internal storage services went offline, resulting in elevated HTTP 5XX error responses for GET requests to their bucket\(s\). The cause for this degradation was an internal service restart, which failed to initialize all dependent services during the restart process. Due to this internal service failure, the internal connection to some storage subsystems was lost. Wasabi's Operations team was able to restart the failed initialization on all impacted servers to restore the S3 service to a fully operational state. By 9:14 UTC, all...

30 Jul 2025, 12:07 UTC

Read the full incident on the official Wasabi status page

Is Wasabi down now?

This page is the record of one past incident. For the live status, see Is Wasabi down right now? - it reads the official status page every 2 minutes.

Other Wasabi incidents

  1. System Errors in AP-SOUTHEAST-1

  2. Intermittent Wasabi Console Access

  3. WACM reporting 0% storage utilization for subaccounts

  4. System Errors in US-EAST-1

  5. System Errors in EU-CENTRAL-2

  6. Intermittent Wasabi Console Access - Singapore (ap-southeast-1)

  7. Wasabi Management Console network errors

  8. System Errors in AP-NORTHEAST-2

All recorded Wasabi incidents