GCP Firestore SLA Credits & Refunds

Google's database SLAs — Firestore included — are written around "Monthly Uptime Percentage" with credit tiers that step up as availability drops. This guide explains the Firestore 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 Firestore uptime commitment and credit tiers
• Which incidents qualify (and which exclusions silently disqualify claims)
• How to file a Firestore credit request inside the GCP claim window
• Why manual claim recovery typically leaves money on the table

Frequently asked questions about GCP Firestore SLAs

What is the typical SLA uptime guarantee for GCP Firestore?

Google publishes tiered uptime commitments for Firestore: 99.999% monthly uptime for multi-region database locations and 99.99% for regional database locations. The tier is fixed by the location you chose at database creation time and cannot be changed after the fact.

How do I claim GCP Firestore 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 Firestore 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 Firestore SLA?

Specifically for Firestore, errors caused by hot-spotting from your write patterns, contention on the same document, or exceeding the 1-write-per-second per-document soft limit are excluded — only Google-side regional unavailability counts.

Why is it difficult to get refunds for Firestore outages manually?

Database SLAs get complicated because read availability, write availability, and replication health are often measured separately. A Firestore 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 SQL SLA credits — Database
• GCP Cloud Spanner SLA credits — Database
• GCP BigQuery SLA credits — Database
• GCP Compute Engine SLA credits — Compute

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

GCP's claim deadline for Firestore 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 Firestore 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.