Companies / Wasabi / incidents
Wasabi: System Errors in EU-CENTRAL-1
Affected components: EU-Central-1 (Amsterdam)
Timeline of updates
- investigating
We are currently experiencing system errors in our EU-CENTRAL-1 region. Customers may experience elevated HTTP 5XX error responses when interacting with their Wasabi bucket(s). We will update this page as we have more information.
- monitoring
We have identified and resolved the issue. All affected resources are back in service. We are currently monitoring the status. If you see any error, please reach out to support@wasabi.com for assistance.
- resolved
This incident has been resolved.
- postmortem
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 services in the eu-central-1 region were running properly.
Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab). Wasabi profile · Recent Wasabi incidents · Markdown · JSON