Major impactOngoingDatabases

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

Confluent Cloud reported this major-impact incident on its official status page on Oct 9, 2026, 23:03 UTC. It has not been marked resolved yet.

Right now Confluent Cloud is having a partial outage. Live Confluent Cloud status →

🔔 Get alerted when Confluent Cloud has issuesFree · email alerts · no credit card
Oct 9, 2026, 23:03 UTC
started
—
resolved
ongoing
duration
Major
impact

Affected components

  • Confluent Cloud
  1. 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.

  2. 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.

  3. 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.

  4. 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.

  5. 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.

  6. 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.

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

  8. identifiedOct 9, 2026, 16:46 UTC

    Azure has identified the issue and recovery actions are underway

  9. 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

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.

How often does Confluent Cloud have incidents?

Confluent Cloud reported 16 incidents in the last 90 days, 11 of them major or critical. A typical incident lasted 4h 1m. See Confluent Cloud's uptime and incident history