Wasabi change history

Wasabi reported a major outage in AP-SOUTHEAST-1 (Singapore), starting 2026-10-10 02:27 UTC and lasting 1 h 43 min. Customers experienced degraded performance, elevated error rates and interrupted API operations. The postmortem attributed the disruption to a data-center power unit failure; the data center team replaced the failed unit and restored power.

Wasabi reported a major S3 outage in Frankfurt (eu-central-2) from 07:36 UTC to 08:03 UTC on 4 August 2026, caused by a frontend software update; rollback restored service. The record lists start 2026-08-04 14:20 UTC and resolution 2026-08-04 07:30 UTC, conflicting with the update; computed duration is unknown.

Wasabi reported a major outage affecting S3 services in US-West-1 (Oregon), disrupting customer access and operations. The incident started at 2026-02-06 08:45 UTC and was resolved at 2026-02-06 12:28 UTC, lasting 3 h 42 min. Wasabi attributed the disruption to a partial datacenter power issue affecting multiple racks.

Wasabi recorded a major outage in AP-Northeast-2 (Osaka), starting 2025-04-08 14:41 UTC and resolved at 2025-04-08 15:23 UTC (42 min). Its postmortem separately reported service unavailability on 08 April 2025 from 14:13 UTC to approximately 14:39 UTC, caused by an internal routing issue that impaired processing of incoming customer requests.

Wasabi reported a major incident in US-West-1 (Oregon), degrading performance and affecting customers’ S3 API calls. It started at 2024-09-25 13:51 UTC and was resolved at 2024-09-25 15:22 UTC (duration: 1 h 30 min). The postmortem attributed it to an upgrade misconfiguration that falsely marked a service ready; Operations corrected the issue.