Wasabi experienced a minor incident on May 27, 2026 affecting US-Central-1 (Texas) and EU-Central-1 (Amsterdam) and 1 more component, lasting 6h 59m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating May 27, 2026, 06:39 AM UTC
We are currently investigating intermittent Network Errors when creating or accessing buckets via Wasabi Console in some regions.
- investigating May 27, 2026, 09:12 AM UTC
We are continuing to investigate this issue.
- monitoring May 27, 2026, 10:46 AM UTC
The issue was identified and a fix implement by our team. We are currently monitoring our systems.
- monitoring May 27, 2026, 01:38 PM UTC
We are continuing to monitor for any further issues.
- resolved May 27, 2026, 01:39 PM UTC
This incident has been resolved.
- postmortem Jun 03, 2026, 01:31 PM UTC
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 activation. Additional release verification controls have been implemented to better align tested and deployed software, and we are evaluating improvements to version reporting and monitoring to increase deployment visibility and help identify potential discrepancies earlier.