Wasabi incident

StorageQuotaExceeded error sent incorrectly on some accounts

Resolved after 2 hours 57 minutes, on May 8, 2026.

resolved May 13, 2026, 08:48 PM UTC

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.

Started
May 08, 2026, 10:00 AM UTC
Resolved
May 08, 2026, 12:57 PM UTC
Duration
2h 57m
Detected by Pingoru
May 08, 2026, 10:00 AM UTC

Update timeline

  1. resolved May 13, 2026, 08:48 PM UTC

    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.

Your product runs on more than Wasabi

Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.

Add your stack →