Last checked: 5 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: From 2024-09-18 17:55 UTC to 2024-09-18 18:08 UTC, we experienced an issue where client connection attempts to Wasabi Cloud Storage were impacted during an upgrade to our services in the CA-CENTRAL-1 region. The activity had no expectations to create any service impact and began on 2024-09-18 at 13:00 UTC. During the maintenance task, two internal software components had a networking port conflict, causing a delay on the restart process for our load balancer network component. Once our Operations Team identified the condition and cause for the failure, immediate corrective action was taken, and service availability was reestablished.
Status: Postmortem
Impact: None | Started At: Sept. 18, 2024, 6:09 p.m.
Description: From 2024-09-16 04:30 UTC to 2024-09-16 12:30 UTC, we experienced an issue within our US-EAST-1 region causing customers to receive 5XX errors and a reduced ability to ingest data to customer buckets within the region. The system user-servers reached capacity with logs resulting in a failure of our streaming service. Because the user-servers were busy writing logs, they had reduced capability to handle requests. Additionally, messages that were unable to be published were written to disk, further increasing I/O operations on the system. By 12:30 UTC, our Operations team had taken corrective action by emptying the streaming queue, and restarted the user-server services. After these actions were performed, ingest to our US-EAST-1 region had been fully restored.
Status: Postmortem
Impact: Minor | Started At: Sept. 16, 2024, 11:53 a.m.
Description: In Wasabi’s us-central-1 region, an incident occurred where a storage system I/O module became inoperable and prevented access to some disks that it served. Simultaneously, the software managing these disks improperly took multiple other disks offline. As a result of this incident, some objects on these disks are no longer accessible. The software problem that triggered this event has now been addressed and Wasabi is working on the appropriate remedy with affected customers and partners.
Status: Resolved
Impact: None | Started At: Aug. 30, 2024, 3:25 p.m.
Description: This incident has been resolved.
Status: Resolved
Impact: Minor | Started At: Aug. 28, 2024, 8:04 p.m.
Description: Between 10:32 UTC 2024-08-06 and 20:40 UTC 2024-08-07, we experienced three outages affecting both S3 and user services in all regions. Starting at 10:32 UTC 2024-08-06, our queueing service reached a full capacity state which impacted our database cache causing it to become unresponsive. The Wasabi Operations team initiated a restart to the primary database in an attempt to clear out all stale connections to the database while simultaneously clearing the queuing service queue. When this action failed to bring the database into a fully operational state, the secondary database instance was promoted to primary. At 11:20 UTC the S3 service was fully operational again. Between 13:17 UTC and 13:23 UTC, the database was restarted once more by Operations in order to fully incorporate our queueing service library. Between 02:55 UTC to 03:35 UTC on 2024-08-07, a second event occurred when our Operations team identified a configuration issue within the queueing service and the previously promoted secondary database instance. This configuration issue was causing timeouts to occur on user services such as our Web Console, WAC API, and WACM interface. Our Operations team then promoted the primary database back to production, alleviating these issues. There was no impact to S3 services during this event. Between 20:30 UTC to 20:44 UTC on 2024-08-07, a third event occurred when an automation cluster was failing to be seen by our automation service, causing a small decrease in accepted traffic to our S3 vaults. Our Operations team then recreated and redeployed this cluster, fully restoring the S3 service.
Status: Postmortem
Impact: Minor | Started At: Aug. 7, 2024, 3:46 a.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.
