StatOSS

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.

cloudresourcemanager.googleapis.com/v1/projectsEvery 5 minutes

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
EuropeEurope157 ms
N. AmericaNorth America45 ms
AsiaAsia1,089 ms
OceaniaOceania504 ms

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
EuropeEurope159 ms
N. AmericaNorth America65 ms
AsiaAsia1,246 ms
OceaniaOceania626 ms

Medians over this range, on one scale up to 2,000 ms. Europe's places are scaled to Falkenstein, its fastest shared place.

Each bar of the first strip is one check, five minutes apart; each bar of the second is a day. Height is response time, red is a failed check, amber a timeout. Times are UTC, as of 2026-11-20 18:56 UTC.

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.

LastPassedChecksOutages
24 hours100%288 of 2880
7 days100%2,014 of 2,0140
30 days100%8,863 of 8,8630
90 daysNot 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.

FromMedian95th percentileMeanChecks
Falkenstein, Germany162 ms715 ms355 ms420
Helsinki, Finland728 ms883 ms688 ms42
Ashburn, USA52 ms137 ms71 ms502
Copenhagen, Denmark662 ms683 ms626 ms42
Singapore1,118 ms1,234 ms1,045 ms505
Sydney, Australia577 ms1,330 ms809 ms504

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.