# Confluent: Investigating Elevated Errors in GCP us-central1

- Impact (vendor’s label): minor
- Status: resolved
- Started: 2026-09-01 16:27 UTC · Resolved: 2026-09-01 17:14 UTC · Duration: 48 min
- Updates: 2 · Affected components: Confluent Cloud
- [Vendor status page: https://stspg.io/t0syqzdkvc44](https://stspg.io/t0syqzdkvc44)
- [Company: Confluent](https://rewindex.com/company/confluent.md)

## Part of an outage event

- [Google Cloud us-central1 outage, Sep 1, 2026: 47 vendors, 54 incidents](https://rewindex.com/events/2026-09-01-google-cloud-us-central1)
- This incident blames Google Cloud as the cause. (hop 1, posted +1 h 45 min vs Google Cloud’s own post)
- Evidence: “…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. Pro…”

```mermaid
flowchart LR
  root["Google Cloud us-central1<br/>posted 14:42 UTC"]:::root
  h1["Within an hour<br/>8 vendors, 8 blamed Google Cloud<br/>Pinecone, Elastic Cloud, FullStory +5"]:::blames
  root --> h1
  h4["1 to 4 hours later<br/>6 vendors, 6 blamed Google Cloud<br/>Apollo GraphQL, Temporal Cloud, Clerk +3"]:::blames
  root --> h4
  p0["GitHub<br/>posted +18 min, did not name Google Cloud"]:::timing
  root -.-> p0
  k0["Bolt.new<br/>+24 min"]:::hop2
  p0 -->|"blamed GitHub"| k0
  p1["Twilio<br/>posted +1 h 42 min, did not name Google Cloud"]:::timing
  root -.-> p1
  k1["Gorgias, Iterable<br/>+2 h 23 min to +2 h 37 min"]:::hop2
  p1 -->|"blamed Twilio"| k1
  me["Confluent (this incident)<br/>posted +1 h 45 min"]:::me
  h4 --- me
```

_Detected automatically from incidents that started together and named the same provider; a link means one incident named another vendor, not a confirmed cause._

## Timeline of updates

- **investigating** 2026-09-01 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.
- **resolved** 2026-09-01 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.


---
Canonical: https://rewindex.com/company/confluent/incidents/7k0n2f5rgfgs · Markdown: https://rewindex.com/company/confluent/incidents/7k0n2f5rgfgs.md · JSON: https://rewindex.com/api/v1/companies/confluent/incidents/7k0n2f5rgfgs · Generated 2026-10-20T00:03:15.976Z