Rewindex

RewindexOutage eventsSep 1, 2026

Google Cloud us-central1 outage, Sep 1, 2026

45 vendors posted 49 incidents between 14:00 and 19:00 UTC, against about 32 incidents from 20 vendors in the same hours on an ordinary week. 13 vendors named Google Cloud in 15 incidents (13 of them blamed it). Google Cloud posted “Multiple products in us-central1-b are experiencing network service degradation.” at 14:42 UTC.

Observed, not verified. A line means a vendor’s incident named another vendor, or started in the same window. It is not a proven cause.

Times are UTC; lags are from when Google Cloud posted (14:42).

    11. Google Cloud posted 14:42
Named Google CloudNamed another vendorDid not name anyoneEach column is 30 minutes

How it spread

Vendors that named Google Cloud, grouped by when they posted, and vendors that blamed one of the vendors Google Cloud took down. Solid lines: the vendor named the other. Dashed: same window, not named.

Swipe sideways to see the whole diagram.

blamed GitHubblamed TwilioGoogle Cloud us-central1posted 14:42 UTCWithin an hour8 vendors, 8 blamed Google CloudPinecone, Elastic Cloud, FullStory, imgix +41 to 4 hours later6 vendors, 6 blamed Google CloudApollo GraphQL, Temporal Cloud, Clerk, Confluent+2GitHubposted +18 min, did not name Google CloudBolt.new+24 minTwilioposted +1 h 42 min, did not name Google CloudGorgias, Iterable+2 h 23 min to +2 h 37 min
blamed GitHubblamed TwilioGoogle Cloud us-central1posted 14:42 UTCWithin an hour8 vendors, 8 blamed GoogleCloudPinecone, Elastic Cloud,FullStory, imgix +41 to 4 hours later6 vendors, 6 blamed GoogleCloudApollo GraphQL, TemporalCloud, Clerk, Confluent +2GitHubposted +18 min, did not nameGoogle CloudBolt.new+24 minTwilioposted +1 h 42 min, did notname Google CloudGorgias, Iterable+2 h 23 min to +2 h 37 min
Rendered on the server with pele from the Mermaid source below. Each box lists the first few vendors; every vendor is listed further down.
Mermaid source
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, imgix +4"]:::blames
  root --> h1
  h4["1 to 4 hours later<br/>6 vendors, 6 blamed Google Cloud<br/>Apollo GraphQL, Temporal Cloud, Clerk, Confluent +2"]:::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

Vendors that named Google Cloud

In their own words. “Blames” means a causal phrase sits next to the name (“due to”, “upstream provider”…).

Within an hour

9 vendors

  • +23 min

    Blames Google Cloud

    Major incident

    Pinecone5xx errors on some control plane operations

    …the results. This incident has been resolved. This is likely related to ongoing issues in GCP. Affected services include Console, Index management, Assistant management, and APIs served at api.pinecon…

  • +36 min

    Blames Google Cloud

    Major incident

    Elastic CloudIssue impacting services running in GCP us-central1

    …Issue impacting services running in GCP us-central1 This issue has been resolved. An ongoing <a href="https://status.cloud.google.com/incidents/J5ia5t9p3g9Q5Wi7r8Ev">upstream CSP issue</a> is impactin…

  • +37 min

    Blames Google Cloud

    Critical incident

    FullStoryMultiple Fullstory Services Unavailable (NA1 Data Center)

    …es Unavailable (NA1 Data Center) The issue reported by our cloud infrastructure provider (Google Cloud Platform) is now resolved and Fullstory services are fully operational as of September 1st, 2026…

  • +49 min

    Blames Google Cloud

    Major incident

    imgixIncreased errors for new render requests

    …o normal levels. We are continuing to monitor the situation while awaiting an update from Google Cloud. This incident has been resolved. We have identified a correlation with an ongoing Google Cloud i…

  • +49 min

    Blames Google Cloud

    Minor incident

    SourcegraphCloud customers might see degraded performance because of underling Google Platform issues

    …Google Platform issues The issue has been resolved The issue has been resolved Underling Google Cloud infrastructure provider is experiencing performance issues, which might impact Sourcegraph Cloud…

  • +53 min

    Blames Google Cloud

    Critical incident

    Sigma ComputingWidespread failures are preventing Sigma from loading for GCP-hosted organizations.

    …Widespread failures are preventing Sigma from loading for GCP-hosted organizations. **Incident date:** September 1, 2026 **Duration:** Approximately 90 minutes **Affected service:** Sigma organization…

  • +54 min

    Blames Google Cloud

    Major incident

    CockroachDBCloud Latency, Delays, Connection Issues

    …restored. Should you need further help, please reach out and file a ticket with Support. Google Cloud is experiencing networking outages which is affecting Cockroach Cloud customers. Cockroach Cloud…

  • +59 min

    Blames Google Cloud

    Minor incident

    CohereMultiple Endpoint Disruptions

    …the incident has been fully resolved. 🛠️ We have identified the root cause as an ongoing Google Cloud Platform (GCP) outage. Our team is actively monitoring the situation while we wait for GCP to res…

  • +59 min

    Blames Google Cloud

    Major incident

    SourcegraphSign-in and authentication errors

    …en resolved Error rates have returned to normal and sign-in has recovered. The underlying Google Cloud networking incident is still ongoing, so we're continuing to monitor closely. The issue has been…

1 to 4 hours later

6 vendors

  • +1 h

    Blames Google Cloud

    Major incident

    Apollo GraphQLService Disruptions Due to Google Cloud Platform Issues

    …Service Disruptions Due to Google Cloud Platform Issues Our third party vendor has confirmed the issue is now resolved, and all Apollo products have recovered. Due to an ongoing outage on Google Cloud…

  • +1 h 6 min

    Blames Google Cloud

    Minor incident

    Temporal CloudElevated error rates in GCP us-central1

    …Elevated error rates in GCP us-central1 GCP is reporting that mitigations are in place, and that all services in this region are operational. MRN namespaces have been failed back to their primary regi…

  • +1 h 6 min

    Blames Google Cloud

    Minor incident

    ClerkGCP incident in us-central1-b

    …GCP incident in us-central1-b Latency and error rates have held steady since the last update. We will re-open if there is a resurgence in errors or latency. Dashboard analytics have recovered and we'r…

  • +1 h 45 min

    Blames Google Cloud

    Minor incident

    ConfluentInvestigating Elevated Errors in GCP us-central1

    …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…

  • +1 h 54 min

    Blames Google Cloud

    Major incident

    imgixIncreased errors for new render requests

    …Between approximately 7:49 AM and 10:57 AM PDT on September 1, 2026, a network fault in a Google Cloud Platform region disrupted connectivity to infrastructure that powers a portion of Imgix's image a…

  • +3 h 58 min

    Blames Google Cloud

    Minor incident

    AstronomerPotential impact to Astro deployments in GCP us-central1

    …Potential impact to Astro deployments in GCP us-central1 The GCP incident is marked as Closed officially Google Cloud has resolved the networking incident affecting us-central1. The incident ran from…

Second hop: vendors that named another vendor

These incidents name a vendor other than Google Cloud, for example a messaging or CDN provider that was itself affected.

Same window, did not name anyone

31 incidents started during the event without naming Google Cloud or another vendor. Some are part of it, some are a normal day’s background (about 32 in these hours).

Show all 31

Detected automatically from 23 status pages opening incidents in the peak hour (normally at most 8). Mentions are matched by name in each incident’s title and updates, then classified as cause, location or integration; quoted text is the vendor’s. Vendors that share one status page are shown once.