Wasabi outage, 11 November 2026

System errors in CA-CENTRAL-1

Started
Resolved
11 Nov 2026, 14:42 UTC (after 3 h)
Impact
Minor
Affected
CA-Central-1 (Toronto)

Is this still happening?

No. Wasabi marked this incident resolved on 11 Nov 2026, 14:42 UTC, 3 h after it began.

Right now: Wasabi is running scheduled maintenance - some features may be briefly unavailable. (as of 13 Nov, 20:53 UTC) Live Wasabi status

At a glance

Our summary from the Wasabi incidents we have recorded since 29 May 2025 - how we count.

Last update from Wasabi

This incident has been resolved.

11 Nov 2026, 14:42 UTC

Read the full incident on the official Wasabi status page

Similar Wasabi incidents

Earlier incidents with the same affected part or wording - useful to see how long this kind of problem usually takes.

  1. , resolved after 1 h 43 min

    System Errors in AP-SOUTHEAST-1Postmortem

  2. , resolved after 2 h 51 min

    System Errors in US-EAST-1

  3. , resolved

    System Errors in EU-CENTRAL-2

  4. , resolved

    System Errors in AP-NORTHEAST-2Postmortem

  5. , resolved

    System Errors in AP-NORTHEAST-1

Other recent Wasabi incidents

  1. Intermittent Wasabi Console Access

  2. WACM reporting 0% storage utilization for subaccounts

  3. Intermittent Wasabi Console Access - Singapore (ap-southeast-1)

  4. Wasabi Management Console network errors

  5. Intermittent Network Error - Wasabi ConsolePostmortem

  6. System Errors in AP-NORTHEAST-1Postmortem

  7. StorageQuotaExceeded error sent incorrectly on some accounts

  8. Wasabi Management Console timeout and network errors in us-east-1

All recorded Wasabi incidents

Something wrong on this page?

A person reads every report. We fix our own mistakes - wording, mapping, a moved status page; the status itself always comes from Wasabi's official page. How we handle corrections.

Thanks - your report is on its way to us. We read every one.