Confluent incident

Flink job submission and job scale operations are affected in GCP asia-northeast1, europe-west8, europe-north1, southamerica-east1

Major Resolved View vendor source →

Confluent experienced a major incident on December 2, 2025 affecting Confluent Cloud, lasting 4h 26m. The incident has been resolved; the full update timeline is below.

Started
Dec 02, 2025, 09:37 PM UTC
Resolved
Dec 03, 2025, 02:04 AM UTC
Duration
4h 26m
Detected by Pingoru
Dec 02, 2025, 09:37 PM UTC

Affected components

Confluent Cloud

Update timeline

  1. investigating Dec 02, 2025, 09:37 PM UTC

    This manifests itself in new Flink jobs remaining stuck in "Statement Status: Pending", existing Flink jobs being requested to stop remaining stuck in "Statement Status: Stopping". This issue started manifesting at 2025-12-02 19:53 UTC. We are currently investigating the issue and attempting to mitigate or provide a work-around.

  2. identified Dec 02, 2025, 10:03 PM UTC

    The root cause for the issue has been identified and the team is working on applying a mitigation.

  3. identified Dec 02, 2025, 11:14 PM UTC

    The team has successfully applied a fix to asia-northeast1 and we're seeing recovery there. Meanwhile the team is applying mitigations in the other affected regions.

  4. monitoring Dec 03, 2025, 01:32 AM UTC

    A fix has been applied to all regions and we've seen recovery in all affected regions. We'll continue to monitor for the next 30 minutes.

  5. resolved Dec 03, 2025, 02:04 AM UTC

    No further issues have been observed. The incident is now resolved as of 2025-1203 02:03 UTC.