← Live dashboard

Elevated error rates and latencies in Azure westus2 region

ResolvedmajorOfficial source confirmedSingle region affectedFirst recorded update May 29, 2026, 05:57 AM · Resolved May 29, 2026, 09:47 PM

The Multi Service degradation on Azure has been mitigated. Confluent Cloud is operating normally.

Confluent Cloud live status →

Free for 3 services · Pro adds recovery alertsAdd to Chrome

What visitors reported during this incident

No visitor reports were filed for this incident.

Having problems with Confluent Cloud now? Check the current status

Affected services

Confluent Cloud

Updates (5)

  1. May 29, 2026, 09:47 PM
    Elevated error rates and latencies in Azure westus2 region

    The Multi Service degradation on Azure has been mitigated. Confluent Cloud is operating normally.

    Confluent Cloud ↗
  2. May 29, 2026, 04:49 PM
    Elevated error rates and latencies in Azure westus2 region

    Confluent services in the Azure West US2 region are now healthy. We are continuing to monitor for residual effects as Azure continues to address their service outage. More details about the Multi Service degradation on the Azure status page: https://azure.status.microsoft/en-us/status

    Confluent Cloud ↗
  3. May 29, 2026, 10:25 AM
    Elevated error rates and latencies in Azure westus2 region

    We are monitoring the health of impacted Confluent services in the Azure West US2 region. More details about the Multi Service degradation on the Azure status page: https://azure.status.microsoft/en-us/status

    Confluent Cloud ↗
  4. May 29, 2026, 06:47 AM
    Elevated error rates and latencies in Azure westus2 region

    Confluent cloud services are experiencing outage in Azure West US2 region linked to Azure network connectivity degradation. Team is continuing active investigation.

    Confluent Cloud ↗
  5. May 29, 2026, 05:57 AM
    Elevated error rates and latencies in Azure westus2 region

    We are currently experiencing increased error rates and latencies in the Azure westus2 region. This began at approximately 5:10 AM UTC 29th May. Our team is actively investigating it.

    Confluent Cloud ↗

What to do next

  • Verify your own services recovered cleanly. Some upstream outages leave queues or caches in a degraded state, run smoke tests before declaring green internally.
  • Save the post-mortem. Vendors usually publish a detailed RCA 1-3 days later. We'll add it to this page when it appears.
  • Watch the provider going forward. Follow Confluent Cloud's status feed →

GlobalOutageMap aggregates publicly reported signals. We never claim authoritative status, always cross-check the provider's official channel before making business decisions.