System Errors in CA-CENTRAL-1

What to do

• Check whether you use Wasabi CA-Central-1 (Toronto) in ca, ca-central-1. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 41m it lasted.

  Anything that failed between 2024-09-18 18:09 UTC and 2024-09-18 18:50 UTC may need a replay.

• Subscribe to Wasabi's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=wasabi works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Wasabi 4

1. investigatingSep 18, 2024, 6:09 PM UTC

   We are currently experiencing system errors in our CA-CENTRAL-1 region.

   provider

2. monitoringSep 18, 2024, 6:17 PM UTC

   Our Operations Team identified and corrected the cause of the system errors. Performance to the region is restored and we will continue to monitor the region.

   provider

3. resolvedSep 18, 2024, 6:50 PM UTC

   This incident is now resolved. Please reach out to support@wasabi.com if you continue to see any errors related to this incident.

   provider

4. postmortemSep 27, 2024, 6:03 PM UTC

   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.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.