GCP Cloud SQL SLA Credits & Refunds

Google's database SLAs — Cloud SQL included — are written around "Monthly Uptime Percentage" with credit tiers that step up as availability drops. This guide explains the Cloud SQL SLA in plain terms, calls out the exclusions that most often defeat claims, and shows how automated monitoring sidesteps the manual evidence problem.

What this guide covers

• The official GCP Cloud SQL uptime commitment and credit tiers
• Which incidents qualify (and which exclusions silently disqualify claims)
• How to file a Cloud SQL credit request inside the GCP claim window
• Why manual claim recovery typically leaves money on the table

Frequently asked questions about GCP Cloud SQL SLAs

What is the typical SLA uptime guarantee for GCP Cloud SQL?

Google commits to a 99.95% monthly uptime percentage for Cloud SQL instances configured for high availability (HA / regional with a failover replica). Zonal (single-zone) instances are explicitly not covered by an availability SLA. If Google fails to meet the HA commitment during a billing cycle, you are eligible to receive a portion of your Cloud SQL spend back as a service credit.

How do I claim GCP Cloud SQL SLA credits after an outage?

File a Financial Credit Request through Google Cloud Support within 30 days of the end of the affected billing month — the deadline is shorter than AWS or Azure, which catches a lot of teams out. Include your Project ID, the affected Cloud SQL resources, downtime intervals (with timezone), supporting evidence from Cloud Monitoring or your own observability stack, and a calculation showing where Monthly Uptime Percentage fell below the SLA threshold. Google issues approved credits against your billing account, not as cash refunds.

What exclusions apply to the GCP Cloud SQL SLA?

Specifically for Cloud SQL, downtime during instance maintenance windows you accepted, and any outage on zonal (non-HA) instances, are excluded from the SLA — only HA-configured regional instances accumulate covered downtime.

Why is it difficult to get refunds for Cloud SQL outages manually?

Database SLAs get complicated because read availability, write availability, and replication health are often measured separately. A Cloud SQL outage that prevents writes but allows reads may qualify for a partial credit, or none at all, depending on the precise wording. The evidence required (query error rates, connection failures, replication lag from your monitoring) has to match the SLA's definition of unavailability exactly.

Related GCP SLA guides

Other Google Cloud services with their own published SLA and 30-day claim window:

• GCP Cloud Spanner SLA credits — Database
• GCP BigQuery SLA credits — Database
• GCP Firestore SLA credits — Database
• GCP Compute Engine SLA credits — Compute

Don't miss GCP's 30-day claim window

GCP's claim deadline for Cloud SQL is the shortest of the three major clouds, and most teams miss it for the same reason: nobody owns "file SLA credit requests" as a recurring task. By the time finance closes out the month, the window is already gone.

Next Signal monitors Cloud SQL availability, files the Financial Credit Request inside Google's deadline, and tracks the claim through resolution. See how it works or start a free trial.