Rewindex

CompaniesConfluentIncidents

Confluent: Intermittent Login failures in confluent cloud

MinorStatus: resolvedStarted Resolved (31 min)1 updatestatus.confluent.cloud (opens in new tab)
Part of an outage event

Cloudflare outage, Jun 21, 2022 · 30 vendors, 30 incidents

Confluent’s incident started in the same window without naming Cloudflare (timing only, not evidence of a link). (timing only, posted +54 min vs the first vendor naming Cloudflare)

Swipe sideways to see the whole diagram.

same windowCloudflareown incident not archivedWithin an hour5 vendors, 5 blamed CloudflareDoppler, LiveKit, Lattice, Mattermost +1Confluent (this incident)posted +54 min
same windowCloudflareown incident not archivedWithin an hour5 vendors, 5 blamed CloudflareDoppler, LiveKit, Lattice,Mattermost +1Confluent (this incident)posted +54 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["Cloudflare<br/>own incident not archived"]:::inferred
  h1["Within an hour<br/>5 vendors, 5 blamed Cloudflare<br/>Doppler, LiveKit, Lattice, Mattermost +1"]:::blames
  root --> h1
  me["Confluent (this incident)<br/>posted +54 min"]:::me
  root -.->|"same window"| 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

    Login issue is Resolved.

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