Skip to content

Incident detail

Experiencing high error rate in AZURE in West Europe region

Resolved incidentMajor1 affected service

Timeline window

to

Get alerted the next time Confluent Cloud breaks

Free email alerts for the handful of vendors you cannot afford to miss. No card, live in about a minute. Paid plans add Slack, Teams, Discord, and webhook delivery across your whole stack, plus higher API quotas.

Timeline

Incident updates

Every update on the official status source, oldest to newest, exactly as it appeared there.

  1. Investigating

    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.

  2. Identified

    Azure has identified the issue and recovery actions are underway

  3. Identified

    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.

  4. Identified

    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.

  5. Identified

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

    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.

  7. Identified

    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.

  8. Identified

    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.

  9. Identified

    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.

  10. Identified

    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.

  11. Monitoring

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

  12. Resolved

    This incident has been resolved.

Keep exploring

More from Confluent Cloud

Neighboring incidents on Confluent Cloud's timeline and the rest of their record on OutageDeck.