# Confluent: Widespread Azure Instability and Unavailability

- Impact (vendor’s label): none
- Status: resolved
- Started: 2021-04-01 22:15 UTC · Resolved: 2021-04-02 00:39 UTC · Duration: 2.4 h
- Updates: 1
- [Vendor status page: https://status.confluent.cloud/incidents/sb4zc2n0qvqx](https://status.confluent.cloud/incidents/sb4zc2n0qvqx)
- [Company: Confluent](https://rewindex.com/company/confluent.md)

## Part of an outage event

- [Azure outage, Apr 1, 2021: 13 vendors, 13 incidents](https://rewindex.com/events/2021-04-01-azure)
- This incident blames Azure as the cause. (hop 1, posted +45 min vs the first vendor naming Azure)
- Evidence: “…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…”

```mermaid
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
```

_Detected automatically from incidents that started together and named the same provider; a link means one incident named another vendor, not a confirmed cause._

## Timeline of updates

- **resolved** 2021-04-02 00:39 UTC: 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 the vendor’s published history: only the final update text is available for incidents before Rewindex began polling this page._


---
Canonical: https://rewindex.com/company/confluent/incidents/sb4zc2n0qvqx · Markdown: https://rewindex.com/company/confluent/incidents/sb4zc2n0qvqx.md · JSON: https://rewindex.com/api/v1/companies/confluent/incidents/sb4zc2n0qvqx · Generated 2026-10-19T23:15:51.308Z