Wasabi Outage History

Between 2026-05-20 17:57 UTC and 2026-05-21 01:44 UTC, a subset of customers operating in the AP-NORTHEAST-1 region experienced intermittent HTTP 5xx errors impacting object storage operations. The issue was triggered by failures on a portion of the underlying storage hosts, resulting in temporary service instability within the region. The host failures occurred under elevated internal system activity associated with platform health-management operations and concurrent storage reclamation workflows. Service impact was intermittent throughout the event window. Wasabi has implemented additional operational safeguards and recovery workflows to accelerate remediation of impacted internal nodes. These enhancements improve recovery efficiency across high-availability infrastructure and further reduce the risk and duration of future service-impacting events.

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.

On 25 July 2025 from 19:06 UTC to approximately 21:14 UTC, Wasabi's eu-west-3 \(London\) region experienced a service incident which resulted in elevated HTTP 5XX errors being returned for many request types to the region. The cause for the incident was an internal service failure, which prevented multiple services within the region from being able to successfully communicate across platforms. Due to this failure, our internal proxy service was unable to efficiently direct requests within the region, resulting in a degradation of the service and causing client requests to fail. Wasabi's Engineering and Operations teams worked to systematically restart impacted service hosts beginning at 19:20 UTC through 19:28 UTC. Once the hosts were back online, internal routing issues due to faulty configuration files required the team to manually correct the configurations and apply those to service hosts. By 21:24 UTC, all hosts and services were operating properly, and the region was operational.

On 16 July 2025 from 07:35 UTC to approximately 9:14 UTC, Wasabi's eu-central-1 \(Amsterdam\) region began to see degraded performance for some customers as multiple internal storage services went offline, resulting in elevated HTTP 5XX error responses for GET requests to their bucket\(s\). The cause for this degradation was an internal service restart, which failed to initialize all dependent services during the restart process. Due to this internal service failure, the internal connection to some storage subsystems was lost. Wasabi's Operations team was able to restart the failed initialization on all impacted servers to restore the S3 service to a fully operational state. By 9:14 UTC, all services in the eu-central-1 region were running properly.

On 08 July 2025 from 12:10 UTC to approximately 16:36 UTC, Wasabi S3 services in our Frankfurt \(eu-central-2\) region were unavailable due to a partial power issue in our datacenter. Wasabi’s Operations Team was alerted by our automated alert system that multiple racks were experiencing power issues, however not all racks within the datacenter were impacted due to the power issue not impacting all circuits within the building. While our Operations Team was working to bring up all server hardware and running system checks and diagnostics, a second power issue at 16:18 UTC caused all impacted racks to go offline a second time. By 16:36 UTC, our Operations Team was able to successfully bring up all impacted racks to a fully operational state.

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.

On 18 June 2025 at 23:10 UTC, Wasabi’s Sydney vault was impacted by Network issue at one of our network provider for 20 minutes, causing client requests to result in timeout when trying to reach to Wasabi endpoint in Sydney \([s3.ap-southeast-2.wasabisys.com](http://s3.ap-southeast-2.wasabisys.com)\). This issue was caused by one of the Networking providers in the region, which incorrectly blocked all traffic destined for Wasabi. The situation was restored to normal operation by migrating traffic to one of our other network providers until the routing issue was resolved.

On 28 May 2025 at 19:00 UTC, our Engineering and Operations Teams began investigating subaccount creation failures occurring within our WACM/WAC API services. These failures resulted in an HTTP 5XX response error when clients requested the creation of a subaccount utilizing the API or WACM UI. Upon investigation, it was found that a recently deployed software update was responsible for these errors from a bug which caused the API to be unable to reach an internal service due to query timeouts. Once the bug was discovered, our Engineering Team adjusted an internal parameter, allowing API requests to succeed properly. On 29 May 2025 at 03:30 UTC, the WACM/WAC API services were returned back to normal operation.

On 23 May 2025 at 23:00 UTC, Wasabi’s us-east-2 \(Manassas\) vault began seeing a large increase in S3 API traffic, causing regional resources to become strained with excessive internal connections. This excessive, sustained increase in traffic to the region was outside of normal operating conditions. At 08:12 UTC on 24 May 2025, this high resource usage began to impact the vault, causing an increase in 5xx errors for API calls to S3 buckets. Upon investigation from our Operations Team, it was found that a small number of accounts were responsible for consuming a large portion of available resources within the region, causing the increase in HTTP 5XX error responses for other customers. Our Operations Team took action by limiting the available connections to these accounts, which allowed for the overall active connections to the region to drop substantially. By 08:32 UTC on 24 May 2025, the region was back to normal operation.

From approximately 13:45 to 17:15 UTC, customers using the Free Trial Form Sign Up on Wasabi.com may have been met with a “Server Error” when submitting their request. Due to an error within one of our website modules, a portion of the service was impacted, which prevented the forms from being submitted properly. That error was resolved and the forms are now properly submitted and processed.

From 2025-05-07 03:00 UTC to 2025-05-07 16:00 UTC, a subset of customers experienced data upload issues due to an incorrect storage quota exceeded flag applied to their subaccounts. Specifically, some subaccounts configured with no quota value on their account were incorrectly marked as having exceeded their storage limit. As a result, these subaccounts were temporarily prevented from uploading data. This behavior was the result of a recent update to our billing system, which treated an empty storage quota value as a valid threshold of zero GB and triggered the excessive storage message. By 14:07 UTC, the problematic update was rolled back, and the affected accounts were unflagged. By 16:00 UTC, all impacted subaccounts were verified as having been reset correctly and the service had been returned to normal operational status. ` `

On 08 April 2025 from 14:13 UTC to approximately 14:39 UTC, Wasabi services in our Osaka \(ap-northeast-2\) region was unavailable due to an internal routing issue which impacted the region's ability to process incoming customer requests. At 14:13 UTC, our Operations Team was notified by our internal monitoring service that customer traffic was being impacted within the region. Upon investigation, it was found that internal DNS routing within the ap-northeast-2 region was failing to resolve internal hosts. Wasabi's Operations Team re-deployed the DNS stack and once re-deployment was completed at 14:39 UTC, customer connections to the region was restored.

On 27 March 2025 from 10:09 UTC to approximately 10:14 UTC, Wasabi services in our Ashburn \(us-east-1\), Manassas \(us-east-2\), Hillsboro \(us-west-1\), Plano \(us-central-1\), Amsterdam \(eu-central-1\), Tokyo \(ap-northeast-1\), Osaka \(ap-northeast-2\), London \(eu-west-1\), and Frankfurt \(eu-central-2\) regions were unavailable due to an issue, impacting customer traffic and Web Console connectivity. Wasabi Engineering and Operations teams were notified by our automated monitoring systems of an issue with a spike in connection between internal service worker nodes. This spike led to the inability to open new connections within the services. Wasabi’s Operations Team manually restarted the services, which corrected the issue and allowed for client connections to resume successfully. By 10:14 UTC, all internal services were restarted and all services returned to normal operating conditions.

On 05 February 2025 from 05:06 AM UTC to approximately 06:04 AM UTC, Wasabi Account Control Manager Console \(WACM\) was unavailable, resulting in errors 404 or 502 when trying to access the WACM URL. The issue was caused by internal component restart with a scenario of DB lock causing the slowness due to a backup routine and as consequence it took additional time for the service to be reestablished. Once the internal team stopped the backup routine, it was possible to proceed with the tasks needed and the restart action completed as expected, bringing the service up and running normally.