Flink job submission and job scale operations are affected in GCP asia-northeast1, europe-west8, europe-north1, southamerica-east1
Dec 2, 21:37 UTCDec 3, 02:04 UTC
Duration
4h 27m
Impact
Major
Root cause
Not disclosed
Confluent, 90 days
20 incidents
Affected
Confluent Cloud
Final update
No further issues have been observed. The incident is now resolved as of 2025-1203 02:03 UTC.
Timeline
- Resolved · Dec 3, 02:04 UTC
No further issues have been observed. The incident is now resolved as of 2025-1203 02:03 UTC.
- Monitoring · Dec 3, 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.
- Identified · Dec 2, 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.
- Identified · Dec 2, 22:03 UTC
The root cause for the issue has been identified and the team is working on applying a mitigation.
- Investigating · Dec 2, 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.
More from Confluent
Full historyKafka - Increased latency and connectivity issues - Azure - brazilsouthlasted 2h 9mMultiple Confluent Cloud services are in a degraded state - GCP EU-West2lasted 10h 25mDelay in Kafka cluster provisioninglasted 7h 18mConfluent Cloud Console (UI) degraded functionalitylasted 2h 45mPossible outage in AWS us-east-1lasted 56mExperiencing high error rate in AZURE in West Europe regionlasted 20h 2m