Wasabi outage, 13 May 2026

StorageQuotaExceeded error sent incorrectly on some accounts

Started
Resolved
8 May 2026, 10:00 UTC - reported afterwards
Impact
Not stated

Last update from Wasabi

On May 8, 2026, at approximately 10:00 UTC, a set of accounts was incorrectly flagged as having exceeded their Storage Quota. These were reset manually by 12:57 UTC, restoring backend/API upload functionality. Some customers may have experienced errors when attempting customers attempted GDB/S3 uploads during the incident window and experienced actual upload blocking behavior. Additionally, some customers experienced WACM or Custom Cloud Console application errors during this time. On May 9, 2026, a fix was deployed to address the issue and prevent future occurances.

8 May 2026, 10:00 UTC

Read the full incident on the official Wasabi status page

Is Wasabi down now?

This page is the record of one past incident. For the live status, see Is Wasabi down right now? - it reads the official status page every 2 minutes.

Other Wasabi incidents

  1. System Errors in AP-SOUTHEAST-1

  2. Intermittent Wasabi Console Access

  3. WACM reporting 0% storage utilization for subaccounts

  4. System Errors in US-EAST-1

  5. System Errors in EU-CENTRAL-2

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

  7. Wasabi Management Console network errors

  8. System Errors in AP-NORTHEAST-2

All recorded Wasabi incidents