Wasabi incident
System Errors in US-EAST-1 and US-EAST-2 regions
Wasabi experienced a minor incident on June 26, 2025 affecting US-East-1 (N. Virginia) and US-East-2 (N. Virginia), lasting 2h 13m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Jun 26, 2025, 06:01 PM UTC
We are currently investigating system errors in our US-EAST-1 and US-EAST-2 regions. Customers may experience elevated HTTP 5XX error responses when interacting with their Wasabi bucket(s). We will update this page as we have more information.
- monitoring Jun 26, 2025, 07:24 PM UTC
We have identified and resolved the issue. All affected resources are back in service. We are currently monitoring the status. If you see any error, please reach out to [email protected] for assistance.
- resolved Jun 26, 2025, 08:14 PM UTC
This incident has been resolved. Please reach out to [email protected] for any further assistance.
- postmortem Jul 03, 2025, 01:13 PM UTC
On 26 June 2025 from 18:30 UTC to 19:12 UTC, we experienced system errors in our us-east-1 and us-east-2 regions due to an unplanned data center thermal event. Starting at 18:30 UTC, our Operations team was notified of a spike in thermal temperature within several servers within the data centers. Due to the increase in temperature, multiple storage pools shut down power to the enclosed drives to preserve drive health and data integrity. Due to the powering down of these drives, several read & write operations resulted in HTTP 5XX errors. Upon notification of this thermal event, Wasabi’s Operations Team worked with the data center team to diagnose and correct the cooling issue and power cycled each impacted server. Once each server was fully powered up, all services was restored. By 19:12 UTC, all services were fully operational.