Frequently asked questions

Check the live answer at the top of our homepage. It re-checks public Google Cloud health data every 60 seconds, and if a product is impaired you will see the affected products and regions, plus a link to the full incident timeline.

We continuously poll the official Google Cloud Service Health dashboard and combine it with our own independent probes and community signals. When impact is confirmed we open an incident and can email subscribers within a minute or two.

No. GCPDown is an independent monitoring site and is not affiliated with, endorsed by, or sponsored by Google. Google Cloud and product names are used only for identification.

Identity and Cloud networking are shared control-plane dependencies, so when they degrade, authentication and traffic routing fail across products that are otherwise healthy. That is why one incident can ripple far beyond the product that broke.

Degraded means elevated errors or latency with partial functionality, so many requests still succeed. An outage means a product or region is substantially unavailable. We roll individual product statuses up to a single overall answer.

We track the major compute, container, storage, database, networking, and data products (Compute Engine, GKE, Cloud Storage, Cloud SQL, BigQuery, Cloud Networking, IAM and more) across the Google Cloud regions worldwide.

Our status reflects our own checks plus public Google Cloud health data, so it can differ from, and sometimes lead, Google official dashboard, which is occasionally slow to update. Every incident links back to the official source so you can verify.

Possibly. Google Cloud product SLAs (for example Compute Engine, Cloud SQL, and Cloud Storage) pay financial credits when monthly uptime drops below a threshold. Eligibility depends on the product, the affected region, and your usage. Each of our post-mortems notes likely SLA eligibility.

Credits are not automatic. You generally have to file a claim with evidence within a window of the incident. Work out what you are owed with the independent SLA credit calculator at cloudslacredit.com, or automate breach detection with Next Signal.

Subscribe to free outage alerts. You get one email when an incident is detected, with the affected products and regions, and one when it resolves. You can scope alerts by product, region, and severity.

Our /outages archive has detailed post-mortems of major incidents (timeline, root cause, business impact, SLA eligibility), and every analysis links back to the official Google Cloud incident reports.

Yes. We maintain plain-language post-mortems of landmark events, explaining what broke, how long it lasted, and what it means for your architecture and your SLA-credit claims.