Investigating Elevated Errors in GCP us-central1
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.
The latest update from Confluent Cloud.
State
Resolved
Started
61 d ago
2026-09-01 16:27 UTC
Lasted
48 min
until 2026-09-01 17:14 UTC
Worst impact
Degraded
Timeline
2 updatesInvestigating
48 min 100%
Updates
Times in UTCAs posted by Confluent Cloud
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.
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.
Affected components
1Confluent Cloud in the last 90 days
Full historyIncidents in 90 days
16
Days with an incident
17
Median duration
3 h 45 min
This incident
79% shorter than the median
Other Confluent Cloud incidents
All incidentsConfluent Cloud·Multiple Confluent Cloud services are in a degraded state - GCP EU-West2
This incident is resolved as of 18:15 UTC on October 20. Confluent Cloud in GCP EU-West2 region is operating normally.
Confluent Cloud·Delay in Kafka cluster provisioning
This incident has been resolved.
Confluent Cloud·Confluent Cloud Console (UI) degraded functionality
This incident has been resolved.
Confluent Cloud·Possible outage in AWS us-east-1
This incident has been resolved. All affected services have fully recovered.
Confluent Cloud·Experiencing high error rate in AZURE in West Europe region
This incident has been resolved.
Follow Confluent Cloud
Your coding agent knows when Confluent Cloud is down, and tells you when a failure is theirs, not yours. You can also get Confluent Cloud incidents in a feed reader or in Slack.
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.
Add it as a remote MCP server named "outages" at https://outages.cc/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.
Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "confluent" and tell me if Confluent Cloud has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.Paste this into any coding agent. It adds the server with its own MCP setup.
https://outages.cc/feed.xml?providers=confluent/feed subscribe https://outages.cc/feed.xml?providers=confluentFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane