- Level
- confirmed
- Worst impact
- Degraded
- Components
- Wasabi Management Console
- Regions
- us, us-east-1, us-east-2, us-west-1
- Down Index
- 35of 100
What to do
Check whether you use Wasabi Wasabi Management Console in us, us-east-1, us-east-2, us-west-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 1h 43m it lasted.
Anything that failed between 2026-10-06 07:08 UTC and 2026-10-06 08: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 2
- investigating
We are currently investigating some customers difficulty to access the Wasabi Console. As alternative try to use your region URL, example: console.us-east-1.wasabisys.com or console.us-east-2.wasabisys.com or console.us-west-1.wasabisys.com etc
provider
- resolved
This incident has been resolved
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-1b55db5669
Is Wasabi still down?
No, this incident was resolved 2026-10-06 08:51 UTC. For Wasabi's live state, see https://down.guide/wasabi.
How long did it last?
1h 43m, from 2026-10-06 07:08 UTC to 2026-10-06 08:51 UTC, by the times Wasabi posted.
What was affected?
Wasabi named Wasabi Management Console in us, us-east-1, us-east-2, us-west-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.