Wasabi: Issues with DB instance
AWS us-east-1 outage, Dec 22, 2021 · 40 vendors, 40 incidents
Wasabi’s incident started in the same window without naming AWS (timing only, not evidence of a link). (hop 1, posted −32 min vs the first vendor naming AWS)
Swipe sideways to see the whole diagram.
Mermaid source
flowchart LR
root["AWS us-east-1<br/>own incident not archived"]:::inferred
h1["Within an hour<br/>8 vendors, 6 blamed AWS<br/>Firebolt, Bitbucket, HubSpot, CircleCI +4"]:::blames
root --> h1
h4["1 to 4 hours later<br/>1 vendor<br/>Confluent"]:::names
root --> h4
me["Wasabi (this incident)<br/>posted −32 min"]:::me
root -.->|"same window"| meFull event: timeline, evidence and all vendors →
Detected automatically from incidents that started together and named the same provider. A link means one vendor’s incident named another, not a confirmed cause.
Timeline of updates
- resolved
From 12:10-12:25 UTC we saw errors on one of our DB instances that may have impacted some customers when logging into their Wasabi account or interfacing with their buckets. As of 12:25 UTC all systems are operational and responding correctly.
From Wasabi’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.
Impact, status and times are the vendor’s own, as last archived. View on status.wasabi.com (opens in new tab).