Wasabi Outage History

Issue affecting WACM storage utilization data has been resolved. Data synchronization was completed and WACM should now present the correct values. Please contact [email protected] if you continue to see any problem related to this incident.

The issue has been resolved. Earlier today, some customers in our US-EAST-1 region may have experienced elevated latency or errors on storage PUT requests due to an internal infrastructure issue on our backend. Our team identified the cause and applied a fix. Service has been fully restored. We apologize for any inconvenience.

On 4 August 2026 from 07:36 UTC to 08:03 UTC, Wasabi S3 services in our Frankfurt (eu-central-2) region were unavailable due to a recent software update to our frontend infrastructure. Wasabi’s Operations Team was alerted by our automated monitoring systems to a drop on our ingestion traffic and started investigating. The updated was rolled back and services were fully restored on the region by 08:03 UTC.

Between 2026-07-15 19:24 UTC and 20:26 UTC, a subset of customers experienced issues accessing the Wasabi Management Console when their requests were geo-routed through the Singapore console endpoint. Some affected customers also reported difficulty accessing bucket information through the Console. The incident occurred during the rollout of a new content delivery configuration for the Singapore console endpoint. Following deployment, some traffic routed through the new path experienced connectivity issues. Once the issue was identified, Wasabi rolled back the DNS changes, restoring the previous routing. Service recovered as DNS changes propagated globally. Following this incident, Wasabi is reviewing the deployment and validation process for regional console routing changes to improve pre-deployment testing, reduce customer impact during future rollouts, and strengthen monitoring of regional traffic after deployment.

On 4 July 2026, from 16:09 UTC to 17:37 UTC, customers experienced network error messages when accessing the Wasabi Management Console. Wasabi’s Operations team identified the issue and took action to restore service stability by rerouting traffic load. Wasabi Management Console functionality was fully restored by 17:37 UTC. For any questions, please reach out to [email protected].

Between 01:10 UTC and 02:15 UTC on June 25th, some customers may have experienced elevated HTTP 5XX error responses when accessing buckets in the AP-NORTHEAST-1 region. The issue has been resolved. It was caused by a transient issue affecting Wasabi backend components, which was automatically detected by our monitoring systems and promptly remediated by our engineering team.

This incident has been resolved.

On May 8, 2026, at approximately 10:00 UTC, a set of accounts was incorrectly flagged as having exceeded their Storage Quota. These were reset manually by 12:57 UTC, restoring backend/API upload functionality. Some customers may have experienced errors when attempting customers attempted GDB/S3 uploads during the incident window and experienced actual upload blocking behavior. Additionally, some customers experienced WACM or Custom Cloud Console application errors during this time. On May 9, 2026, a fix was deployed to address the issue and prevent future occurances.

On 25 April 2026, from 07:27 UTC to 12:50 UTC, customers experienced network errors and timeout messages when accessing the Wasabi Management Console via the US-East-1 endpoint. Wasabi’s Operations team identified the issue and took action to restore service stability by rerouting traffic load. Wasabi Management Console functionality in US-East-1 was fully restored by 12:50 UTC. For any questions, please reach out to [email protected].

This incident has been resolved.

Management Console Access is restored to Operational Status

The login issue with Custom Cloud Console has been resolved.

From 6:52AM to 7:04AM EST customers may have experienced elevated HTTP 5XX error responses when interacting with their Wasabi bucket(s). This issue has been resolved. For any questions please reach out to [email protected].