Live  /  Confluent Cloud  /  Incident

Confluent Cloud: Investigating Elevated Errors in GCP us-central1

Confluent Cloud · confluent.cloudMinor incidentResolved2026-09-01 16:39 UTC
Public — what happened

Summary

Confluent Cloud said some of its services in the Google Cloud us-central1 region were seeing higher error rates and slower performance starting at 16:27 UTC on 2026-09-01. Customers in that region could run into trouble creating or removing clusters, along with occasional connection problems, delays, or errors. The company attributed the problem to a networking issue on Google Cloud's side affecting part of the region, and said it was still working out how widespread the impact was. The incident is listed as investigating, though a resolution time of 17:18 is recorded.

Timeline

Source of record: provider status page. Summary written by SquidGrid from the provider’s published updates; times in UTC.

Independent path health

The status page is the symptom. SquidGrid measures the paths that reach Confluent Cloud against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.

🔒 Sign in to see
Customers get the live Provider Assessment Report for Confluent Cloud: its full incident track record, what tends to break, and recent public reports of problems.

Included with any paid plan.

Open the Confluent Cloud report →

More from Confluent Cloud

Covered in The Squid’s Ink, Week 37, 2026, our weekly internet health report.

The full archive is on the Confluent Cloud status & history page.

Related: Confluent Cloud status & history. SquidGrid is not affiliated with Confluent Cloud.