- Level
- confirmed
- Worst impact
- Degraded
- Components
- EU-Central-1 (Amsterdam)
- Regions
- eu, eu-central-1
- Down Index
- 27of 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 2h 4m it lasted.
Anything that failed between 2025-07-16 08:47 UTC and 2025-07-16 10:51 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 4
- 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.
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 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.
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-62eebf5464
Is Wasabi still down?
No, this incident was resolved 2025-07-16 10:51 UTC. For Wasabi's live state, see https://down.guide/wasabi.
How long did it last?
2h 4m, from 2025-07-16 08:47 UTC to 2025-07-16 10:51 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.