Google Cloud gives you the least time to claim of any major provider: 30 days from the incident, versus roughly 60 for AWS and two months for Azure. Combine that tight clock with a per-product SLA structure and it is easy to see why Google Cloud credits are the most frequently forfeited of the three. This guide covers the Google Cloud-specific process so a breach turns into a filed claim before the window closes. For the provider-agnostic version, read the complete claim guide; to price the credit first, use the SLA calculator.
Every product has its own SLA
There is no single Google Cloud SLA. Compute Engine, Cloud Storage, Cloud SQL, and the rest each publish their own document, their own Monthly Uptime target, and their own Financial Credit schedule. The first job is matching your outage to the correct product SLA:
| Product | Typical target | Notes |
|---|---|---|
| Compute Engine (multi-zone) | 99.99% | Instances across zones; single-zone carries a lower target |
| Cloud Storage (Standard, multi-region) | 99.95% | Varies by storage class and location type |
| Cloud SQL (HA configuration) | 99.99% | High-availability config; non-HA carries a lower commitment |
As with the other providers, configuration matters. A single-zone Compute Engine deployment does not carry the 99.99% commitment, so claiming that target against a single-zone resource gets the whole request thrown out. Confirm how the resource was deployed before you file.
Convert downtime to a percentage
Google Cloud grades on Monthly Uptime Percentage:
uptime % = (43,200 - downtime minutes) / 43,200 * 100
A 30-minute Compute Engine outage in a 30-day month is 99.93% uptime, which breaches a 99.99% target and lands in the first Financial Credit tier. If mapping minutes to tiers by hand is error-prone for you, the worked table in our downtime and uptime guide does the conversion for every common outage length.
Capture evidence before the 30-day clock runs
The short window makes speed the whole game. Capture on the day the incident resolves:
- The Google Cloud Service Health incident. Export the incident from the status dashboard: date, affected products, and regions. This is your least disputable artifact.
- Cloud Monitoring graphs. Uptime checks, availability, and error-rate panels covering the incident, with region and time zone visible.
- Resource identifiers. Instance names, project ID, zone, and region. Google evaluates claims per resource.
- A sample of failures. Failed request IDs or error logs aligned to the incident window.
Because you have only 30 days, do not wait for a formal post-incident review to open the claim. Start it the moment the incident is resolved.
Notify Cloud Support within 30 days
Google Cloud requires you to notify Cloud Support within 30 days of the incident. File through your support channel and write the request like an invoice, not a complaint:
- The product SLA by name: "Compute Engine Service Level Agreement."
- The month, project, and resources: billing month, project ID, affected instance names, zone, and region.
- The measured uptime and tier: "Measured Monthly Uptime Percentage of 99.93% falls below the 99.99% commitment, in the first Financial Credit tier."
- The requested credit: "The applicable percentage of the month's Compute Engine charges in the affected region: $760."
Attach the Service Health export and your Cloud Monitoring graphs. Keep the tone factual; the Financial Credit is a contractual remedy.
Confirm the Financial Credit posts
An approved Google Cloud Financial Credit is applied against a future invoice as a percentage of the affected product charges, usually within one to two billing cycles. Verify it lands. If Google rejects on an exclusion (maintenance, a factor outside its reasonable control, customer-caused issues), ask for the specific clause and re-check it against your Service Health record. Better evidence frequently reverses an exclusion call.
Google Cloud in the wider picture
Across a multi-cloud estate, Google Cloud is one clock among several, and it is the fastest to expire. The AWS and Azure guides cover their longer windows and different targets. For credit playbooks and negotiation tactics, see cloud-credits.com. Cross-reference the incident against the historical archive at clouddowntime.com/data, and set breach alerts at awsdown.com/alerts. If you are new to the flow, walk how it works first.
On a $30,000/month Google Cloud product footprint, even the first credit tier clears four figures for a single support notification. The only thing that reliably beats a Google Cloud claim is the 30-day clock. Beat it.