Update timeline
- resolved Mar 30, 2026, 03:28 PM UTC
From 3/24 19:30 UTC to 3/25 10:15 UTC customers may have experienced elevated HTTP 5XX error responses when interacting with their Wasabi bucket(s) is AP-NORTHEAST-1 region. This issue has been resolved. For any questions please reach out to [email protected].
- postmortem Apr 27, 2026, 11:38 PM UTC
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.
Looking to track Wasabi downtime and outages?
Pingoru polls Wasabi's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.
- Real-time alerts when Wasabi reports an incident
- Email, Slack, Discord, Microsoft Teams, and webhook notifications
- Track Wasabi alongside 5,000+ providers in one dashboard
- Component-level filtering
- Notification groups + maintenance calendar
5 free monitors · No credit card required