Wasabi: System Errors in AP-NORTHEAST-1
Timeline of updates
- resolved
Between 01:10 UTC and 02:15 UTC on June 25th, some customers may have experienced elevated HTTP 5XX error responses when accessing buckets in the AP-NORTHEAST-1 region.
The issue has been resolved. It was caused by a transient issue affecting Wasabi backend components, which was automatically detected by our monitoring systems and promptly remediated by our engineering team.
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.
First version captured
In the 2026-10-17 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
9c996773290a2e7d…
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-06-25 01:15 UTC, resolved after 0 min, 1 update(s).
- Title
- System Errors in AP-NORTHEAST-1
- Vendor
- Wasabi
- Date
- URL
- https://rewindex.com/company/wasabi/incidents/qpprzmswrcns
Wasabi profileRecent Wasabi incidentsAll outages on June 25, 2026Wasabi in June 2026MarkdownJSON