Cloud Infrastructure
Google Cloud Platform SLA credit guide
What Google Cloud Platform owes you when it misses its uptime commitment — the credit tiers, the filing deadline, how to file, and a calculator to estimate your credit.
What SLA credit are you owed when Google Cloud Platform is down?
When GCP (generic service) falls below its 99.9% monthly uptime commitment, you're owed an SLA service credit worth 10%–50% of the affected service's monthly spend — larger the further uptime fell — claimable within 30 days of incident resolution. It's a credit toward a future invoice, not a cash refund.
Full Google Cloud Platform claim guide · What is an SLA credit? · SLA glossary
Uptime commitment
99.9%
Filing window
30 days
counted from incident resolution
Services with SLA data
5
Credit calculator
SLA target is 99.9% — enter what you actually observed.
Enter your monthly spend above to see the dollar credit for a 10% tier.
Estimate only, from the vendor’s published tiers — the final credit is set by the vendor against your actual invoice and their SLA definitions.
Credit tiers by service
| Measured uptime | Credit |
|---|---|
| 99% – under 99.9% | 10% of spend |
| 95% – under 99% | 25% of spend |
| below 95% | 50% of spend |
CLAIM WINDOWS ARE PER-SERVICE, NOT VENDOR-WIDE: Compute Engine gives 60 days from eligibility, while Cloud Storage, Cloud SQL and BigQuery give 30 — read the window off the specific service's SLA, never off a sibling's. Forfeiture runs from the time you become eligible for the credit. 50% per-service cap (of the covered service's monthly charge), except Compute Engine, whose own table pays 100% below 95.00%. File a Cloud Customer Care case WITH downtime log files. Delegated filing needs roles/cloudsupport.techSupportEditor (org/folder/project — NOT the billing account) + a paid Customer Care tier. Google Cloud claim windows are PER-SERVICE, not vendor-wide: Cloud Storage, Cloud SQL and BigQuery give 30 days, Compute Engine gives 60. This generic profile assumes the shorter 30 days deliberately, because filing early forfeits nothing and filing late forfeits everything — check the specific service's own SLA page, which may well give you longer.
| Measured uptime | Credit |
|---|---|
| 99% – under 99.99% | 10% of spend |
| 95% – under 99% | 25% of spend |
| below 95% | 50% of spend |
CLAIM WINDOWS ARE PER-SERVICE, NOT VENDOR-WIDE: Compute Engine gives 60 days from eligibility, while Cloud Storage, Cloud SQL and BigQuery give 30 — read the window off the specific service's SLA, never off a sibling's. Forfeiture runs from the time you become eligible for the credit. 50% per-service cap (of the covered service's monthly charge), except Compute Engine, whose own table pays 100% below 95.00%. File a Cloud Customer Care case WITH downtime log files. Delegated filing needs roles/cloudsupport.techSupportEditor (org/folder/project — NOT the billing account) + a paid Customer Care tier. BigQuery's claim window is 30 days ("...within 30 days...") — act quickly after breaches. The window is PER-SERVICE across Google Cloud, not vendor-wide: Compute Engine gives 60 days.
| Measured uptime | Credit |
|---|---|
| 99% – under 99.95% | 10% of spend |
| 95% – under 99% | 25% of spend |
| below 95% | 50% of spend |
CLAIM WINDOWS ARE PER-SERVICE, NOT VENDOR-WIDE: Compute Engine gives 60 days from eligibility, while Cloud Storage, Cloud SQL and BigQuery give 30 — read the window off the specific service's SLA, never off a sibling's. Forfeiture runs from the time you become eligible for the credit. 50% per-service cap (of the covered service's monthly charge), except Compute Engine, whose own table pays 100% below 95.00%. File a Cloud Customer Care case WITH downtime log files. Delegated filing needs roles/cloudsupport.techSupportEditor (org/folder/project — NOT the billing account) + a paid Customer Care tier. Cloud SQL's claim window is 30 days (its SLA spells it out: "...within thirty days...") — act quickly after breaches. The window is PER-SERVICE across Google Cloud, not vendor-wide: Compute Engine gives 60 days. These tiers are the 99.95 Enterprise edition; Enterprise Plus is a 99.99 SLA with a different bottom band.
| Measured uptime | Credit |
|---|---|
| 99% – under 99.95% | 10% of spend |
| 95% – under 99% | 25% of spend |
| below 95% | 50% of spend |
CLAIM WINDOWS ARE PER-SERVICE, NOT VENDOR-WIDE: Compute Engine gives 60 days from eligibility, while Cloud Storage, Cloud SQL and BigQuery give 30 — read the window off the specific service's SLA, never off a sibling's. Forfeiture runs from the time you become eligible for the credit. 50% per-service cap (of the covered service's monthly charge), except Compute Engine, whose own table pays 100% below 95.00%. File a Cloud Customer Care case WITH downtime log files. Delegated filing needs roles/cloudsupport.techSupportEditor (org/folder/project — NOT the billing account) + a paid Customer Care tier. Cloud Storage's claim window is 30 days ("...within 30 days...") — act quickly after breaches. This is a PER-SERVICE window across Google Cloud, not a vendor-wide one: Compute Engine gives 60 days.
| Measured uptime | Credit |
|---|---|
| 99% – under 99.99% | 10% of spend |
| 95% – under 99% | 25% of spend |
| below 95% | 100% of spend |
CLAIM WINDOWS ARE PER-SERVICE, NOT VENDOR-WIDE: Compute Engine gives 60 days from eligibility, while Cloud Storage, Cloud SQL and BigQuery give 30 — read the window off the specific service's SLA, never off a sibling's. Forfeiture runs from the time you become eligible for the credit. 50% per-service cap (of the covered service's monthly charge), except Compute Engine, whose own table pays 100% below 95.00%. File a Cloud Customer Care case WITH downtime log files. Delegated filing needs roles/cloudsupport.techSupportEditor (org/folder/project — NOT the billing account) + a paid Customer Care tier. Compute Engine's claim window is 60 DAYS, not the 30 the other Google Cloud SLAs give: "Customer must notify Google technical support within 60 days from the time Customer becomes eligible to receive a Financial Credit." The window is per-service across Google Cloud — Cloud Storage, Cloud SQL and BigQuery are 30 days — so do not read one service's deadline off another's.
How to file a Google Cloud Platform SLA credit claim
Portal: Google Cloud Support ↗
- Sign in to the Google Cloud project that was affected.
- Open Support → Cases → Create case (or email your account team if on a sales-assisted plan).
- Category: Billing → SLA credit. Paste the claim text from section 8.
- ⏰ THE WINDOW IS PER-SERVICE, NOT PER-VENDOR — check the SLA of the service you are claiming on, never a sibling's. Compute Engine gives 60 days ("Customer must notify Google technical support within 60 days from the time Customer becomes eligible to receive a Financial Credit"); Cloud Storage, Cloud SQL and BigQuery give 30. All of them run from the time you become ELIGIBLE for the credit, not from month-end. If you are unsure which applies, work to 30 days: filing early forfeits nothing, filing late forfeits the claim.
- Financial credit is applied to future invoices after Google verifies the SLA shortfall.
Evidence you’ll need
- •Project ID
- •Affected resources
- •Incident timestamps
- •Log files documenting the downtime + dates/times
Common exclusions
- •Scheduled maintenance windows
Frequently asked
What is Google Cloud Platform's SLA uptime commitment?
GCP (generic service) carries a 99.9% monthly uptime commitment.
How much credit can I claim if Google Cloud Platform misses its SLA?
Credits are tiered by measured uptime, from 10% up to 50% of the monthly service spend for the affected service, depending on how far below 99.9% availability fell.
What is the deadline to file a Google Cloud Platform SLA credit claim?
Claims are generally due within 30 days of incident resolution (verify the exact clause in Google Cloud Platform's SLA before filing).
Does Ontracko file Google Cloud Platform SLA credit claims for me?
Ontracko monitors Google Cloud Platform for free, detects SLA breaches automatically, and assembles the complete claim package (evidence + credit math + claim text). You file it; Ontracko charges 8% only on credits that are actually recovered.
Let Ontracko file it for you
Connect Google Cloud Platform and Ontracko monitors the SLA, catches every breach, and drafts the claim with the evidence attached. Free — 8% only on recovered credits.