Provider trouble · Sep 1, 2026
14 companies posted about trouble at Google Cloud us-central1 (Iowa)
The first posted at Sep 1, 14:49 UTC, the last 2 hours later. 14 companies wrote about it in their own words.
Google Cloud posted on its own status page at 14:42 UTC, 7 minutes before the first company.
1,100 companies in our directory rely on Google Cloud.
When they first posted
Companies by when their status page first showed it, 10 minutes a column. The most, 3, in Sep 1, 15:30–15:40 UTC.
What they said
Quoted from their status pages. Times are UTC.
- Ampcode: “Amp unavailable due to Google Cloud incident”
- Elastic: “Issue impacting services running in GCP us-central1”
- Full Story: “Multiple Fullstory Services Unavailable (NA1 Data Center)”
- Wunderkind: “Email & Text Send Disruption”
- Sigma Computing: “Widespread failures are preventing Sigma from loading for GCP-hosted organizations.”
- Noibu: “Access to the Noibu Console is down”
- Anecdotes: “Service Disruption”
- Temporal: “Elevated error rates in GCP us-central1”
- Clerk (clerk.com): “GCP incident in us-central1-b”
- Expo: “Problems with API and website availability”
- Torq: “[US] - Elevated error rates in US Data Center”
- Confluent: “Investigating Elevated Errors in GCP us-central1”
- Jasper: “Elevated errors caused by a Google Cloud incident”
- AppOmni: “Intermittent outages in US tenants due to Google Cloud Platform incident”
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 domainMore 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.