Rewindex

CompaniesConfluentIncidents

Confluent: Confluent Cloud UI Inaccessable

No impact listedStatus: resolvedStarted Resolved (38 min)1 updatestatus.confluent.cloud (opens in new tab)
Part of an outage event

AWS outage, Dec 15, 2021 · 49 vendors, 50 incidents

Confluent’s incident names AWS (location or integration). (hop 1, posted +35 min vs the first vendor naming AWS)

“…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.…”

Swipe sideways to see the whole diagram.

AWSown incident not archivedWithin an hour15 vendors, 11 blamed AWSDaily, Gusto, Logz.io +12Confluent (this incident)posted +35 min
AWSown incident not archivedWithin an hour15 vendors, 11 blamed AWSDaily, Gusto, Logz.io +12Confluent (this incident)posted +35 min
Confluent is outlined in red. Groups show up to a few vendors each; the event page lists every incident.
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 +35 min"]:::me
  h1 --- me

Full 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

  1. 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.

Impact, status and times are the vendor’s own, as last archived. View on status.confluent.cloud (opens in new tab).

Confluent profileRecent Confluent incidentsMarkdownJSON