Live  /  Confluent Cloud  /  Incident

Confluent Cloud: Kafka - Increased latency and connectivity issues - Azure - brazilsouth

Confluent Cloud · confluent.cloudMinor incidentResolved2026-11-05 14:49 UTC
Public — what happened

Summary

Confluent Cloud said its Kafka clusters in the Azure brazilsouth region were having slower performance and connection problems, which it rated as minor. It reported that the trouble began at 11:20 UTC on November 5, and customers could see dropped client connections, slower sending and receiving of data, and failed requests on single-zone clusters. Confluent said it was investigating and later working with Azure to get an estimated time for a fix, without naming a cause in the updates provided. The incident is now marked resolved as of 14:49 UTC.

Affected

Confluent Cloud

As listed on Confluent Cloud’s status page.

Timeline

Source of record: provider status page. Summary written by SquidGrid from the provider’s published updates; times in UTC.

Independent path health

The status page is the symptom. SquidGrid measures the paths that reach Confluent Cloud against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.

🔒 Sign in to see
Customers get the live Provider Assessment Report for Confluent Cloud: its full incident track record, what tends to break, and recent public reports of problems.

Included with any paid plan.

Open the Confluent Cloud report →

More from Confluent Cloud

Covered in The Squid’s Ink, Week 46, 2026, our weekly internet health report.

The full archive is on the Confluent Cloud status & history page.

Related: Confluent Cloud status & history. SquidGrid is not affiliated with Confluent Cloud.