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

Affected components

• Confluent Cloud

1. resolvedDec 3, 2025, 02:04 UTC

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

2. monitoringDec 3, 2025, 01:32 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.

3. identifiedDec 2, 2025, 23:14 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. identifiedDec 2, 2025, 22:03 UTC

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

5. investigatingDec 2, 2025, 21:37 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.

What APIStatus.watch saw

Our 5-minute checks didn't record a change in Confluent Cloud's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

• Contentful: CMA Usage reporting and Audit Logs missing fieldsMinor · Dec 2, 2025, 15:12 UTC

How often does Confluent Cloud have incidents?

Confluent Cloud reported 13 incidents in the last 90 days, 8 of them major or critical. A typical incident lasted 7h 3m. See Confluent Cloud's uptime and incident history