rewindex

RewindexOutage eventsAug 20, 2026

Google Cloud us-west1 outage, Aug 20, 2026

8 linked vendors posted 8 incidents between and . 8 vendors named Google Cloud in 8 incidents (7 of them blamed it), and 2 did so before Google Cloud’s own status page. Google Cloud posted “We are investigating an issue where customers may experience timeouts, service degradations, errors, and elevated latencies across multiple products in the us-west1 region.” at 15:40 UTC. 12 other vendors had incidents in the same window; nothing links them to Google Cloud (listed below).

Observed, not verified. A line means a vendor’s incident named another vendor, or a known dependency (declared by the vendor and named as a cause before). It is not a proven cause. Incidents that only share the time window are listed apart.

Times are in UTC; lags are from when Google Cloud posted ().

    9. Google Cloud posted first vendor named Google Cloud
Named Google CloudNamed another vendor or depends on oneEach 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: a known dependency, not named in the incident.

Swipe sideways to see the whole diagram.

Google Cloud us-west1posted 15:40 UTCPosted before Google Cloud did2 vendors, 1 blamed Google CloudFirebase, Temporal CloudWithin an hour3 vendors, 3 blamed Google CloudRender, Mailgun, E2B1 to 4 hours later3 vendors, 3 blamed Google CloudConfluent, Harness, Bugsnag
Google Cloud us-west1posted 15:40 UTCPosted before Google Cloud did2 vendors, 1 blamed GoogleCloudFirebase, Temporal CloudWithin an hour3 vendors, 3 blamed GoogleCloudRender, Mailgun, E2B1 to 4 hours later3 vendors, 3 blamed GoogleCloudConfluent, Harness, Bugsnag
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-west1<br/>posted 15:40 UTC"]:::root
  before["Posted before Google Cloud did<br/>2 vendors, 1 blamed Google Cloud<br/>Firebase, Temporal Cloud"]:::blames
  root --> before
  h1["Within an hour<br/>3 vendors, 3 blamed Google Cloud<br/>Render, Mailgun, E2B"]:::blames
  root --> h1
  h4["1 to 4 hours later<br/>3 vendors, 3 blamed Google Cloud<br/>Confluent, Harness, Bugsnag"]:::blames
  root --> h4

Vendors that named Google Cloud

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

Posted before Google Cloud did

2 vendors

Within an hour

3 vendors

  • +7 min

    Blames Google Cloud

    Major incident

    RenderDeployment Issues

    …This incident has been resolved. An issue has been identified with our upstream provider, Google Cloud. Free Web Services: Builds/deploys and spin-up have been temporarily disabled while we work to mi…

  • +39 min

    Blames Google Cloud

    Minor incident

    MailgunGCP Reporting Multi Service Outage in US-West1

    …GCP Reporting Multi Service Outage in US-West1 This incident has been resolved. GCP has put a mitigation in place, we are monitoring the results. At this time we are experiencing no impacts. All delay…

  • +45 min

    Blames Google Cloud

    Minor incident

    E2BElevated error rates for sandbox operations

    …Elevated error rates for sandbox operations Resolved. Google Cloud fully resolved the underlying Compute Engine incident at 12:37 PDT and all sandbox operations in the US region are back to normal. Re…

1 to 4 hours later

3 vendors

  • +1 h 30 min

    Blames Google Cloud

    Major incident

    ConfluentElevated error rates and latency in GCP us-west1

    …Elevated error rates and latency in GCP us-west1 The GCP issues in us-west1 region have been mitigated. Confluent services are no longer seeing any impact based on our monitoring. The GCP issues in us…

  • +1 h 37 min

    Blames Google Cloud

    Major incident

    HarnessAll modules are running slow in Prod1/2/3/4 due to cloud provider incident

    …tion, pipeline orchestration, and Feature Management & Experimentation were all affected. Google Cloud Platform experienced a multi-product incident in the us-west1 region affecting Bigtable, Compute…

  • +1 h 57 min

    Blames Google Cloud

    Minor incident

    BugsnagSessions processing delays

    …nd we are monitoring the results. Our session processing is currently slower because of a GCP Region service outage, and reporting will also experience elevated latency. We’re continuing to monitor th…

Also happening at the same time (not linked)

12 incidents from 12 vendors started in this window without naming Google Cloud or a linked vendor, and with no known dependency on them. Listed for context only; they are not counted as part of the event (an ordinary week has about 24 incidents in these hours).

Show all 10

Detected automatically from 9 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.