Minor impactResolvedDatabases

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

Confluent Cloud reported this minor-impact incident on its official status page on Nov 5, 2026, 12:40 UTC. It was resolved after 2h 9m.

Right now Confluent Cloud is operational. Live Confluent Cloud status →

🔔 Get alerted when Confluent Cloud has issuesFree · email alerts · no credit card
Nov 5, 2026, 12:40 UTC
started
Nov 5, 2026, 14:49 UTC
resolved
2h 9m
duration
Minor
impact

Affected components

  • Confluent Cloud
  1. resolvedNov 5, 2026, 14:49 UTC

    This incident has been resolved.

  2. investigatingNov 5, 2026, 14:06 UTC

    We are continuing to work with Azure for an ETA. The next update will be at 15:00 UTC

  3. investigatingNov 5, 2026, 12:41 UTC

    We are continuing to investigate this issue.

  4. investigatingNov 5, 2026, 12:40 UTC

    Kafka clusters in Azure brazilsouth are experiencing increased latency and connectivity issues as of 11:20 UTC on November 5. Customers may see client disconnects, increased produce and consume latency, and failed requests on single-zone clusters. Confluent is investigating and will post the next update by 13:30 UTC.

What APIStatus.watch saw

  • Nov 5, 2026, 12:41 UTCoperational → partial outage
  • Nov 5, 2026, 14:51 UTCpartial outage → operational

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

How often does Confluent Cloud have incidents?

Confluent Cloud reported 17 incidents in the last 90 days, 12 of them major or critical. A typical incident lasted 3h 45m. See Confluent Cloud's uptime and incident history