Wasabi Storage Accounts Receiving 'StorageQuotaExceeded' Error Message

Incident Report for Wasabi Technologies

Postmortem

From 2025-05-07 03:00 UTC to 2025-05-07 16:00 UTC, a subset of customers experienced data upload issues due to an incorrect storage quota exceeded flag applied to their subaccounts. Specifically, some subaccounts configured with no quota value on their account were incorrectly marked as having exceeded their storage limit. As a result, these subaccounts were temporarily prevented from uploading data. 

This behavior was the result of a recent update to our billing system, which treated an empty storage quota value as a valid threshold of zero GB and triggered the excessive storage message.  By 14:07 UTC, the problematic update was rolled back, and the affected accounts were unflagged. By 16:00 UTC, all impacted subaccounts were verified as having been reset correctly and the service had been returned to normal operational status. 

Posted May 09, 2025 - 21:36 UTC

Resolved

The issue affecting some RCS and PayGo accounts with an incorrect 'StorageQuotaExceeded' error message has been resolved. Please reach out to support@wasabi.com if you require further assistance.
NOTE: This entry has been updated to reflect that the incident affected not only RCS accounts but some PayGo accounts as well.

Posted May 08, 2025 - 01:32 UTC

Monitoring

A fix has been implemented and we expect that there will be no more new instances of this issue for any Wasabi accounts. If you continue to experience any issues with your Wasabi account, please reach out to our Support Team at support@wasabi.com
NOTE: This entry updated to reflect that the incident affected not only RCS accounts but some PayGo accounts as well.

Posted May 07, 2025 - 15:31 UTC

Identified

We have isolated this issue and are working to ensure all impacted accounts are adjusted appropriately.

Posted May 07, 2025 - 13:34 UTC

Investigating

We are investigating Storage Quota Exceeded error messages for RCS accounts, our teams are working to resolve this issue.

Posted May 07, 2025 - 13:09 UTC

This incident affected: US-Central-1 (Texas), US-East-1 (N. Virginia), US-East-2 (N. Virginia), US-West-1 (Oregon), CA-Central-1 (Toronto), EU-Central-1 (Amsterdam), EU-Central-2 (Frankfurt), EU-West-1 (London), EU-West-2 (Paris), EU-West-3 (London), EU-South-1 (Milan), AP-Northeast-1 (Tokyo), AP-Northeast-2 (Osaka), AP-Southeast-1 (Singapore), AP-Southeast-2 (Sydney), Wasabi Account Control API, Wasabi Account Control Manager Console, Wasabi Management Console, and Wasabi.com.