- Level
- confirmed
- Worst impact
- Partial outage
- Regions
- eu, eu-central-2
- Down Index
- 26of 100
What to do
Check whether you use Wasabi 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 0m it lasted.
Anything that failed between 2026-08-04 14:20 UTC and 2026-08-04 07:30 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 1
- resolved
On 4 August 2026 from 07:36 UTC to 08:03 UTC, Wasabi S3 services in our Frankfurt (eu-central-2) region were unavailable due to a recent software update to our frontend infrastructure. Wasabi’s Operations Team was alerted by our automated monitoring systems to a drop on our ingestion traffic and started investigating. The updated was rolled back and services were fully restored on the region by 08:03 UTC.
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-34558965fe
Is Wasabi still down?
No, this incident was resolved 2026-08-04 07:30 UTC. For Wasabi's live state, see https://down.guide/wasabi.
How long did it last?
0m, from 2026-08-04 14:20 UTC to 2026-08-04 07:30 UTC, by the times Wasabi posted.
What was affected?
Wasabi named 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.