Confluent incident

Flink statements failing in multiple regions

Critical Resolved View vendor source →

Confluent experienced a critical incident on October 22, 2025 affecting Confluent Cloud, lasting 6h 24m. The incident has been resolved; the full update timeline is below.

Started
Oct 22, 2025, 04:21 PM UTC
Resolved
Oct 22, 2025, 10:45 PM UTC
Duration
6h 24m
Detected by Pingoru
Oct 22, 2025, 04:21 PM UTC

Affected components

Confluent Cloud

Update timeline

  1. investigating Oct 22, 2025, 04:21 PM UTC

    Flink statements are failing to execute across multiple regions. The impact started at 15:12 UTC on Oct. 22, 2025. Customers may be experiencing increased rate of degraded statements and internal errors. We are currently investigating the issue.

  2. identified Oct 22, 2025, 05:42 PM UTC

    The issue causing Flink statement failures has been identified and a hotfix has been prepared. We are actively working to mitigate all impacted compute pools.

  3. identified Oct 22, 2025, 07:04 PM UTC

    We are continuing to mitigate Flink statement failures and apply fixes to necessary compute pools. We will post an update in 1 hour, or sooner if mitigation has been completed.

  4. identified Oct 22, 2025, 08:33 PM UTC

    A fix has been applied to a number Flink compute pools, but some customers may still see failing statement failures. We are continuing to apply the fixes to the remaining impacted pools. The next update will be posted in 1 hour, or sooner if mitigation has been completed.

  5. monitoring Oct 22, 2025, 10:25 PM UTC

    All impacted Flink compute pools have been fixed and degraded statements have now recovered. We are continuing to monitor to ensure no further issues occur.

  6. resolved Oct 22, 2025, 10:45 PM UTC

    All impacted Flink compute pools have been fixed and degraded statements have recovered.