- Level
- confirmed
- Worst impact
- Degraded
- Components
- EU-Central-2 (Frankfurt)
- Regions
- eu, eu-central-2
- Down Index
- 30of 100
What to do
Check whether you use Wasabi EU-Central-2 (Frankfurt) in eu, eu-central-2. 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 6h 22m it lasted.
Anything that failed between 2025-07-08 12:28 UTC and 2025-07-08 18:50 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 6
- investigating
We are currently experiencing system errors in our EU-CENTRAL-2 (Frankfurt) 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
- identified
Our Operations Team is working to restore services in the region. Customers may continue to experience HTTP 5XX error responses when interacting with their Wasabi bucket(s) at this time.
provider
- identified
We are continuing to work on restoring service in the region. Some customers may continue to experience HTTP 5XX error responses when interacting with their Wasabi bucket(s) at this time.
provider
- monitoring
Our EU-CENTRAL-2 region is now fully operational, and we will continue to monitor the service. For any questions or concerns, please reach out to our Support Team at support@wasabi.com
provider
- resolved
This incident has been resolved.
provider
- postmortem
On 08 July 2025 from 12:10 UTC to approximately 16:36 UTC, Wasabi S3 services in our Frankfurt \(eu-central-2\) region were unavailable due to a partial power issue in our datacenter. Wasabi’s Operations Team was alerted by our automated alert system that multiple racks were experiencing power issues, however not all racks within the datacenter were impacted due to the power issue not impacting all circuits within the building. While our Operations Team was working to bring up all server hardware and running system checks and diagnostics, a second power issue at 16:18 UTC caused all impacted racks to go offline a second time. By 16:36 UTC, our Operations Team was able to successfully bring up all impacted racks to a fully operational state.
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-a31627d409
Is Wasabi still down?
No, this incident was resolved 2025-07-08 18:50 UTC. For Wasabi's live state, see https://down.guide/wasabi.
How long did it last?
6h 22m, from 2025-07-08 12:28 UTC to 2025-07-08 18:50 UTC, by the times Wasabi posted.
What was affected?
Wasabi named EU-Central-2 (Frankfurt) in eu, eu-central-2.
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.