Confluent Cloud incident: Flink statements degraded in GCP us-central1 region

Affected components

• Confluent Cloud

1. resolvedJul 18, 2026, 00:59 UTC

   All the statements should be running now.

2. monitoringJul 17, 2026, 22:55 UTC

   Currently, we are monitoring the results after rolling out the fix.

3. identifiedJul 17, 2026, 22:54 UTC

   Engineers have identified and implemented a fix.

4. investigatingJul 17, 2026, 22:01 UTC

   Flink statements are degraded in GCP us-central1 region. The impact started at 18:37 UTC on July 17. Currently, engineers are investigating the issue.

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.

• Supabase: Project Actions Failing Across Multiple RegionsMajor · Jul 17, 2026, 17:49 UTC
• LaunchDarkly: LaunchDarkly is operational but customer action may be requiredMinor · Jul 10, 2026, 16:00 UTC
• Akamai: Application Load Balancer reporting availability issuesMinor · Jul 16, 2026, 04:21 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