outages.live
Live
Confluent CloudIncident · 2026-08-25 04:17 UTC

Elevated error rates and latencies in Azure Southeast Asia region

ResolvedOfficial update

Confluent services in the Azure Southeast Asia region are now healthy and operating normally.

The latest update from Confluent Cloud.

State

Resolved

Started

68 d ago

2026-08-25 04:17 UTC

Lasted

3 h 12 min

until 2026-08-25 07:29 UTC

Worst impact

Partial outage

Timeline

3 updates
04:1705:0505:5306:4107:29
Partial outageUpdate postedTimes in UTC

Investigating

1 h 11 min 37%

Monitoring

2 h 1 min 63%

Updates

Times in UTC

As posted by Confluent Cloud

Resolved2026-08-25 07:29 UTC

Confluent services in the Azure Southeast Asia region are now healthy and operating normally.

Monitoring2026-08-25 05:28 UTC

We are seeing recovery of Confluent services in the affected Azure Southeast Asia region and are continuing to monitor the situation.

Investigating2026-08-25 04:17 UTC

We are investigating connectivity issues and elevated error rates affecting some Confluent Cloud clusters hosted in the Azure Southeast Asia region, beginning at approximately 03:13 UTC on 25 Aug 2026. Affected customers may experience degraded produce/consume availability or intermittent connectivity for clusters in this region. This is associated with an ongoing Microsoft Azure service disruption in the Southeast Asia region. We are actively engaged with Microsoft Azure.

Affected components

1
Confluent Cloud

Confluent Cloud in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

16

Days with an incident

17

Median duration

3 h 45 min

This incident

About 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 45 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.

Resolvedresolved 12 d ago

Confluent Cloud·Delay in Kafka cluster provisioning

This incident has been resolved.

Resolvedresolved 16 d ago

Confluent Cloud·Confluent Cloud Console (UI) degraded functionality

This incident has been resolved.

Resolvedresolved 17 d ago

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

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

Resolvedresolved 22 d ago

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

This incident has been resolved.

Resolvedresolved 22 d ago

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