Compute Engine SLA

Google Cloud · Compute · promises up to 99.99% · SLA of Mar 4, 2025 · checked 24h ago

1 major outage in the 208 days of history: 3.7 h counted, 99.927% observed against the 99.99% Instances in Multiple Zones (Premium Tier).

1 of 7 months fell below it (credits are claimed per month).

Last 90 days: 3.7 h counted, 99.83% observed.

Incidents, last 365 days

StartedIncidentCounted asDuration

Sep 1, 2026Multiple products in us-central1-b are experiencing network service degradation.us-central1Minor4.1 hSep 1, 2026 · 4.1 h
Aug 20, 2026We are investigating an issue where customers may experience timeouts, service degradations, errors, and elevated latencies across multiple products in the us-west1 region.global, us-west1Outage3.7 hAug 20, 2026 · 3.7 h

Major outage time per month

Allowed per month: 4.4 min

Commitments and credits

TierUptimeCredit of the monthly bill

Instances in Multiple Zones (Premium Tier)VMs across two or more zones in a region; Cloud Regions excluding Mexico and Stockholm99.99%below 99.99%: 10% · below 99%: 25% · below 95%: 100%
Instances in Multiple Zones (Premium Tier, Mexico and Stockholm)Multi-zone VMs in the Mexico and Stockholm regions99.95%below 99.95%: 10% · below 99%: 25% · below 95%: 100%
Instances in Multiple Zones (Standard Tier network)Multi-zone VMs on the Standard Network Service Tier99.9%below 99.9%: 10% · below 99%: 25% · below 95%: 100%
Single Instance, Memory Optimized familyA single memory-optimized VM (regions excluding Mexico and Stockholm)99.95%below 99.95%: 10% · below 95%: 25% · below 90%: 100%
Single Instance, all other familiesA single VM of any other machine family (all regions)99.9%below 99.9%: 10% · below 95%: 25% · below 90%: 100%

SLA changes

DateServiceChangeSource

Aug 29, 2023Compute EngineSingle Instance SLO raised from 99.5% to 99.9% (99.95% for memory-optimized family).Source
Apr 12, 2021Compute EngineSingle Instance SLO of 99.5% added (Jan 13, 2020 version had no single-instance commitment).Source
Apr 13, 2018Compute EngineCompute Engine SLO raised from 99.95% to 99.99%. Nov 30, 2017 version: 'Monthly Uptime Percentage to Customer of at least 99.95%'; April 13, 2018 version: 'at least 99.99%'.Source

More in compute

ServicePromisedFirst creditObserved 365dDowntime

Terms, exclusions and sources

Measured: Calendar month, per Project per Region (per instance for a Single Instance), per Network Service Tier
Credit cap: Will not exceed the amount due for the respective Covered Services in the Regions that did not meet SLO for the month
Claim window: Within 60 days from the time Customer becomes eligible
How to claim: Notify Google technical support; provide log files/identifying info showing Downtime Periods and when they occurred
Not covered: Features designated pre-general availability; Features excluded from the SLA in the Documentation; Errors caused by factors outside Google's reasonable control; Errors from Customer's or third-party software or hardware; Abuses or behaviors that violate the Agreement; Errors resulting from quotas applied by the system / listed in the Admin Console
Status history: Status history since Feb 27, 2026
Weighted uptime: All incidents, weighted: 99.488% · Downtime

Premium Tier Cloud Regions (excluding Mexico and Stockholm) ... Instances in Multiple Zones >= 99.99% ... 99.00% - < 99.99% (Premium Tier) 10% ... 95.00% - < 99.00% 25% ... < 95.00% 100%

Google Cloud, Last modified March 4, 2025. Read the SLA

Load balancing has the same 99.99% (Premium) / 99.9% (Standard) SLO. Downtime = loss of external connectivity or persistent disk access.

All Google Cloud SLAs How this is measured

Summaries of published SLAs; the contract you sign governs. Logos via logo.dev; trademarks belong to their owners.