Wasabi outage, 30 March 2026

System Errors in AP-NORTHEAST-1

Started
Resolved
24 Mar 2026, 19:30 UTC - reported afterwards
Impact
Not stated

Last update from Wasabi

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.

27 Apr 2026, 23:38 UTC

Read the full incident on the official Wasabi status page

Is Wasabi down now?

This page is the record of one past incident. For the live status, see Is Wasabi down right now? - it reads the official status page every 2 minutes.

Other Wasabi incidents

  1. System Errors in AP-SOUTHEAST-1

  2. Intermittent Wasabi Console Access

  3. WACM reporting 0% storage utilization for subaccounts

  4. System Errors in US-EAST-1

  5. System Errors in EU-CENTRAL-2

  6. Intermittent Wasabi Console Access - Singapore (ap-southeast-1)

  7. Wasabi Management Console network errors

  8. System Errors in AP-NORTHEAST-2

All recorded Wasabi incidents