Live / Wasabi Technologies / Incident
Wasabi Technologies: System errors in CA-CENTRAL-1
Wasabi Technologies · wasabi.comMinor incidentResolved2026-11-11 14:42 UTC
Public — what happened
Summary
Wasabi Technologies said it began investigating a problem at 11:41 UTC on 2026-11-11 affecting its CA-CENTRAL-1 (Toronto) region, where customers could see errors or failed requests. By 12:21 UTC the company said it had identified the issue, that its Operations Team was working to restore service, and that customers might still receive HTTP 5XX error responses when using their storage buckets. At 12:31 UTC Wasabi said the region was operational again and it was monitoring, and the incident was marked resolved at 14:42 UTC. The company rated it as minor and did not state a cause in the text provided.
Affected
CA-Central-1 (Toronto)
Timeline
- Started — 2026-11-11 11:41 UTC
- Investigating — 2026-11-11 11:41 UTC
- Identified — 2026-11-11 12:21 UTC
- Monitoring — 2026-11-11 12:31 UTC
- Resolved — 2026-11-11 14:42 UTC · 3h after it started
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach Wasabi Technologies against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for Wasabi Technologies: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the Wasabi Technologies report →
More from Wasabi Technologies
Covered in The Squid’s Ink, Week 47, 2026, our weekly internet health report.