Provider trouble · Aug 20, 2026

6 companies posted about trouble at Google Cloud us-west1 (Oregon)

The first posted at Aug 20, 14:50 UTC, the last 2 hours later. 6 companies wrote about it in their own words.

Google Cloud posted on its own status page at 15:40 UTC, 50 minutes after the first company.

1,100 companies in our directory rely on Google Cloud.

Share on LinkedInShare on X

When they first posted

Companies by when their status page first showed it, 10 minutes a column. The most, 1, in Aug 20, 14:50–15:00 UTC.

Aug 20, 14:50 UTCAug 20, 17:10 UTC

What they said

Quoted from their status pages. Times are UTC.

  • Railway: “Deployments are slow”
  • Temporal: “Customers in (GCP) us-west1 may experience elevated API latencies”
  • Neo4j: “Aura metrics issue.”
  • LangChain: “[GCP US only] LangSmith Deployments Builds Outage”
  • Mailgun: “GCP Reporting Multi Service Outage in US-West1”
  • Confluent: “Elevated error rates and latency in GCP us-west1”

Google Cloud's page: its status, and who relies on it

Find out when the next one touches your vendors

Start with your domain. We read its DNS for the services it uses, you add the rest of your vendors, and we email you when one of them posts trouble on its status page, or when trouble like this reaches them.

Start with your domain

More moments

We found this one later, by running the same rules over the status-page posts we had kept from before Oct 20, 2026. Status pages say what each company chose to post; a company not listed may have had the same trouble and said nothing.