rewindex

CompaniesWasabiIncidents

Wasabi: System Errors in AP-NORTHEAST-1

No impact listedStatus: postmortemStarted Resolved (-8399 min)2 updatesstspg.io (opens in new tab)

Timeline of updates

  1. resolved

    From 3/24 19:30 UTC to 3/25 10:15 UTC customers may have experienced elevated HTTP 5XX error responses when interacting with their Wasabi bucket(s) is AP-NORTHEAST-1 region. This issue has been resolved. For any questions please reach out to support@wasabi.com.

  2. postmortem

    Between 24 March 2026 at 19:30 UTC and 25 March 2026 at 10:15 UTC, Wasabi S3 read operations in the Tokyo region (ap-northeast-1) were impacted for a small subset of customers and buckets.

    The impact was caused by a software deployment that unintentionally impacted one of our storage pools, resulting in the inability to access data stored on that pool. No other storage pools in the Tokyo region were affected.

    Once this was detected the pool was enabled again and data access restored.

    Procedural changes were added and active monitoring was already added to avoid this specific type of incident in the future.

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-03-30 15:28 UTC, resolved after -8399 min, 2 update(s).

Title
System Errors in AP-NORTHEAST-1
Vendor
Wasabi
Date
URL
https://rewindex.com/company/wasabi/incidents/0bb0rjdfvmyf

Wasabi profileRecent Wasabi incidentsAll outages on March 30, 2026Wasabi in March 2026MarkdownJSON