Confluent Cloud incident: Investigating Elevated Errors in GCP us-central1

Affected components

• Confluent Cloud

1. resolvedSep 1, 2026, 17:14 UTC

   The GCP issue affecting the us-central1 region has been mitigated and all Confluent Cloud services in the region have returned to normal operation. Provisioning capability, error rates and latency have recovered to expected levels. Customers should no longer experience impact. If you continue to see any issues, please contact Confluent Support.

2. investigatingSep 1, 2026, 16:27 UTC

   We are investigating elevated error rates and degraded performance for some services running in the Google Cloud (GCP) us-central1 region. This is related to an ongoing Google Cloud networking issue affecting a portion of the region. Customers in this region may experience issues provisioning or deprovisioning clusters, intermittent connectivity issues, elevated latency, or errors. We are actively assessing the full scope of impact and will provide an update as more information becomes available.

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.

• Elasticsearch: Replication bug causing slow recoveriesMajor · Sep 1, 2026, 08:16 UTC
• Pinecone: 5xx errors on some control plane operationsMajor · Sep 1, 2026, 15:04 UTC
• Elasticsearch: Issue impacting services running in GCP us-central1Major · Sep 1, 2026, 15:18 UTC
• Imgix: Increased errors for new render requestsMajor · Sep 1, 2026, 16:36 UTC
• OVHcloud: [EU-SOUTH-MIL][Containers & Orchestration] - Managed Private Registry incident notificationMinor · Aug 26, 2026, 15:00 UTC
• Snowflake: INC20000150Minor · Aug 28, 2026, 00:07 UTC
• Snyk: Partial Broker Service DegradationMinor · Aug 30, 2026, 14:32 UTC
• Sentry: Span ingestion is degraded in USMinor · Sep 1, 2026, 14:16 UTC
• Grafana Cloud: Investigating issues in US Central (prod-us-central-0, prod-us-central-5)Minor · Sep 1, 2026, 15:25 UTC
• Clerk: GCP incident in us-central1-bMinor · Sep 1, 2026, 15:48 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