GCP Pub/Sub SLA Credits & Refunds

Pub/Sub on GCP is covered by Google's standard service-credit framework, but the per-product thresholds vary and the claim process is documented in pieces across Cloud Support and the SLA terms. Here's the consolidated Pub/Sub version: uptime targets, exclusions, and how to recover credits without grinding through a multi-week support thread.

What this guide covers

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

Frequently asked questions about GCP Pub/Sub SLAs

What is the typical SLA uptime guarantee for GCP Pub/Sub?

Google commits to a 99.95% monthly uptime percentage for Pub/Sub (covering both publish and pull/push subscription delivery on global topics). Pub/Sub Lite, a regional product, is governed by a separate, lower-tier SLA — confirm which SKU you are running. If Google fails to meet the applicable commitment, you are eligible for a service credit.

How do I claim GCP Pub/Sub 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 Pub/Sub 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 Pub/Sub SLA?

Specifically for Pub/Sub, push subscriptions that fail because your endpoint is down or returns non-success codes are excluded — only failures in Google's publish acknowledgement and pull-delivery paths qualify.

Why is it difficult to get refunds for Pub/Sub outages manually?

Networking incidents are the easiest to misclassify. A Pub/Sub disruption might really be a DNS resolution issue, an upstream peering problem, or a TLS certificate failure — and the SLA only covers what the provider's own infrastructure caused. Distinguishing a true Pub/Sub outage from a downstream symptom requires correlated telemetry across multiple layers, which is exactly the data manual claim filers tend to miss.

Related GCP SLA guides

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

• GCP VPC SLA credits — Networking
• GCP Cloud CDN SLA credits — Networking
• GCP Compute Engine SLA credits — Compute
• GCP Cloud Storage SLA credits — Storage

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

GCP's claim deadline for Pub/Sub 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 Pub/Sub 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.