rewindex

CompaniesWasabiIncidents

Wasabi: StorageQuotaExceeded error sent incorrectly on some accounts

No impact listedStatus: resolvedStarted Resolved (-7848 min)1 updatestspg.io (opens in new tab)

Timeline of updates

  1. resolved

    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.

Archive proof

Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert. That proves this record existed by then and has not been changed since, by anyone, Rewindex included.

How the archive is checked, and what it cannot prove.

Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab).

Cite this

Status incident (vendor impact label: none) posted by Wasabi, started 2026-05-13 20:48 UTC, resolved after -7848 min, 1 update(s).

Title
StorageQuotaExceeded error sent incorrectly on some accounts
Vendor
Wasabi
Date
URL
https://rewindex.com/company/wasabi/incidents/x897s2f1tb9z

Wasabi profileRecent Wasabi incidentsAll outages on May 13, 2026Wasabi in May 2026MarkdownJSON