Confluent Cloud outage: Experiencing high error rate in AZURE in West Europe region

Affected components

• Confluent Cloud

1. resolvedOct 10, 2026, 09:36 UTC

   This incident has been resolved.

2. monitoringOct 10, 2026, 08:47 UTC

   A fix has been implemented and we are monitoring the results.

3. identifiedOct 10, 2026, 04:15 UTC

   Confluent continues to work closely with Azure, and we are seeing recovery across a number of affected clusters. Azure has not yet provided a specific ETA for full resolution. We will continue to provide updates as more information becomes available.

4. identifiedOct 10, 2026, 02:12 UTC

   Confluent is continuing to work with Azure on recovery for a small number of affected clusters. Azure has not provided Confluent with a specific ETA for resolution. Our next update will be posted by 03:00 UTC, or sooner, as updates are available.

5. identifiedOct 10, 2026, 00:12 UTC

   Confluent is continuing to work with Azure on recovery for a small number of affected clusters. Azure has not provided Confluent with a specific ETA for resolution. Our next update will be posted by 01:00 UTC, or sooner, as updates are available.

6. identifiedOct 9, 2026, 23:03 UTC

   Confluent is continuing to work with Azure on recovery for a small number of affected clusters. Azure has not provided Confluent with a specific ETA for resolution. Our next update will be posted by 00:00 UTC, or sooner, as updates are available.

7. identifiedOct 9, 2026, 22:04 UTC

   Confluent is continuing to work with Azure on recovery for a small number of affected clusters. Azure has not provided Confluent with a specific ETA for resolution. Our next update will be posted by 23:00 UTC, or sooner, as updates are available.

8. identifiedOct 9, 2026, 21:07 UTC

   Confluent is continuing to work with Azure on recovery for a small number of affected clusters. Azure has not provided Confluent with a specific ETA for resolution. Our next update will be posted by 22:00 UTC, or sooner, as updates are available.

9. identifiedOct 9, 2026, 20:02 UTC

   Confluent is continuing to work with Azure on recovery for a small number of affected clusters. Azure has not provided Confluent with a specific ETA for resolution. Our next update will be posted by 21:00 UTC, or sooner, as updates are available.

10. identifiedOct 9, 2026, 19:10 UTC

    Confluent is continuing to work with Azure on recovery for a small number of affected clusters. Azure has not provided Confluent with a specific ETA for resolution. Our next update will be posted by 20:00 UTC, or sooner, as updates are available.

11. identifiedOct 9, 2026, 16:46 UTC

    Azure has identified the issue and recovery actions are underway

12. investigatingOct 9, 2026, 13:34 UTC

    Users in West Europe region of Azure could face elevated error rates and experience degraded performance. We are currently investigating the issue and attempting to mitigate or provide a work-around.

What APIStatus.watch saw

• Oct 10, 2026, 09:37 UTCpartial outage → operational

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

• Anthropic: Elevated errors on platform.claude.comMajor · Oct 7, 2026, 13:25 UTC
• CircleCI: Delay in data appearing in UI and APIMajor · Oct 9, 2026, 11:33 UTC
• OpenAI: Some ChatGPT content may be unavailable on AndroidMajor · Oct 9, 2026, 21:00 UTC
• OpenAI: Workspace admins may be unable to manage pluginsMajor · Oct 9, 2026, 21:48 UTC
• Convex: Failing function callsMajor · Oct 9, 2026, 22:33 UTC
• PlanetScale: AWS us-east-1 connectivity failuresMajor · Oct 9, 2026, 22:53 UTC
• Shippo: USPS Service DegradationMajor · Oct 9, 2026, 23:08 UTC
• Vercel: Delays in Drains, Observability, and Workflow in Washington (iad1)Major · Oct 10, 2026, 00:15 UTC
• Shippo: Elevated error rate on DPD Germany TrackingMajor · Oct 10, 2026, 06:42 UTC
• Twilio: MMS Delivery Delays from a Subset of Twilio Long Codes to GCI United StatesMinor · Sep 26, 2026, 03:16 UTC

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