Confluent: Increase of errors in our Azure services due DNS connectivity issues in Azure
Timeline of updates
- resolved
Between 07:50 and approximately 08:45 UTC on 18 Jul 2020, Azure DNS experienced a transient resolution issue which in-turn impacted connectivity for some other Azure services. This affected some of the Confluent services in different zones including KSQL, Connect and our internal monitoring services. Kafka clusters should not be affected, but customers running on Azure might had been impacted too and unable to access our services.
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).
Cite this
Status incident (vendor impact label: none) posted by Confluent, started 2020-07-18 06:00 UTC, resolved after 0 min, 1 update(s).
- Title
- Increase of errors in our Azure services due DNS connectivity issues in Azure
- Vendor
- Confluent
- Date
- URL
- https://rewindex.com/company/confluent/incidents/5l44hf86fntx
Confluent profileRecent Confluent incidentsAll outages on July 18, 2020Confluent in July 2020MarkdownJSON