Wasabi had 14 outages in the last 2 years totaling 19h 39m of downtime — averaging 0.6 incidents per month.
There were 14 Wasabi outages since October 23, 2025 totaling 19h 39m of downtime. Each is summarised below — incident details, duration, and resolution information.
We are currently investigating some customers difficulty to access the Wasabi Console. As alternative try to use your region URL, example: console.us-east-1.wasabisys.com or console.us-east-2.wasabisys.com or console.us-west-1.wasabisys.com etc
This incident has been resolved
We are currently investigating an issue with WACM reporting 0% storage utilization for subaccounts instead of the actual value
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.
We are currently investigating issues happening in US-EAST-1 region that are impacting some of the PUT (Upload) api calls.
Our team has identified the issue and fixed it. At the moment everything is back to normal and we will continue to monitor before we mark this event as resolved.
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.
We are currently investigating intermittent Network Errors when creating or accessing buckets via Wasabi Console in some regions.
We are continuing to investigate this issue.
The issue was identified and a fix implement by our team. We are currently monitoring our systems.
We are continuing to monitor for any further issues.
This incident has been resolved.
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.
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].
A power issue at the US-WEST-1 datacenter has been identified which is in the process of being restored. We will update this page as we have more information.
The issue has been identified and a fix is being implemented.
All services are operational and are currently under monitoring.
This incident has been resolved.
On 6 February 2026 from 06:30 UTC to approximately 10:02 UTC, Wasabi S3 services in our Hillsboro \(us-west-1\) region were unavailable due to a partial power issue within our datacenter facility. Wasabi’s Operations Team was alerted by our automated monitoring systems that multiple racks were experiencing power disruptions, which impacted customer access and operations during this time. The disruption originated within infrastructure hosted at Flexential’s Portland–Hillsboro 2 \(PDX02\) data center, where the failure of an upstream electrical distribution circuit breaker resulted in a loss of power to cabinets supporting affected systems. Flexential performed controlled restoration procedures and subsequently replaced the failed breaker under emergency change control. Following power restoration and comprehensive system validation checks by Wasabi’s Operations Team, services were progressively restored and us-west-1 region were fully operational.
We are investigating issues regarding Wasabi Console access. Some customers were facing timeout or webpage taking a long time to load.
We are continuing to investigate this issue.
Our team had identified the issue and the Wasabi Management Console access is back to normal. We will continue to monitoring the System status.
Management Console Access is restored to Operational Status
Customers attempting to log in to their Custom Cloud Console may receive a login error. We will update this page as we have more information.
The login issue with Custom Cloud Console has been identified and fixed.
Custom Cloud Console is now fully operational and being monitored by our Operations team.
The login issue with Custom Cloud Console has been resolved.