Skip to content

Incident detail

Degraded Flink statements in Azure

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

    Confluent engineers are engaged on the incident.

    The impact is related to the ongoing Azure incident. You can find more information here: https://azure.status.microsoft/en-us/status

  2. Investigating

    We are continuing to investigate this issue.

  3. Identified

    Confluent has confirmed that Flink statements running in Azure are currently degraded. Microsoft is actively working to roll back the configuration change.

  4. Monitoring

    Microsoft has indicated they have completed rolling back the network configuration change. Degraded Flink statements have begun recovering.

  5. Monitoring

    Flink statements in Azure have recovered following Microsoft’s rollback of a recent network configuration change. Confluent systems are fully operational at this time, though Microsoft is continuing to monitor the rollback and validate stability. We will remain in monitoring until Microsoft confirms full recovery.

  6. Resolved

    Microsoft reports Azure status as fully operational. The incident is now resolved as of 0:40 UTC on Oct 29th, 2025.

Keep exploring

More from Confluent Cloud

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