GCP Cloud Functions SLA Credits & Refunds

Google Cloud publishes a service-specific SLA for Cloud Functions that describes exactly when a compute workload qualifies for credits — and the thresholds are stricter than most teams realize. This guide breaks down the Cloud Functions commitment, what Google considers a downtime period, and how to file a financial credit request through the Cloud Console.

What this guide covers

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

Frequently asked questions about GCP Cloud Functions SLAs

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

Google commits to a 99.95% monthly uptime percentage for Cloud Functions (covering both 1st-gen and 2nd-gen execution paths). If Google fails to meet this commitment during a billing cycle, you are eligible to receive a portion of your Cloud Functions spend back as a service credit.

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

Specifically for Cloud Functions, errors caused by your function code (exceptions, timeouts from your business logic, or memory-limit exhaustion you configured) are excluded — only platform-side invocation failures, cold-start regressions caused by Google, or trigger-delivery failures count.

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

Compute outages rarely show up cleanly. A Cloud Functions workload might be partially degraded — some instances fail, others stay healthy — and the SLA only counts the portion of capacity that was actually unavailable. To prove a claim you need per-instance (or per-task) error-rate data, not just an aggregate dashboard. Most teams discover this only when their first credit request comes back denied for "insufficient evidence."

Related GCP SLA guides

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

• GCP Compute Engine SLA credits — Compute
• GCP Cloud Run SLA credits — Compute
• GCP GKE SLA credits — Compute
• GCP Cloud Storage SLA credits — Storage

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

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