Rewindex

CompaniesConfluentIncidents

Confluent: Some Confluent Cloud users might experience issues with network provisioning and Kafka read/write unavailability in multiple AWS regions

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

AWS outage, Aug 29, 2024 · 14 vendors, 14 incidents

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

“…perience issues with network provisioning and Kafka read/write unavailability in multiple AWS regions This incident has been resolved.…”

Swipe sideways to see the whole diagram.

AWSown incident not archivedWithin an hour3 vendors, 1 blamed AWSSegment, Ably, Front1 to 4 hours later2 vendors, 1 blamed AWSConfluent, SemgrepConfluent (this incident)posted +1 h 4 min
AWSown incident not archivedWithin an hour3 vendors, 1 blamed AWSSegment, Ably, Front1 to 4 hours later2 vendors, 1 blamed AWSConfluent, SemgrepConfluent (this incident)posted +1 h 4 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/>3 vendors, 1 blamed AWS<br/>Segment, Ably, Front"]:::blames
  root --> h1
  h4["1 to 4 hours later<br/>2 vendors, 1 blamed AWS<br/>Confluent, Semgrep"]:::blames
  root --> h4
  me["Confluent (this incident)<br/>posted +1 h 4 min"]:::me
  h4 --- 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

    This incident has been resolved.

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

Confluent profileRecent Confluent incidentsMarkdownJSON