Google Cloud uptime
Google Cloud, checked by StatOSS every 5 minutes from Helsinki in Finland, Falkenstein in Germany, Copenhagen in Denmark, Ashburn in the USA, Singapore and Sydney in Australia. Measured from outside, with every outage dated in UTC.
Google Cloud is up.
Up for 51 d 10 h. Last checked 2026-11-20 18:53 UTC from Falkenstein, Germany: 401 in 146 ms.
Last 24 hours
Up for 51 d 10 h100% passed
287 checks, median 157 ms from Falkenstein, all passed
95% under 669 ms
Response time by region
Medians over this range, on one scale up to 1,500 ms.
Last 90 days
Up for 51 d 10 h100% passed
14,805 checks, median 159 ms from Falkenstein, all passed
95% under 703 ms
Response time by region
Medians over this range, on one scale up to 2,000 ms. Europe's places are scaled to Falkenstein, its fastest shared place.
In the last 30 days Google Cloud passed 8,863 of 8,863 checks, 100%.
No outage since checks began on 30 Sep 2026.
Availability
The share of checks that passed, and the outages that began, in each window up to now.
| Last | Passed | Checks | Outages |
|---|---|---|---|
| 24 hours | 100% | 288 of 288 | 0 |
| 7 days | 100% | 2,014 of 2,014 | 0 |
| 30 days | 100% | 8,863 of 8,863 | 0 |
| 90 days | Not enough history yet: checks began on 30 Sep 2026 | ||
A year of checks is kept; the year's figure appears here once there is a year of them.
Response time by location
Over the last 7 days, from the checks that passed: the time from the start of the request to the answer's headers, with the DNS lookup, the connection and TLS included.
| From | Median | 95th percentile | Mean | Checks |
|---|---|---|---|---|
| Falkenstein, Germany | 162 ms | 715 ms | 355 ms | 420 |
| Helsinki, Finland | 728 ms | 883 ms | 688 ms | 42 |
| Ashburn, USA | 52 ms | 137 ms | 71 ms | 502 |
| Copenhagen, Denmark | 662 ms | 683 ms | 626 ms | 42 |
| Singapore | 1,118 ms | 1,234 ms | 1,045 ms | 505 |
| Sydney, Australia | 577 ms | 1,330 ms | 809 ms | 504 |
Outages
None detected since checks began on 30 Sep 2026.
What is checked
Google's cloud: Compute Engine, Cloud Run, GKE, Cloud Storage, BigQuery and the APIs behind them.
StatOSS sends GET https://cloudresourcemanager.googleapis.com/v1/projects and counts the check as passed on status 401 within 10 seconds. The Resource Manager API's list of projects on googleapis.com, the address gcloud and the client libraries call. Without credentials it answers 401.
It checks the API front end and one API. Workloads running on Google Cloud, and other APIs, can fail on their own.
Google Cloud reports its own incidents at status.cloud.google.com. The figures here are measured from outside and can differ from it in both directions.
How it is measured
- One check every 5 minutes, from one location at a time in turn: Helsinki in Finland, Falkenstein in Germany, Copenhagen in Denmark, Ashburn in the USA, Singapore and Sydney in Australia.
- A check fails when no answer comes within 10 seconds, when the connection or TLS fails, or when the answer is not status 401.
- A failed check is repeated at once from a second location, and counts only when that location fails too, or cannot answer within 20 seconds.
- Two failed checks in a row make an outage, dated from the second, and the first check that passes ends it. A failure shorter than 10 minutes may not make one, and times are good to about 5 minutes.
- Availability is the share of checks that passed. There are no maintenance windows: every check counts.
It is the same check a StatOSS status page runs for its owner, with the same rules; the docs on checks have the details.