- Level
- confirmed
- Worst impact
- Degraded
- Components
- CA-Central-1 (Toronto)
- Regions
- ca, ca-central-1
What to do
Check whether you use Wasabi CA-Central-1 (Toronto) in ca, ca-central-1. Check your stack
Drop a package.json, lockfile, Terraform or a list of domains at down.guide to see every provider you depend on.Fail over away from ca, ca-central-1 if you can, or switch to a fallback provider.
Otherwise back off retries and queue work, so you don't add load while it recovers.Watch Wasabi's own updates; this page re-reads them every minute.
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 an issue impacting the CA-CENTRAL-1 (Toronto) region, services in the region are impacted and customers may experience errors or failed requests.
provider
- identified
Our Operations Team is working to restore services in the region. Customers may continue to experience HTTP 5XX error responses when interacting with their Wasabi bucket(s) at this time.
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-af5031d73b
Is Wasabi down right now?
Wasabi reports degraded (System errors in CA-CENTRAL-1), open since 2026-11-11 11:41 UTC. Live state for every component: https://down.guide/providers/wasabi.
What was affected?
Wasabi named CA-Central-1 (Toronto) in ca, ca-central-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.