Wasabi outage, 27 May 2026

Intermittent Network Error - Wasabi Console

Started
Resolved
27 May 2026, 13:39 UTC (after 6 h 59 min)
Impact
Minor
Affected
US-Central-1 (Texas), EU-Central-1 (Amsterdam), EU-Central-2 (Frankfurt), EU-West-1 (London), Wasabi Management Console

Last update from Wasabi

Between 2026-05-26 13:40 UTC and 2026-05-27 09:20 UTC, some customers experienced intermittent difficulties accessing buckets through the Wasabi Console in the us-central-1, eu-central-1, eu-central-2, and eu-west-1 regions. The incident was caused by a deployment inconsistency introduced during a backend system update. As a result, a subset of backend services was running a different software version than expected, leading to intermittent failures when customers accessed bucket information through the Console. Following identification of the issue, Wasabi strengthened its deployment validation process to ensure software version consistency across production environments before feature act...

3 Jun 2026, 13:31 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