- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 8of 100
What to do
Check whether your product depends on Wasabi. 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 2025-02-20 21:25 UTC and 2025-02-19 09:00 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
From 09:00 to 11:00 UTC on 19 February 2025, visitors experienced HTTP 5XX errors when attempting to view our Wasabi.com website. These errors were caused by an update to the site, which resulted in multiple modules not loading properly. Once the issue was identified, the changes were reverted, and the website was fully operational around 11:00 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-1fb209d3f6
Is Wasabi still down?
No, this incident was resolved 2025-02-19 09:00 UTC. For Wasabi's live state, see https://down.guide/wasabi.
How long did it last?
0m, from 2025-02-20 21:25 UTC to 2025-02-19 09:00 UTC, by the times Wasabi posted.
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.