---
title: "GCP Compute Engine (us-central1) uptime and outage history"
description: "GCP Compute Engine (us-central1) was available 99.98% of the last 30 days, measured independently from 5 locations. Outage history and latency."
url: https://uptimeproject.org/service/gcp-compute-us-central1/
built: 2026-11-06T12:58:15.145Z
---

# GCP Compute Engine

us-central1 Operational

[Official site](https://cloud.google.com/compute) [Provider status](https://status.cloud.google.com/)

Google Cloud · Cloud / IaaS

Updated 2026-11-06 12:58 UTC

24h availability

100.00%

0 min down

7d availability

99.97%

1 min down

30d availability

99.98%

4 min down

90d availability

99.98%

10 min down

Period:    

Avg response time 117ms

90d: 10 min down, 9 min degraded, 7 min unmeasured

## Recent incidents

[All incidents](https://uptimeproject.org/incidents/) [Atom feed](https://api.uptimeproject.org/v1/services/gcp-compute-us-central1/incidents.atom)

Recent incidents for GCP Compute Engine (us-central1)
| Started (UTC) | Worst status | Duration | Down | Degraded |
| --- | --- | --- | --- | --- |
| 2026-11-04 23:16 | Down | 2 min | 1 min | 1 min |
| 2026-10-21 06:06 | Down | 2 min | 2 min | 0 min |
| 2026-10-15 21:06 | Down | 3 min | 1 min | 2 min |
| 2026-09-18 22:31 | Down | 2 min | 2 min | 0 min |

## Vantage points

Falkenstein, DE Hetzner

161ms Operational

Roubaix, FR OVH

133ms Operational

New York, US DigitalOcean

56ms Operational

Seattle, US Vultr

70ms Operational

Singapore Vultr

233ms Operational

## What we monitor

2 active checks

Each row below is one probe-side measurement we run from every vantage point. The availability number on this page is the consensus across these checks, not a single endpoint hit.

-   HTTP `https://redacted-uc.a.run.app/` every minute
-   TLS `redacted-uc.a.run.app:443` every hour

## About this data

Availability is measured independently by probes in five locations. Each probe runs the appropriate mix of HTTP, DNS, TLS, and storage checks at per-check cadences and records timing, status code, and any error. A probe votes "up" for a given minute if any of its checks for this service succeeded; the minute is then counted as "up" on the leaderboard only when a strict majority of reporting probes voted up. Minutes where fewer than three probes reported are excluded from the denominator. [Full methodology](https://uptimeproject.org/methodology/)

## Embed a badge

Markdown for a README. The image is served by the public API and links back to this page.

          `[![GCP Compute Engine (us-central1) uptime](https://api.uptimeproject.org/v1/services/gcp-compute-us-central1/badge.svg)](https://uptimeproject.org/service/gcp-compute-us-central1/)`

[Back to Cloud / IaaS leaderboard](https://uptimeproject.org/category/iaas/)

Live data: https://api.uptimeproject.org/v1/services/gcp-compute-us-central1