Cloud SQL runs managed MySQL, PostgreSQL, and SQL Server - and sits at the bottom of most request paths, so a few minutes of connection failures cascade into full application outages upstream. Incidents typically look like connection failures to a subset of instances, slow failovers, or maintenance surprises rather than region-wide loss.
Connection failures or timeouts to a subset of instances in one region
High-availability failovers taking longer than the expected ~60–120 seconds
Storage or IOPS degradation making queries slow, not failed
Connectivity-path issues (Cloud SQL Auth Proxy, Private Service Connect) that look like database outages
Cloud SQL questions
Is Cloud SQL down right now?+
Check the live status above. If Cloud SQL shows Operational but your database is unreachable, check whether an HA failover just moved your instance, and verify the auth-proxy/connector path - connector failures are indistinguishable from database failures to your app.
Does high availability protect me from Cloud SQL outages?+
An HA (regional) instance survives zone failures via automatic failover with a brief interruption. It does not protect against region-level events or issues in the shared control plane - for those you need cross-region read replicas and a promotion runbook you have actually tested.
What SLA does Cloud SQL carry?+
HA-configured instances carry a 99.95% monthly uptime SLA (Enterprise Plus edition targets 99.99%). Single-zone instances carry no SLA. Credits are tiered, must be claimed within 30 days, and cap at 50% of the monthly charge.
Get alerted when Cloud SQL breaks
Instant email the moment we detect an incident - affected services and regions included.
gcp