Rewindex

CompaniesConfluentIncidents

Confluent: Widespread Azure Instability and Unavailability

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

Azure outage, Apr 1, 2021 · 13 vendors, 13 incidents

Confluent’s incident blames Azure as the cause. (hop 1, posted +45 min vs the first vendor naming Azure)

“…Widespread Azure Instability and Unavailability We continue to see Confluent Cloud Clusters operating nominally. Should you find any continuing issues out of this DNS outage, please contact our Custom…”

Swipe sideways to see the whole diagram.

Azureown incident not archivedWithin an hour4 vendors, 3 blamed AzureLaunchDarkly, InfluxData (InfluxDB Cloud), Confluent, JFrogConfluent (this incident)posted +45 min
Azureown incident not archivedWithin an hour4 vendors, 3 blamed AzureLaunchDarkly, InfluxData(InfluxDB Cloud), Confluent,JFrogConfluent (this incident)posted +45 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["Azure<br/>own incident not archived"]:::inferred
  h1["Within an hour<br/>4 vendors, 3 blamed Azure<br/>LaunchDarkly, InfluxData (InfluxDB Cloud), Confluent, JFrog"]:::blames
  root --> h1
  me["Confluent (this incident)<br/>posted +45 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 continue to see Confluent Cloud Clusters operating nominally. Should you find any continuing issues out of this DNS outage, please contact our Customer Support and we will help you resolve them. Thank you for your continued patience.

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