- Level
- confirmed
- Worst impact
- Degraded
- Components
- Wasabi Management Console
- Down Index
- 19of 100
What to do
Check whether you use Wasabi Wasabi Management Console. 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 1h 31m it lasted.
Anything that failed between 2025-11-20 02:35 UTC and 2025-11-20 04:06 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 investigating issues regarding Wasabi Console access. Some customers were facing timeout or webpage taking a long time to load.
provider
- investigating
We are continuing to investigate this issue.
provider
- monitoring
Our team had identified the issue and the Wasabi Management Console access is back to normal. We will continue to monitoring the System status.
provider
- resolved
Management Console Access is restored to Operational Status
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-4103b71847
Is Wasabi still down?
No, this incident was resolved 2025-11-20 04:06 UTC. For Wasabi's live state, see https://down.guide/wasabi.
How long did it last?
1h 31m, from 2025-11-20 02:35 UTC to 2025-11-20 04:06 UTC, by the times Wasabi posted.
What was affected?
Wasabi named Wasabi Management Console.
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.