# Wasabi: Issues with DB instance

- Impact (vendor’s label): none
- Status: resolved
- Started: 2021-12-22 12:10 UTC · Resolved: 2021-12-22 12:10 UTC · Duration: 0 min
- Updates: 1
- [Vendor status page: https://status.wasabi.com/incidents/d1n352dstg3c](https://status.wasabi.com/incidents/d1n352dstg3c)
- [Company: Wasabi](https://rewindex.com/company/wasabi.md)

## Part of an outage event

- [AWS us-east-1 outage, Dec 22, 2021: 40 vendors, 40 incidents](https://rewindex.com/events/2021-12-22-aws-us-east-1)
- This 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)

```mermaid
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"| me
```

_Detected automatically from incidents that started together and named the same provider; a link means one incident named another vendor, not a confirmed cause._

## Timeline of updates

- **resolved** 2021-12-22 12:10 UTC: 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 the vendor’s published history: only the final update text is available for incidents before Rewindex began polling this page._


---
Canonical: https://rewindex.com/company/wasabi/incidents/d1n352dstg3c · Markdown: https://rewindex.com/company/wasabi/incidents/d1n352dstg3c.md · JSON: https://rewindex.com/api/v1/companies/wasabi/incidents/d1n352dstg3c · Generated 2026-10-19T23:16:21.837Z