- Level
- confirmed
- Worst impact
- Degraded
- Components
- Wasabi Custom Cloud Console
- Down Index
- 18of 100
What to do
Check whether you use Wasabi Wasabi Custom Cloud 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 46m it lasted.
Anything that failed between 2025-10-23 14:13 UTC and 2025-10-23 15: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 4
- investigating
Customers attempting to log in to their Custom Cloud Console may receive a login error. We will update this page as we have more information.
provider
- identified
The login issue with Custom Cloud Console has been identified and fixed.
provider
- monitoring
Custom Cloud Console is now fully operational and being monitored by our Operations team.
provider
- resolved
The login issue with Custom Cloud Console 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-d4a45614cb
Is Wasabi still down?
No, this incident was resolved 2025-10-23 15:00 UTC. For Wasabi's live state, see https://down.guide/wasabi.
How long did it last?
46m, from 2025-10-23 14:13 UTC to 2025-10-23 15:00 UTC, by the times Wasabi posted.
What was affected?
Wasabi named Wasabi Custom Cloud 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.