Confluent incident

Some customers using Confluent Cloud Flink on Azure with PrivateLink connectivity are experiencing issues submitting new Flink statements

Notice Resolved View vendor source →

Confluent experienced a notice incident on April 24, 2026 affecting Confluent Cloud, lasting 6h 56m. The incident has been resolved; the full update timeline is below.

Started
Apr 24, 2026, 05:18 PM UTC
Resolved
Apr 25, 2026, 12:14 AM UTC
Duration
6h 56m
Detected by Pingoru
Apr 24, 2026, 05:18 PM UTC

Affected components

Confluent Cloud

Update timeline

  1. investigating Apr 24, 2026, 05:18 PM UTC

    We are currently investigating this issue.

  2. identified Apr 24, 2026, 08:14 PM UTC

    The issue has been identified and fix is being rolled out. ETA for rollout complete across impacted regions 2 hours.

  3. identified Apr 24, 2026, 10:27 PM UTC

    Roll out of fix is progressing, expecting all clusters to complete in approximately 30 minutes.

  4. monitoring Apr 24, 2026, 11:06 PM UTC

    A fix has been implemented and we are monitoring for next hour.

  5. resolved Apr 25, 2026, 12:14 AM UTC

    This incident has been resolved.