Rewindex

CompaniesConfluentIncidents

Confluent: Connectivity issues in AWS in us-east1

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

AWS outage, Sep 28, 2023 · 23 vendors, 24 incidents

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

“…Connectivity issues in AWS in us-east1 This incident has been resolved.…”

Swipe sideways to see the whole diagram.

AWSown incident not archivedWithin an hour3 vendors, 1 blamed AWSAbly, Temporal Cloud, Keeper1 to 4 hours later4 vendors, 3 blamed AWSDremio, Firebolt, CockroachDB, Elastic CloudLater3 vendors, 1 blamed AWSAptible, Temporal Cloud, ConfluentConfluent (this incident)posted +8 h 51 min
AWSown incident not archivedWithin an hour3 vendors, 1 blamed AWSAbly, Temporal Cloud, Keeper1 to 4 hours later4 vendors, 3 blamed AWSDremio, Firebolt, CockroachDB,Elastic CloudLater3 vendors, 1 blamed AWSAptible, Temporal Cloud,ConfluentConfluent (this incident)posted +8 h 51 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/>Ably, Temporal Cloud, Keeper"]:::blames
  root --> h1
  h4["1 to 4 hours later<br/>4 vendors, 3 blamed AWS<br/>Dremio, Firebolt, CockroachDB, Elastic Cloud"]:::blames
  root --> h4
  later["Later<br/>3 vendors, 1 blamed AWS<br/>Aptible, Temporal Cloud, Confluent"]:::blames
  root --> later
  me["Confluent (this incident)<br/>posted +8 h 51 min"]:::me
  later --- 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.

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