Skip to content
PulseWatchOUTAGE.INTEL
Google Compute Engine logo

Cloud Infrastructure

Is Google Compute Engine down right now?

UnknownOfficial status last polled Sep 7, 2026 15:54 UTCcloud.google.com/computeOfficial status page

Google Cloud virtual machine compute

Are you on the Google Compute Engine team and see something inaccurate? Report it to us. We respond within one business day.

Is Google Compute Engine down right now?

Unknown. Google Compute Engine does not have a conclusive current status. A single-runtime HTTP reachability check succeeded; no fresh official status confirms whole-service health. No current vendor status signal: vendor status was last polled on 2026-09-07, more than 7 days ago. The most recent attempt on 2026-10-12 could not be acquired.

Status as of Oct 12, 2026 17:38 UTC

Unknown

Google Compute Engine: status unknown

As of Oct 12, 2026 17:38 UTC

No product check is currently qualified to corroborate an incident for this service. Overall service status has not been established.

Reports 24h

0

Last incident

May 4, 2026 21:13 UTC

Trend

0/15m

Monitoring

Coverage gap

Observed health

Unknown

No samples qualify for a combined success and latency score.

Evidence strength

No current issue evidence

No current corroborated or observed finding.

Evidence describes support for an issue, not its outage probability.

How this score works

100 × successful samples within the latency target ÷ assessed samples. Targets use a historical operation-latency baseline and are heuristic. Server failures count as failed samples; successful responses without a qualified target are shown separately. Only named operations are measured. Vendor statements, report volume, forecasts and incident records do not add score points.

A component issue stays visible even when other operations pass. Forecasts are separate from current health.

30 days incident history

Daily incident severity and duration for Google Compute Engine.

0

Incident days

30

No recorded incident

0 min

Recorded duration

No recorded incident — health unknownLow or mediumHigh or critical
Recorded incidents remain visible regardless of current monitoring status. Days without records do not establish historical coverage or healthy service.
Showing available records within the selected range.

30-day outage frequency

Recorded incidents per day and recorded incident duration for Google Compute Engine. Hover a day for detail.

Sep 13Sep 18Sep 23Sep 28Oct 3Oct 801234

Green baseline markers mean no recorded incident. These records do not establish historical monitoring coverage or verified uptime.

0

Days with incidents

0 incidents

Busiest day

0 min

Recorded duration

Report volume

0 reports in last 24H

05:30 PM09:00 PM12:30 AM04:00 AM07:30 AM11:00 AM02:30 PM00.511.52baseline 2

Issue types

No data

Top cities

No location data

Top providers

No provider data

Auto-drafted postmortem

Google Compute Engine outage on May 4 — 33-minute disruption

May 4, 08:39 PM → May 4, 09:13 PM · 33 minutes · high

On May 4, 2026, Google Compute Engine experienced a service disruption. This incident, which was detected through user reports, began at approximately 20:39 UTC and was fully resolved by 21:13 UTC, lasting 33 minutes.

Peak reports
5
in 15 min
Total reports
6
during the incident
Duration
33 minutes
tracked by PulseWatch

Impact

The disruption to Google Compute Engine was identified through user reports, with a total of 6 reports received during the incident. Users primarily reported issues related to API functionality, accounting for 4 of the reports, and some users also experienced the service as being down, making up 2 reports. No specific regional impact was recorded during this period. The incident was classified as high severity based on the nature of the reported issues.

Top reported issues

  • API issues4
  • Website down2

Incident timeline

  1. May 4, 08:39 PM

    PulseWatch detected elevated report volume (high severity)

  2. May 4, 09:00 PM

    Peak of 0 reports in 15 minutes (baseline 1.5)

  3. May 4, 09:13 PM

    Report volume returned to baseline — incident resolved

Official updates

  1. May 4, 08:39 PM

    Google Compute Engine status page acknowledged the incident.

    View official source
  2. May 4, 09:13 PM

    API issues clustered from 2 sources across 5 signals. Suppressed 4 redundant alerts and flagged flapping behavior.

Draft auto-generated by PulseWatch when the incident resolved. Based on aggregated user-report signals and the sources listed above.

Reliability

Not measured

30-day uptime

n/a

90-day uptime

n/a

Not calculated: Google Compute Engine is unknown, so there is no incident history to measure and no uptime figure is shown.

Other cloud infrastructure services we monitor

Browse all

Community reports

0 comments

Confirm what you're seeing — your report helps others know if it's just them.

500 characters left

Be the first to post a report.

Incident timeline

Scrub through detection, peak, status updates, and resolution.

Full history →
ResolvedHigh

Google Compute Engine: grouped 5 related API issues alerts into one incident to reduce noise.

5/4/2026, 8:39:44 PM · 33 min

08:39 PM09:13 PM
Detection5/4/2026, 8:39:44 PM · 5mo ago

Detected — high severity

Google Compute Engine: grouped 5 related API issues alerts into one incident to reduce noise.

ResolvedHigh

Google Compute Engine: grouped 5 related API issues alerts into one incident to reduce noise.

5/3/2026, 9:54:43 PM · 28 min

09:54 PM10:23 PM
Detection5/3/2026, 9:54:43 PM · 5mo ago

Detected — high severity

Google Compute Engine: grouped 5 related API issues alerts into one incident to reduce noise.

ResolvedHigh

Google Compute Engine: grouped 5 related API issues alerts into one incident to reduce noise.

5/3/2026, 9:54:43 PM · 23 min

09:54 PM10:18 PM
Detection5/3/2026, 9:54:43 PM · 5mo ago

Detected — high severity

Google Compute Engine: grouped 5 related API issues alerts into one incident to reduce noise.

ResolvedHigh

Google Compute Engine incident correlated across 1 signal group: official/vendor.

5/3/2026, 10:13:02 AM · 19 min

10:13 AM10:32 AM
Detection5/3/2026, 10:13:02 AM · 5mo ago

Detected — high severity

Google Compute Engine incident correlated across 1 signal group: official/vendor.

ResolvedHigh

Google Compute Engine: grouped 5 related API issues alerts into one incident to reduce noise.

5/2/2026, 11:24:42 PM · 28 min

11:24 PM11:53 PM
Detection5/2/2026, 11:24:42 PM · 5mo ago

Detected — high severity

Google Compute Engine: grouped 5 related API issues alerts into one incident to reduce noise.

DetectionPeakStatus updateResolvedCrowd warning

Subscribe to updates

Get an email the moment Google Compute Engine enters an incident — and again when it's resolved. No account required.

Free for anyone. Unsubscribe anytime from any email we send.

Signal quality

Live signal

Status
Unknown
Monitoring
A single-runtime HTTP reachability check succeeded; no fresh official status confirms whole-service health. No current vendor status signal: vendor status was last polled on 2026-09-07, more than 7 days ago. The most recent attempt on 2026-10-12 could not be acquired.
Coverage
Reachability and crowd signals only; not independently verifiable
Reports (24h)
0
Baseline / hour
6
Open threshold
3x

Official site

cloud.google.com/compute