outages.live
Live
Confluent CloudIncident ·

Kafka - Increased latency and connectivity issues - Azure - brazilsouth

ResolvedOfficial update
0

Confluent Cloud Kafka had increased latency and connectivity problems in the Azure brazilsouth region. The incident is resolved. It lasted 2 hours and 9 minutes.

State

Resolved

Started

Lasted

2 h 9 min

Worst impact

Degraded

Timeline

3 updates
12:4013:1213:4414:1714:49
DegradedUpdate postedTimes in UTC

Investigating

2 h 9 min 100%

Updates

Times in UTC

As posted by Confluent Cloud

Resolved

This incident has been resolved.

Investigating

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

Investigating

We are continuing to investigate this issue.

Affected components

1
Confluent Cloud

Confluent Cloud in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

17

Days with an incident

18

Median duration

3 h 41 min

This incident

42% shorter than the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

29 h 39 min
median 3 h 41 min
90 days agoToday

Other Confluent Cloud incidents

All incidents

Confluent Cloud·Multiple Confluent Cloud services are in a degraded state - GCP EU-West2

This incident is resolved as of 18:15 UTC on October 20. Confluent Cloud in GCP EU-West2 region is operating normally.

Resolved

Confluent Cloud·Delay in Kafka cluster provisioning

This incident has been resolved.

Resolved

Confluent Cloud·Confluent Cloud Console (UI) degraded functionality

This incident has been resolved.

Resolved

Confluent Cloud·Possible outage in AWS us-east-1

This incident has been resolved. All affected services have fully recovered.

Resolved

Confluent Cloud·Experiencing high error rate in AZURE in West Europe region

This incident has been resolved.

Resolved

Follow Confluent Cloud

Your coding agent knows when Confluent Cloud is down, and tells you when a failure is theirs, not yours. You can also get Confluent Cloud incidents in a feed reader or in Slack.

Prompt
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.

Add it as a remote MCP server named "outages" at https://outages.cc/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.

Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "confluent" and tell me if Confluent Cloud has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.

Paste this into any coding agent. It adds the server with its own MCP setup.

RSS
https://outages.cc/feed.xml?providers=confluent
Slack
/feed subscribe https://outages.cc/feed.xml?providers=confluent

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane