GCP Cloud Vision SLA Credits & Refunds

Google Cloud publishes a service-specific SLA for Cloud Vision that describes exactly when an AI/ML workload qualifies for credits — and the thresholds are stricter than most teams realize. This guide breaks down the Cloud Vision 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 Vision uptime commitment and credit tiers
• Which incidents qualify (and which exclusions silently disqualify claims)
• How to file a Cloud Vision credit request inside the GCP claim window
• Why manual claim recovery typically leaves money on the table

Frequently asked questions about GCP Cloud Vision SLAs

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

Google commits to a 99.9% monthly uptime percentage for the Cloud Vision API. The SLA covers synchronous image annotation requests (label, OCR, face, object detection, etc.); if Google fails to meet this commitment during a billing cycle, you are eligible to receive a portion of your Cloud Vision spend back as a service credit.

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

Specifically for Cloud Vision, async batch operations (longRunningRecognize-style requests) and AutoML Vision custom-model serving are governed by separate terms — only synchronous Vision API errors from Google's side count toward the standard SLA.

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

AI/ML SLAs are still maturing, and Cloud Vision carries some of the most nuanced terms in the cloud catalog. Rate limits, queue depths, and model availability all get measured differently, and the SLA often excludes throttling that the provider deems "expected." Teams that successfully claim Cloud Vision credits do so by capturing per-request latency and error-code data and matching it precisely against the published terms.

Related GCP SLA guides

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

• GCP Vertex AI SLA credits — AI/ML
• GCP AutoML SLA credits — AI/ML
• 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 Cloud Vision 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 Vision 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.