Vendor reports: operationalResolved · vendor status “postmortem”Official status API

System Errors in CA-CENTRAL-1

Reported by Wasabi · Cloud & Infrastructure · source last read 5 min ago

Official source (opens in a new tab)
Vendor start
Sep 18, 2024, 18:09 UTC
Vendor's clock
Resolved
Sep 18, 2024, 18:50 UTC
Vendor's clock
First seen by Statuswall
Before tracking began
Statuswall's clock
Duration
41 min
From vendor start and resolution

Summary

Built from the facts below, no AI

Potential impact, not a confirmed outage of your systems.

What the vendor confirmed

  • Wasabi reports operational: "System Errors in CA-CENTRAL-1".[E1, E2]
  • The vendor marked it resolved at 2024-09-18 18:50 UTC.[E3, E7]

Affected products and regions

  • Regions: ca-central-1 (read from the title, so inferred).[E5]
  • Components: CA-Central-1 (Toronto).[E6]

What is unknown

  • Whether your own systems are affected: a vendor report cannot tell you; check your monitoring.

Last update in these facts: 2024-09-18 18:50 UTC · summary s1, evidence fbe2fe2929351a03

Evidence (7)
  1. E1Wasabi reports operational. (vendor) source (opens in a new tab)
  2. E2Vendor title: "System Errors in CA-CENTRAL-1". (vendor) source (opens in a new tab)
  3. E3Vendor status word: "postmortem". (vendor) source (opens in a new tab)
  4. E4Vendor-reported start: 2024-09-18 18:09 UTC. (vendor) source (opens in a new tab)
  5. E5Regions written in the title (inferred): ca-central-1. (Statuswall) source (opens in a new tab)
  6. E6Components the vendor attached: CA-Central-1 (Toronto). (vendor) source (opens in a new tab)
  7. E7Vendor-reported resolution: 2024-09-18 18:50 UTC. (vendor) source (opens in a new tab)

Affected scope

ca-central-1

Components: CA-Central-1 (Toronto)

Read from region codes written in the incident title, so treat it as inferred.

Potential relevance

Wasabi is not in your stack. Follow it to see whether reports like this fall inside the regions you use.

Timeline

Vendor times come from the vendor. “Seen by Statuswall” times are when Statuswall noticed a change, which can lag the vendor by a few minutes. Statuswall does not store the vendor's update text; read it on the official page.

  1. Sep 18, 2024, 18:09 UTCVendor-reported startVendor time
  2. Sep 18, 2024, 18:50 UTCVendor-reported resolutionVendor time

No changes observed yet. Statuswall began recording changes on incidents in November 2026.

Wasabi: System Errors in CA-CENTRAL-1 — statuswall