Google Cloud status: is it down right now?
Our own check of cloud.google.com from Europe and the US, every 3 minutes, with recent history.
cloud.google.com responded. The page answered normally in 174 ms.
cloud.google.com responded.
The page answered normally in 174 ms.
Checked (2 minutes ago) from Europe and the US, automatic every 3 minutes.
Run a website? Hear about it before your visitors do.
Google Cloud is up right now. Visual Sentinel watches your own site the same way and alerts you when a check fails or the page looks broken. Add your address and we'll check it now. No account needed.
This checks the response from cloud.google.com. It does not test playback, login or every Google Cloud feature.
Google Cloud status history
Our own checks from Europe and the US. Green means every check passed, amber means some checks failed, red means most checks in that period failed.
Outages our checks detected
None since Oct 13. A problem has to fail two checks in a row before we record it.
Watch your own site
This page is for their outage. Your own site can fail the same way. See its first check free, then try a paid plan for 7 days (card required).
Monitor my siteabout this service
About Google Cloud
Google Cloud Platform (GCP) runs Compute Engine, Google Kubernetes Engine (GKE), Cloud Run, Cloud Functions, Cloud Storage, BigQuery, Firestore, Spanner, Vertex AI, and dozens of other services across multiple regions globally. GCP outages tend to be scoped per service per region, similar to AWS. BigQuery outages are particularly visible because analytics teams see dashboards and ETL pipelines fail simultaneously. GKE control-plane outages block deployments but leave running pods alive. Notable GCP incidents have had wide blast radius because several global services (Cloud CDN, Load Balancing, IAM) share underlying infrastructure across regions.
The official Google Cloud status page is available as a reference. Official pages are useful, but they can lag behind real outages by minutes or hours.
outage patterns
What outages typically look like on Google Cloud
Cloud platforms like Google Cloud rarely fail in obvious, all-or-nothing ways. The more common pattern is regional degradation: one availability zone or geographic region runs at half capacity while the rest of the platform serves traffic normally. Status pages often show green because the aggregate health check is still passing, even when a customer's specific workload is degraded.
The live tool above checks the public cloud.google.com endpoint from EU and US and compares status and response time. That can reveal a regional reachability problem, but it cannot prove that every Google Cloud product, API, or customer workload is healthy. Use the provider status reference and test the specific workflow you depend on before drawing a broader conclusion.
Common signs Google Cloud is having issues
- Temporarily unavailable pages or requests timing out during normal browsing
- Sustained response-time drift above the Google Cloud baseline (usually a precursor to hard failures)
- TLS handshake delays during peak hours that resolve at quieter times
- Regional disparity: one geography returns errors while another stays healthy
What to do when Google Cloud is degraded
If Google Cloud appears degraded, compare the EU and US endpoint results, open the provider status reference, and test the exact region and workflow your system uses. Preserve failed request IDs and timestamps for support. If only one region fails, use an alternate region only when your own failover policy permits it.
monitor 24/7
Monitor Google Cloud automatically.
Get independent uptime alerts when the public Google Cloud endpoint fails a confirmed check. Solo and Starter check every 5 minutes; Business and Agency check every 60 seconds.
5-minute checks from Solo
Business and Agency support 60-second uptime checks.
Multi-region
EU & US checks. Catch regional outages.
Alerts where you work
Email and push on every plan, plus team and incident channels by plan.
free first check · 7-day trial, card required · from $15/month
why independent monitoring
Provider status references
and endpoint checks answer different questions.
Independent endpoint evidence
The regional check can show that a public endpoint is failing before or after a provider posts broader incident context. It does not validate every product subsystem.
Scheduled alerts
Monitor Google Cloud on your plan interval and route confirmed endpoint failures through the notification channels available to your workspace.
Multi-region verification
EU and US results can reveal a regional difference in public-endpoint reachability. Confirm the exact workflow and provider region you use.
Historical data
Track Google Cloud uptime over time. See trends, identify recurring issues, and make informed decisions about your dependency.
Frequently asked questions
Is Google Cloud down right now?
See the latest check of cloud.google.com and its timestamp at the top of this page. If Google Cloud is down, you can also check the official status page for extra context.
How do I check if Google Cloud is having issues?
This page checks the public Google Cloud endpoint from EU and US. You can also monitor that endpoint on a schedule and receive confirmed-failure alerts through the channels available on your plan. Test the exact provider feature you use for a complete diagnosis.
How can I get alerted when Google Cloud goes down?
Add cloud.google.com to Visual Sentinel and its first check is free. To keep monitoring, start a 7-day trial (card required) or subscribe now: Solo and Starter check every 5 minutes, Business and Agency every 60 seconds, with email, push and chat alerts.
Where can I find Google Cloud outage context?
The official Google Cloud status page is available as a reference. Official pages are useful, but they can lag behind real outages by minutes or hours. Visual Sentinel checks the public Google Cloud endpoint independently from EU and US. Paid Business and Agency plans support 60-second uptime checks.
Why do GKE clusters keep running during a GKE control-plane outage?
GKE splits the control plane (where kubectl commands hit) from the data plane (where workloads run). Control-plane incidents block new deployments, rolling updates, and kubectl access, but existing pods continue serving traffic because node-level kubelets operate independently.
Does BigQuery downtime affect data stored in Cloud Storage?
No. Cloud Storage and BigQuery are separate services with separate data paths. BigQuery queries that read from Cloud Storage (external tables, federated queries) fail during BigQuery outages, but the underlying data stays accessible via Cloud Storage APIs and other tools (e.g. gcloud storage, Spark).
Often checked together with Google Cloud
Many sites and apps run on these platforms, so one cloud problem can affect services that look unrelated.