Google Cloud

cloud.google.com (opens in new tab)Status page (opens in new tab)

Status page says: Operational since Oct 19
Last 90 days: 3 incidents, 1 major or critical
Rewrites caught: None so far
Next deprecation: None announced

Google Cloud incidents per day, last 90 days

Select a day to jump to its incidents below.

How Google Cloud reports incidents

Not enough incidents to compare Google Cloud with other vendors yet: a vendor needs 20 incidents in a year and 10 with full update detail (Google Cloud has 7 and 7).

Provisional. Built nightly from every archived version of each incident, last on Oct 19. Compare all vendors

Dependencies

What Google Cloud relies on and who relies on Google Cloud, as observed in status-page incidents: who they blame, where they say they run, and who fails at the same time. Observed, not verified.

Who depends on Google Cloud

Vendor	Evidence	Signal
Confluent	blamed in 11 incidents; named as hosting in 72; integration affected in 1; together in 5 outage events “…Google Cloud Platform Outage Affecting Multiple Confluent Cloud Services All Confluent Cloud systems have recovered and the issues have been resolved. All operations should work normally as expected.…” incident	Strong
JFrog	blamed in 11 incidents; named as hosting in 12; together in 3 outage events “…JFrog Cloud Platform outage affecting subset of customers in GCP US region The service degradation affecting Artifactory uploads and downloads in the GCP US regions has been resolved. JFrog Engineers…” incident	Strong
Discord	blamed in 9 incidents; together in 1 outage event “…Service is working as expected at this time. Engineering has root-caused this issue to a Google Cloud component called "Traffic Director" which is responsible for configuring our load balancing layer…” incident	Strong
Grafana Cloud	blamed in 7 incidents; named as hosting in 34; integration affected in 4; together in 4 outage events “…bes in the US region All probes are back online. Engineering believes this was related to Google Cloud Provider issues.…” incident	Strong
CockroachDB	blamed in 7 incidents; named as hosting in 3; together in 3 outage events “…ted their public status page to indicate the underlying issue is resolved, and individual Google Cloud services are in the process of restoring full service. We are continuing to monitor the issue and…” incident	Strong
Dialpad	blamed in 6 incidents; together in 3 outage events “…a fix is being implemented. This incident has been resolved. We are aware of a widespread Google Cloud outage that began on June 12, 2025. As Dialpad relies on Google Cloud for certain functionalities…” incident	Strong
Elastic Cloud	blamed in 5 incidents; named as hosting in 56; integration affected in 2; together in 2 outage events “…GCP Elastic Cloud regions may be experiencing routing issues due to GCP provider networking issues We've confirmed that the Google Cloud Global Load Balancing incident has been resolved. Jul 17, 2018…” incident	Strong
imgix	blamed in 5 incidents; together in 3 outage events “…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…” incident	Strong
Sourcegraph	blamed in 5 incidents; together in 1 outage event “…s affecting Sourcegraph Cloud. This is related to an ongoing incident with our underlying Google Cloud infrastructure. Our team is actively monitoring the situation and working with Google Cloud as th…” incident	Strong
Pinecone	blamed in 4 incidents; named as hosting in 42; together in 2 outage events “…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…” incident	Strong
Gorgias	blamed in 4 incidents; named as hosting in 22; together in 3 outage events “…Helpdesk service disruption on us-east1-2607 What happened: Between 01:43 and 02:25 UTC, some customers experienced slow or failed Helpdesk responses and intermittent login issues. Impact was limited…” incident	Strong
Harness	blamed in 4 incidents; named as hosting in 3; together in 2 outage events “…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…” incident	Strong
Couchbase	blamed in 4 incidents; together in 1 outage event “…Capella Operations Impacted by GCP Global Network Resources issue The issue impacting Google Cloud Platform (GCP) Global Network Resources has been fully resolved. Capella Operational Cluster, App Ser…” incident	Strong
MongoDB Atlas	blamed in 3 incidents; named as hosting in 12; together in 1 outage event “…GCP capacity constraints affecting Atlas deployments We believe the symptoms of this have largely subsided, looking at both customer cases and our internal metrics. We will share any more information…” incident	Strong
FullStory	blamed in 3 incidents; integration affected in 1; together in 3 outage events “…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…” incident	Strong

And 45 more.

Outage events: Google Cloud us-central1, Sep 1.

Strong: same company, or blamed in two separate outages. Likely: blamed once, or named as hosting and failing together. Weak: listed as a subprocessor, integration-only, or failing together repeatedly without being named.