Confluent: Confluent Cloud Clusters in AWS us-west-2 may be experiencing connectivity issues
AWS outage, Dec 15, 2021 · 49 vendors, 50 incidents
Confluent’s incident names AWS (location or integration). (hop 1, posted +30 min vs the first vendor naming AWS)
“…Confluent Cloud Clusters in AWS us-west-2 may be experiencing connectivity issues We have identified the issue which was first observed at 15:34 UTC which affected connectivity to AWS US West 2 region…”
Swipe sideways to see the whole diagram.
Mermaid source
flowchart LR
root["AWS<br/>own incident not archived"]:::inferred
h1["Within an hour<br/>15 vendors, 11 blamed AWS<br/>Daily, Gusto, Logz.io +12"]:::blames
root --> h1
me["Confluent (this incident)<br/>posted +30 min"]:::me
h1 --- 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
We have identified the issue which was first observed at 15:34 UTC which affected connectivity to AWS US West 2 region. The issue has been resolved at 15:56 UTC and service is operating normally.
From Confluent’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert.
How the archive is checked, and what it cannot prove.
This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.
Impact, status and times are the vendor’s own, as last archived. View on status.confluent.cloud (opens in new tab).