Confluent Cloud outage: Availability issues for Kafka clusters in Azure West Europe

Affected components

• Confluent Cloud

1. resolvedNov 6, 2025, 21:39 UTC

   All affected clusters are now fully operational.

2. monitoringNov 6, 2025, 14:03 UTC

   Issues observed with Azure Europe West are now resolved. Most impacted services have recovered and are operational. We are working on resolving issues impacting performance for few customers.

3. identifiedNov 6, 2025, 01:48 UTC

   We are monitoring Azure updates and recovery closely. We are noticing partial recovery in a subset of affected resources and will provide an update as more information becomes available.

4. identifiedNov 5, 2025, 22:29 UTC

   Azure has provided an update on it's Status Page (https://azure.status.microsoft/en-us/status) stating that recovery efforts are in progress. We will provide an update within 60 minutes.

5. identifiedNov 5, 2025, 21:13 UTC

   Azure posted outage details on its status page: https://azure.status.microsoft/en-us/status. No material changes since last update. We continue monitoring the situation from our side and will provide the next update within 60 minutes or when the status changes.

6. identifiedNov 5, 2025, 19:51 UTC

   The issue was localized to a single Availability Zone in Azure West Europe region. Only Single Zone Kafka Clusters are affected at this time. Multi-Zone clusters experienced intermittent availability and elevated latency for produce and fetch requests but auto-recovered within minutes. We are continuing to work with Microsoft Azure for resolution of affected single zone clusters. We will post next update by 1:00 PST.

7. investigatingNov 5, 2025, 19:22 UTC

   We are continuing to investigate this issue.

8. investigatingNov 5, 2025, 18:47 UTC

   We are beginning to see some recovery of the affected Kafka clusters.

9. investigatingNov 5, 2025, 18:19 UTC

   We are currently experiencing an issue that appears to be related to an ongoing incident with Microsoft Azure. We are actively working with the Azure team to confirm the impact and will provide updates as soon as more information becomes available.

What APIStatus.watch saw

Our 5-minute checks didn't record a change in Confluent Cloud's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

• LogRocket: Ingestion InstabilityMajor · Nov 5, 2025, 19:43 UTC
• Pinecone: [Serverless][AWS][eu-west-1] 5xx errors on some write path operationsMajor · Nov 6, 2025, 14:38 UTC
• Mux: Investigating elevated playback errors on Chrome version 141.0.7390.123 and laterMinor · Oct 23, 2025, 14:16 UTC
• Convex: elevated latency/errors for a subset of customersMinor · Nov 5, 2025, 22:37 UTC
• Sanity: Elevated API and API CDN error rate for some customersMinor · Nov 6, 2025, 08:40 UTC
• npm: Issue with npm website and loginMinor · Nov 6, 2025, 13:56 UTC
• 1Password: Elevated Errors and Latency Affecting AuthenticationMinor · Nov 6, 2025, 20:16 UTC

How often does Confluent Cloud have incidents?

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