- 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 2024-12-01 23:41 UTC and 2024-12-01 23:41 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
We experienced an issue that interrupted services for a brief period at 23:41 UTC on December 1, 2024. The system config was adjusted and service resumed at approximately 23:51 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-27e842c407
Is Wasabi still down?
No, this incident was resolved 2024-12-01 23:41 UTC. For Wasabi's live state, see https://down.guide/wasabi.
How long did it last?
0m, from 2024-12-01 23:41 UTC to 2024-12-01 23:41 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.