Google Cloud SLA Credit Requirements and Claim Deadlines
| Applicable service | Compute Engine - Instances in Multiple Zones (Premium Tier) |
|---|---|
| Official SLA source | https://cloud.google.com/compute/sla |
| Availability target | 99.99% |
| Measurement period | calendar month, per Project per Region |
| Credit tiers / formula | 10% when uptime is below 99.99% and at or above 99%; 25% when uptime is below 99% and at or above 95%; 100% when uptime is below 95% and at or above 0% |
| Claim window (verified text) | Customer must notify Google technical support within 60 days from the time Customer becomes eligible to receive a Financial Credit. |
| Evidence requirements | Log files showing Downtime Periods; Date and time each Downtime Period occurred |
| Official submission procedure | Notify Google technical support within 60 days of becoming eligible and provide log files showing Downtime Periods and the date and time they occurred (per the SLA page). Financial Credits are applied within 60 days after the Financial Credit was requested (per fetched page). |
| Important exclusions | SLA does not apply to pre-GA features, features excluded in associated Documentation, or errors caused by factors outside Google's control (summary per fetched page; see official document for full text). |
| Monitoring limitations | CreditClaim monitors the vendor's official public status feed (https://status.cloud.google.com/incidents.json). A public incident is not, by itself, proof that your service breached its SLA; eligibility requires your measured uptime and the evidence above. |
| Last verification date | 2026-10-27 |
| Source content hash (SHA-256) | 8db0d4ad202b430ba449f7534b3038eb419d6f1a4c9ac766c09f576390b3bbfa |
| Verification status | VERIFIED |
Downtime for VMs means loss of external connectivity or persistent disk access; a Downtime Period is one or more consecutive minutes; partial/intermittent downtime under one minute does not count (per fetched page).