Skip to main content
gcpdown

About GCPDown

GCPDown answers one question faster and more clearly than anyone else: is Google Cloud down right now? - and then explains what broke, why, and what to do about it. The site is written for the platform and DevOps teams who own the on-call rotation and the postmortem, with a bias toward GKE and Kubernetes reliability.

How status is measured

The status you see is generated by our own ingestion pipeline, which polls public Google Cloud health data (the Google Cloud Service Health dashboard) every 60 seconds, normalizes events per product and region, and stores every incident with its full update timeline. The live pill on the homepage and the per-service pages on /status reflect the most recent check, with the timestamp shown next to the pill. We do not guess from social media reports.

“Operational” means our latest check found no active incident for that product. Severity levels (minor / major / critical) follow the impact language Google itself uses, and each product page charts the last 90 days of incident history so a green pill has context.

How post-mortems are researched

Analyses in the outage archive are compiled from primary sources: Google’s official incident reports on the Service Health dashboard, the incident’s own status-page timeline, and reproducible technical detail from engineering write-ups. Every post-mortem lists its sources, shows a published and last-updated date, and separates established fact from our analysis. When Google publishes a correction, we update the analysis and bump the visible date.

Who is behind this

GCPDown is operated by the team at Next Signal, whose monitoring platform powers the status checks and the free outage alerts. That relationship is disclosed wherever Next Signal is recommended. GCPDown is not affiliated with, sponsored by, or endorsed by Google; Google Cloud product names are used for identification.

Corrections

If we got a fact wrong, we want to know. Corrections are applied in place with the last-updated date bumped, so the record is transparent.