- Level
- confirmed
- Worst impact
- Degraded
- Components
- EU-Central-1 (Amsterdam)
- Regions
- eu, eu-central-1
- Down Index
- 28of 100
What to do
Check whether you use Wasabi EU-Central-1 (Amsterdam) in eu, eu-central-1. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 3h 57m it lasted.
Anything that failed between 2025-04-04 10:01 UTC and 2025-04-04 13:59 UTC may need a replay.Subscribe to Wasabi's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=wasabi works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Wasabi 5
- investigating
We are currently investigating system errors in our EU-CENTRAL-1 region. Our team is working to isolate the issue and provide a resolution.
provider
- investigating
We are continuing to investigate this issue.
provider
- 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.
provider
- resolved
This incident has been resolved.
provider
- postmortem
On 04 April 2025 from 06:20 UTC to 12:20 UTC, we experienced system errors in our eu-central-1 \(Amsterdam\) region. This issue affected the S3 service and impacted customer’s ability to read and write to/from their Wasabi buckets within the region. Starting at 05:11 UTC, our Operations Team was notified of a spike in internal system read operations in our eu-central-1 region across multiple storage zones. Approximately 1 hour and 9 minutes after this spike at 06:20 UTC, our storage sub-systems errored to read and write requests, impacting customers. Wasabi’s Operations Team was able to identify a recent upgrade to our internal system as responsible for the spike in storage read operations, that eventually led to the storage system errors. Operations proceeded to rollback this upgrade to a previous stable release, which then restored operations on the storage system, leading to a restoration of service for customers. By 12:20 UTC, all S3 services in the eu-central-1 region were operational.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-1e8c6b9c8d
Is Wasabi still down?
No, this incident was resolved 2025-04-04 13:59 UTC. For Wasabi's live state, see https://down.guide/wasabi.
How long did it last?
3h 57m, from 2025-04-04 10:01 UTC to 2025-04-04 13:59 UTC, by the times Wasabi posted.
What was affected?
Wasabi named EU-Central-1 (Amsterdam) in eu, eu-central-1.
What caused it?
Wasabi hasn't published a root cause. If it does, it shows here.
Where does this come from?
Wasabi's official status page, https://status.wasabi.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.