Last checked: 10 minutes ago
Get notified about any outages, downtime or incidents for Wasabi Technologies and 1800+ other cloud vendors. Monitor 10 companies, for free.
Outage and incident data over the last 30 days for Wasabi Technologies.
Join OutLogger to be notified when any of your vendors or the components you use experience an outage. It's completely free and takes less than 2 minutes!
Sign Up NowOutlogger tracks the status of these components for Xero:
| Component | Status |
|---|---|
| AP-Northeast-1 (Tokyo) | Active |
| AP-Northeast-2 (Osaka) | Active |
| AP-Southeast-1 (Singapore) | Active |
| AP-Southeast-2 (Sydney) | Active |
| CA-Central-1 (Toronto) | Active |
| EU-Central-1 (Amsterdam) | Active |
| EU-Central-2 (Frankfurt) | Active |
| EU-South-1 (Milan) | Active |
| EU-West-1 (London) | Active |
| EU-West-2 (Paris) | Active |
| US-Central-1 (Texas) | Active |
| US-East-1 (N. Virginia) | Active |
| US-East-2 (N. Virginia) | Active |
| US-West-1 (Oregon) | Active |
| Wasabi Account Control API | Active |
| Wasabi Account Control Manager Console | Active |
| Wasabi Management Console | Active |
View the latest incidents for Wasabi Technologies and check for official updates:
Description: On 12 May 2024 at 23:56 UTC until 13 May 2024 at 00:22 UTC, Wasabi had an issue in the US-EAST-1 \(Ashburn\) vault which resulted in degraded performance in the region. This impacted customer’s ability to send and retrieve data to/from their buckets in the region. The queueing service in US-EAST-1 region failed to accept new connections due to an overloaded memory issue. This caused issues with communication to our global database cache, which resulted in an inability to serve customer requests. Our Operations Team restarted the global database cache and queuing service. The restarting of both services resulted in connections being restored for the vault. At 00:22 UTC, 13 May 2024, all services were restored to the US-EAST-1 region.
Status: Postmortem
Impact: Minor | Started At: May 13, 2024, midnight
Description: On 07 May 2024 at 15:40 UTC, Wasabi had an issue in the US-EAST-1 \(Ashburn\) vault which resulted in severely degraded performance in the region. This impacted customer’s ability to send and retrieve data to/from their buckets in the region. At around 15:40 UTC, the Wasabi Operations team was deploying updates in the US-EAST-1 region which caused our queueing service to fail to accept new connections due to an overloaded memory issue. The queuing service failing to accept new connections caused issues with communication to our global database cache, which resulted in an inability to serve customer requests. To mitigate this issue, our Operations Team found it necessary to restart the global database cache and queuing service. Once the queuing service was restarted, it was allotted additional memory resources to avoid another overload scenario while the deployment was completed. The restarting of both services resulted in connections being restored for the vault. At 16:02 UTC, 07 May 2024, all services were restored to the US-EAST-1 region.
Status: Postmortem
Impact: Minor | Started At: May 7, 2024, 3:49 p.m.
Description: From 2024-04-03 11:55 UTC to 2024-04-03 12:25 UTC, we experienced a global outage with all Wasabi services, including S3, IAM, STS, WACM, WAC API, and Console, with our us-west-1 region having an extended outage lasting until 13:06 UTC. At 11:55 UTC our Operations Team was notified by our alerting system that our global database was beginning to experience memory-related issues outside of its normal operating range. Ten minutes later at 12:05 UTC the database crashed, causing all services and APIs to fail to accept any incoming requests from clients, resulting in a global outage of all services. At 2024-04-03 12:05 UTC, our Operations Team began the manual process of rebooting this database server instance to restore database operation. Once rebooted and all safety checks were completed, service was restored at 12:25 UTC to 12 out of 13 regions, with our us-west-1 region being the outlier. The regional servers in our us-west-1 region had difficulty with restoring the connection to our global database, which caused our Operations Team to take action by manually restarting these servers to restore connection. By 13:06 UTC, services were restored in our us-west-1 region.
Status: Postmortem
Impact: Critical | Started At: April 3, 2024, 12:08 p.m.
Description: On 3/25/24 from 15:02 UTC to 3/25/24 at 15:53 UTC, Wasabi experienced issues with logging into the Wasabi Web Console, returning an error message to users of "10000ms limit exceeded". During this timeframe, customers may have experienced issues with logging into the Wasabi Web Console and performing actions that rely on this application such as viewing billing information and SSO authentication. The Wasabi Operation Team noted that the cause of this issue was due to a large influx of connections coming from incoming client connections. Action was taken by increasing the available number of server hardware to handle these types of requests, which allowed our Operations Team to restore connections to the affected services.
Status: Postmortem
Impact: Minor | Started At: March 25, 2024, 3:35 p.m.
Description: On Tuesday February 27, 2024 at approximately 20:30:00 UTC, consistent timeout errors when attempting to log into the Wasabi Management Console were being seen by users. Wasabi Operations Team noted that some services were not running properly due to a memory issue. These services were restarted, and normal Wasabi Management Console logins resumed on February 27, 2024 at approximately 21:30:00 UTC.
Status: Postmortem
Impact: Major | Started At: Feb. 27, 2024, 8:43 p.m.
Join OutLogger to be notified when any of your vendors or the components you use experience an outage or down time. Join for free - no credit card required.
