# Cloud Run GPUs > Cloud Run GPUs attach one NVIDIA L4 or RTX PRO 6000 Blackwell GPU to a Cloud Run service, job or worker pool, so a container serves models serverlessly, billed per second and able to scale to zero. - Canonical: https://www.anchorterminal.com/tools/cloud-run-gpus - Pricing: https://www.anchorterminal.com/tools/cloud-run-gpus#pricing - Reviews: https://www.anchorterminal.com/tools/cloud-run-gpus#reviews - Markdown: https://www.anchorterminal.com/tools/cloud-run-gpus.md (~7,600 tokens) - Slim: https://www.anchorterminal.com/tools/cloud-run-gpus.min.md (~1,480 tokens, same facts, less prose, for token-sensitive contexts) - JSON: https://www.anchorterminal.com/tools/cloud-run-gpus.json (this page as data, same URL with Accept: application/json) - Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt) - API: https://www.anchorterminal.com/api/v1/index.json - MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key) - DNS: dig +short TXT cloud-run-gpus.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.. and .vs.. under the zone, and the same under grade.letme.dev) - Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data) - Updated: 2026-11-07 ## Overview **Grade B · 68.4/100 · rank #288 of 1486 · #2 in GPU & serverless compute · not agent-ready · confidence medium** More from Google Cloud, listed separately because each is its own product: [Gemini Developer API](https://www.anchorterminal.com/tools/gemini-api.md) (Model APIs & inference), [Vertex AI (Gemini Enterprise Agent Platform)](https://www.anchorterminal.com/tools/vertex-ai.md) (Model APIs & inference), [Gemini Embedding](https://www.anchorterminal.com/tools/gemini-embedding.md) (Embeddings & rerankers), [Vertex AI Gemini tuning](https://www.anchorterminal.com/tools/vertex-ai-tuning.md) (Fine-tuning), [Google Cloud Model Armor](https://www.anchorterminal.com/tools/google-model-armor.md) (Guardrails & safety filters), [Google Imagen](https://www.anchorterminal.com/tools/google-imagen.md) (Image generation), [Google Veo](https://www.anchorterminal.com/tools/google-veo.md) (Video generation), [Google Lyria](https://www.anchorterminal.com/tools/google-lyria.md) (Music generation), [Google Cloud Speech-to-Text](https://www.anchorterminal.com/tools/google-speech-to-text.md) (Speech-to-text), [Google Cloud Text-to-Speech](https://www.anchorterminal.com/tools/google-cloud-tts.md) (Text-to-speech), [Gemini Live API](https://www.anchorterminal.com/tools/gemini-live.md) (Conversational voice agents), [Agent Development Kit (ADK)](https://www.anchorterminal.com/tools/google-adk.md) (Agent frameworks & SDKs), [Agent Platform Memory Bank](https://www.anchorterminal.com/tools/google-memory-bank.md) (Agent memory), [Google Cloud Secret Manager](https://www.anchorterminal.com/tools/google-secret-manager.md) (Secrets & credential vaults), [Google Cloud Document AI](https://www.anchorterminal.com/tools/google-cloud-document-ai.md) (Document parsing & extraction), [Google Weather API (Maps Platform)](https://www.anchorterminal.com/tools/google-weather-api.md) (Weather & climate data), [Chrome DevTools MCP](https://www.anchorterminal.com/tools/chrome-devtools-mcp.md) (Browser automation), [Google Maps Platform + Grounding Lite MCP](https://www.anchorterminal.com/tools/google-maps-platform.md) (Maps, geocoding & places), [Google Cloud Translation](https://www.anchorterminal.com/tools/google-cloud-translation.md) (Translation), [Google Calendar API](https://www.anchorterminal.com/tools/google-calendar-api.md) (Calendars & scheduling), [Firebase Cloud Messaging](https://www.anchorterminal.com/tools/firebase-cloud-messaging.md) (Notifications), [Google Cloud Storage](https://www.anchorterminal.com/tools/google-cloud-storage.md) (File storage & sharing), [Google Drive API + MCP](https://www.anchorterminal.com/tools/google-drive-api.md) (File storage & sharing), [Gemini Enterprise](https://www.anchorterminal.com/tools/gemini-enterprise.md) (Company knowledge & data catalogues), [Gemini CLI](https://www.anchorterminal.com/tools/gemini-cli.md) (Agent harnesses), [Google Search Console API](https://www.anchorterminal.com/tools/google-search-console.md) (SEO & search visibility), [Google Ads API](https://www.anchorterminal.com/tools/google-ads-api.md) (Advertising & campaign operations), [Google Forms API](https://www.anchorterminal.com/tools/google-forms.md) (Forms, surveys & structured intake), [Google Sheets API](https://www.anchorterminal.com/tools/google-sheets-api.md) (Spreadsheets & operational tables), [Gmail API](https://www.anchorterminal.com/tools/gmail-api.md) (Mailbox access), [Google People API](https://www.anchorterminal.com/tools/google-people-api.md) (Contacts & address books). ## Assessment Serverless GPUs on Cloud Run, an L4 or RTX PRO 6000 per instance, billed per second, scaling to zero and starting in about 5 seconds before the model loads, with a published SLA and IAM. One GPU per instance, 3 GPUs of default quota a region and instance-based billing limit it to small and mid-size models. ## Facts | Field | Value | | --- | --- | | Vendor | Google Cloud (https://cloud.google.com/run) | | Kind | Platform | | Category | GPU & serverless compute (https://www.anchorterminal.com/categories/gpu-compute) | | Endpoint | `https://run.googleapis.com` | | Auth | OAuth · Deploys go through the Cloud Run Admin API with OAuth 2.0 bearer tokens from a service account or Application Default Credentials, under IAM roles such as roles/run.developer and roles/run.invoker. A deployed service can require IAM authentication or allow public calls. A project with billing enabled is set up in the console first. | | Pricing | Pay per use (Pay per use) · Per second, instance-based billing only. L4 $0.0001867 a second (about $0.67 an hour) without zonal redundancy, $0.0002909 with; RTX PRO 6000 $0.00036522 (about $1.31 an hour) and $0.00056913. CPU and memory extra, with a minimum of 4 vCPU and 16 GiB (L4) or 20 vCPU and 80 GiB (RTX PRO 6000). | | x402 | No · No x402, MPP or L402 on the Cloud Run pricing, GPU or quotas pages (checked 2026-11-06). Billing runs through a Google Cloud billing account. | | Licence | Proprietary service under the Google Cloud Platform terms. Client libraries are Apache-2.0 | | Packages | pypi: `google-cloud-run`; npm: `@google-cloud/run` | | Docs | https://docs.cloud.google.com/run/docs/configuring/services/gpu | | llms.txt | not found | | Last release | 2026-10-30 | | Surface listed | GPUs on Cloud Run services, jobs and worker pools, configured through gcloud, YAML, Terraform or the Cloud Run Admin API, read from docs.cloud.google.com (GPU pages for services and jobs, GPU best practices, quotas, release notes), the pricing page, the SLA and status.cloud.google.com on 6 November 2026. Nothing was deployed | | Scope | The GPU option of Cloud Run. Google Cloud's other model and compute products are separate, and no Anchor Terminal listing covers Cloud Run itself | | GPUs | One GPU per instance, NVIDIA L4 (24 GB) or RTX PRO 6000 Blackwell (96 GB), attached to one container | | Regions | L4 in regions including europe-west1, europe-west4, asia-southeast1 and asia-south1 (by invitation); RTX PRO 6000 in us-central1, europe-west4, asia-southeast1 and asia-south2, among others listed on the GPU page | | Zonal redundancy | On by default for new services, reserving GPU capacity across zones for failover at a higher price; off is cheaper and fails over on a best-effort basis | | Billing | Instance-based billing only, for the whole instance lifecycle. Minimum instances bill at the full rate while idle. No per-request fees | | Model loading | The best-practices page recommends downloading models from Cloud Storage at startup in parallel, and keeping models in the image only below about 10 GB | | Capabilities | compute.serverless, compute.gpu, compute.endpoints, compute.containers, compute.batch | | Tags | hosted, official, usage, per-second, scale-to-zero, sla, status-page, discovery-doc, l4, rtx-pro-6000 | | JSON | https://www.anchorterminal.com/api/v1/tools/cloud-run-gpus.json | ## Score breakdown (methodology v0.7, October 2026 research run) Assessed 2026-11-06 from public evidence against the published checklist (https://www.anchorterminal.com/benchmark/#checklist). Confidence: medium. Performance and Task success pending (no score, not in the total); the total is Σ(score × weight) ÷ 80 over the 7 assessed categories. "This run" is each category's share of the 100 points. | Category | Weight | This run | Score (0–100) | Points | | --- | --- | --- | --- | --- | | Reliability | 16% | 20 | 70 | 14.0 | | Performance | 10% | pending | pending | n/a | | Schema & documentation | 13% | 16.2 | 81 | 13.2 | | Agent ergonomics | 13% | 16.2 | 66 | 10.7 | | Security & auth | 14% | 17.5 | 78 | 13.7 | | Payments & pricing | 10% | 12.5 | 20 | 2.5 | | Task success | 10% | pending | pending | n/a | | Maintenance & community | 7% | 8.8 | 80 | 7.0 | | Transparency & trust (editorial 69, provenance 99) | 7% | 8.8 | 84 | 7.3 | | Negative events | up to −15 | up to −15 | none recorded | 0 | | **Total** | | | | **68.4 → B** | ### Why each score - Reliability 70 (checked 2026-11-06): Hosted reading. Google Cloud's status page with a JSON incident feed (20). In the 90 days from 8 August 2026 the feed names Cloud Run in three multi-product incidents, a service outage on 20 August (15:40 to 19:20 UTC, 27 products, global and us-west1), a network degradation in us-central1-b on 1 September and a europe-west2 disruption on 20 October. One major (10). Resource limits and GPU quota are published with numbers (3 GPUs a region by default), but no request rate for the Admin API was found on the quotas page (10). Google's client libraries retry with backoff and the Admin API takes etags, while no GPU-specific retry guidance was found (10). An SLA for GPU services, 99.95% with zonal redundancy and 99.5% without (10). GPU services generally available since 7 April 2025 (10). 20+10+10+10+10+10 = 70. - Performance: Pending. Latency is measured per call by our probes, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until the first probe window closes. - Schema & documentation 81 (checked 2026-11-06): API reading. A public Discovery document for the Cloud Run Admin API v2 (25). No llms.txt; Google's docs answer Markdown only at an unlinked `.md.txt` address, read as half, as for the Document AI listing (5). The GPU page says when to turn zonal redundancy on or off and the best-practices page when to bake models into images or load them from Cloud Storage (16). The GPU type is a free string in a node selector, with CPU and memory minimums stated in prose (9). gcloud, YAML, Terraform and console steps on each page, and errors follow Google's status model with no Cloud Run GPU error list (11). Versioned API (v1 and v2) and dated release notes (15). 25+5+16+9+11+15 = 81. - Agent ergonomics 66 (checked 2026-11-06): Platform reading. One `gcloud run deploy` with `--gpu` and `--gpu-type` adds a GPU to a container, and responses carry the service object with `fieldMask` on updates (15). List calls page with `pageSize` and `pageToken` (15). Google's status codes and messages, with quota errors that name the limit (12). Revisions are immutable, traffic can be moved back, and etags guard updates, but no idempotency key on create (12). Client libraries in many languages and gcloud, though a GPU deploy needs instance-based billing, minimum CPU and memory and, past 3 GPUs, a quota request (12). 15+15+12+12+12 = 66. - Security & auth 78 (checked 2026-11-06): OAuth 2.0 tokens from service accounts under IAM. Google's APIs accept `access_token` as a query parameter, the 10-point deduction other Google API listings take (20). IAM roles separate viewing, deploying and invoking, and services can require IAM authentication for every call (16). The platform runs your own container and returns its output (10). Cloud Audit Logs record Admin API calls, and request logs go to Cloud Logging (15). Google's vulnerability reward programme, security.txt and certifications (17). 20+16+10+15+17 = 78. - Payments & pricing 20 (checked 2026-11-06): No x402, MPP or L402 (0). Per-second GPU, CPU and memory prices published without a login (20). The Cloud Run free tier covers CPU and memory, not GPUs, and the $300 trial credit needs a payment method (0). A person creates the project and billing account in a browser (0). 0+20+0+0 = 20. - Task success: Pending. Task success needs the category task suites run through each tool, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until then. A data provider's data-quality score is published on its listing now and becomes half of this category when it's scored. - Maintenance & community 80 (checked 2026-11-06): Closed service with official SDKs. The newest GPU change is 30 October 2026, jobs with GPUs running up to 12 hours (30). Cloud Run release notes dated 4 November, 2 November, 30 October, 24 October and more in the 90 days (20). Release notes, Google Cloud support and public trackers for the client libraries, which were not read (10). Official client libraries in eight languages and gcloud (15). CI results not checked (5). 30+20+10+15+5 = 80. - Transparency & trust 84 (checked 2026-11-06): Closed service under the Google Cloud terms, with Apache-2.0 client libraries (15). The Cloud Data Processing Addendum and the privacy notice cover customer data, per the Document AI listing's 1 November reading; no Cloud Run statement on GPU instance data after shutdown was found (22). The Cloud terms promise 12 months' notice before a backwards-incompatible API change, and driver versions are announced in the release notes (16). Regions per GPU type listed, with Google's subprocessor list and data-location terms (16). 15+22+16+16 = 69. Fix list, everything this grade says the listing lacks, the biggest gain first (12 items). What it covers is at https://www.anchorterminal.com/fixes/cloud-run-gpus.md (JSON https://www.anchorterminal.com/fixes/cloud-run-gpus.json). The whole list for a coding agent comes from `POST https://www.anchorterminal.com/api/v1/fix-list` with `{"listing": "cloud-run-gpus", "plan": "read"}`, free while the beta runs ### What we couldn't check - unchecked: rate limits on the Cloud Run Admin API, which the quotas page read doesn't give - The Google Cloud terms, privacy notice and security.txt were not re-read for this listing; the provenance follows the Document AI check of 1 November 2026 - The status feed doesn't break incidents down by GPU, so how the three Cloud Run incidents affected GPU instances is not known ### Sources - GPU support for services: (seen 2026-11-06) - GPU support for jobs: (seen 2026-11-06) - GPU best practices: (seen 2026-11-06) - quotas and limits: (seen 2026-11-06) - release notes: (seen 2026-11-06) - pricing: (seen 2026-11-06) - SLA: (seen 2026-11-06) - Google Cloud incident feed: (seen 2026-11-06) - 20 August 2026 incident: (seen 2026-11-06) ## Score history Every move of a score since the listing was graded, newest first, with its cause. A score can't move without an entry here. JSON: https://www.anchorterminal.com/api/v1/tools/cloud-run-gpus/history.json - 2026-11-06: graded 68.4 B (methodology 0.7) ## Who's behind it (provenance 99/100, checked 2026-11-06) | Check | Finding | Points | | --- | --- | --- | | Legal entity named | Google LLC | 20/20 | | Domain age | google.com, registered 1997-09-15 (29 years) | 15/15 | | Endpoint on the vendor's domain | run.googleapis.com | 15/15 | | Terms of service | read, states 7 of the 7 things a reader expects | 10/10 | | Privacy policy | read, states 7 of the 8 things a reader expects | 9.3/10 | | Status page | status.cloud.google.com | 10/10 | | Changelog | published | 10/10 | | security.txt | valid | 10/10 | | People named | 5 named with their role, none with a public profile | 7/10 | | Support route | help pages | 5/5 | The endpoints are on googleapis.com, Google's API domain. Docs are on docs.cloud.google.com. Legal entity, terms, privacy notice and security.txt as on the Google Cloud Document AI listing, checked 1 November 2026, and not re-read for this listing. docs.cloud.google.com/robots.txt and cloud.google.com/robots.txt allow the Cloud Run pages read; status.cloud.google.com/robots.txt allows everything. The Cloud Run SLA lists GPU services separately, 99.95% with zonal redundancy and 99.5% without (https://cloud.google.com/run/sla). ### Terms and privacy, as read A reading by a fixed set of rules, each answered with the vendor's own sentence. Not legal advice. **Terms of service** (https://cloud.google.com/terms), read 2026-10-08, dated 2026-09-02, states 7 of the 7 things a reader expects. - To know. Says access can be ended without notice or for any reason. "For purposes of GCP Services and TSS only, Google may terminate this Agreement or any applicable Order Form for its convenience at any time with 30 days' prior written notice to Customer." - Gives the date it was last updated. Last updated 2026-09-02. - Names the governing law or courts. The law of the United States of America. - States a limit on its liability. Capped at the fees paid in the 12 months before the claim or $5,000. - Says how changes to the terms are announced. Gives 30 days of notice before a change. - Refers to a service level or uptime commitment. Names 99.999% availability. - Also in the text (2026-10-08). Google may change its fees at any time unless an addendum or order form expressly says otherwise. "Google may change the Fees at any time unless otherwise expressly agreed in an addendum or Order Form." - Also in the text (2026-10-08). Google's total liability for services or software supplied free of charge is limited to 5,000 US dollars. "except Google’s total aggregate Liability for damages arising out of or related to Services or Software provided free of charge is limited to $5,000." - Also in the text (2026-10-08). When automated safety tools detect potential abuse of Generative AI Services, Google may log customer prompts to review whether a violation occurred. "Google may log Customer prompts solely for the purpose of reviewing and determining whether a violation has occurred." **Privacy policy** (https://cloud.google.com/terms/cloud-privacy-notice), read 2026-10-09, dated 2026-09-28, states 7 of the 8 things a reader expects. - Gives the date it was last updated. Last updated 2026-09-28. - Not found in the text. Says whether personal data is sold or shared for advertising. - Also in the text (2026-10-08). This notice covers Service Data only and does not cover Customer Data or Partner Data, which the Cloud Data Processing Addendum governs. "applies solely to Service Data and does" ## Humans behind the project (researched 2026-11-06 from public pages, not part of the grade) ### Key people - Larry Page, Co-founder, Google, left executive roles in December 2019 and sits on Alphabet's board - Sergey Brin, Co-founder, Google, left executive roles in 2019 and sits on Alphabet's board - Sundar Pichai, CEO, Google and Alphabet - Thomas Kurian, CEO, Google Cloud - Demis Hassabis, Co-founder and CEO, Google DeepMind - Note: Google Cloud is Google's cloud business, so the company-level people are the same as for Google (out/top/antigravity-cli.json), with Thomas Kurian added as CEO of Google Cloud from Wikipedia's Google Cloud article (infobox owner Google, CEO Thomas Kurian) and his own article, read 28 October 2026. Copied from the Google Cloud Document AI listing for Cloud Run GPUs on 6 November 2026; no Cloud Run product people were looked for. - Google Cloud: LinkedIn https://www.linkedin.com/company/google X https://x.com/Google ### Ownership and investors - Ownership: Part of Alphabet Inc. ### Getting support - Help: https://cloud.google.com/support-hub - Help: https://support.google.com/ - Sources: https://about.google/intl/ALL_en/our-story/, https://www.linkedin.com/company/google, https://x.com/Google, https://cloud.google.com/contact, https://cloud.google.com/support-hub ## Live (updated 2026-11-07 17:49 UTC) - Right now: up, HTTP 404, 33 ms, checked 2026-11-07 17:49 UTC (get on `https://run.googleapis.com`) - Uptime 24h 100.0% (195 probes) · 30 days 100.0% (195 probes) · p50 35 ms · p95 110 ms - Vendor status page: not read, no machine-readable status found - npm `@google-cloud/run` 4.2.0 - pypi `google-cloud-run` 0.16.2, released 2026-10-01 - security.txt: valid, expires 2030-04-01T00:00:00z - Watching changelog - Watching privacy , last changed 2026-11-03 07:43 UTC - Watching terms , last changed 2026-11-03 07:43 UTC - Always current: https://www.anchorterminal.com/api/v1/live/cloud-run-gpus.json ## Probe metrics Not measured yet. Our benchmark probes haven't run, so there's no availability, latency or error rate from a run and Performance is pending. Live uptime, where we poll the endpoint, is under Live and doesn't change the score. ## Prices | Item | Price | Unit | Note | | --- | --- | --- | --- | | NVIDIA L4, no zonal redundancy | $0.67 | per GPU-hour | $0.0001867 a second, tier 1 regions; CPU and memory extra | | NVIDIA L4, zonal redundancy | $1.05 | per GPU-hour | $0.0002909 a second | | NVIDIA RTX PRO 6000, no zonal redundancy | $1.31 | per GPU-hour | $0.00036522 a second | | NVIDIA RTX PRO 6000, zonal redundancy | $2.05 | per GPU-hour | $0.00056913 a second | Across all listings: https://www.anchorterminal.com/prices/index.md ## Strengths - Scales to zero, bills per second, and instances with drivers start in about 5 seconds - SLA of 99.95% with zonal redundancy and 99.5% without, plus Google's status feed - IAM roles for deploying and invoking, Cloud Audit Logs and services that can require authentication - Per-second prices public, L4 from about $0.67 a GPU-hour without zonal redundancy - The same GPU option on services, jobs (up to 12 hours) and worker pools ## Weaknesses - One GPU per instance, L4 (24 GB) or RTX PRO 6000 (96 GB) only, so large models don't fit - Default quota is 3 GPUs a region; more needs a quota request - Model load time comes on top of the 5-second start, and minimum instances bill while idle - No free GPU tier, and the trial credit needs a payment method - Google's APIs accept OAuth tokens in a URL query parameter ## Before you call it (notes for agents) 1. Pass `--gpu 1 --gpu-type nvidia-l4` (or nvidia-rtx-pro-6000) with at least 4 vCPU and 16 GiB, and `--no-cpu-throttling` for instance-based billing 2. Load model weights from Cloud Storage at startup in parallel; bake them into the image only below about 10 GB 3. Turn zonal redundancy off for cheaper, more readily granted quota when failover isn't required 4. Set minimum instances to 0 unless cold starts matter, since minimum instances bill at the full rate 5. Send OAuth tokens in the `Authorization` header, never as `access_token` in the URL ## Similar tools Ranked by shared capabilities, then score. Same-category tools with no shared capability key are listed last. | Tool | Grade | Score | Rank | Shared capabilities | x402 | Markdown | | --- | --- | --- | --- | --- | --- | --- | | Modal | B | 62.7 | 543 | compute.gpu, compute.serverless, compute.endpoints, compute.batch, compute.containers | no | https://www.anchorterminal.com/tools/modal.md | | Beam | C | 56.2 | 835 | compute.gpu, compute.serverless, compute.endpoints, compute.batch, compute.containers | no | https://www.anchorterminal.com/tools/beam.md | | Runpod | C | 55.6 | 859 | compute.gpu, compute.serverless, compute.endpoints, compute.batch, compute.containers | no | https://www.anchorterminal.com/tools/runpod.md | | Verda | D | 53.3 | 946 | compute.gpu, compute.serverless, compute.endpoints, compute.batch, compute.containers | no | https://www.anchorterminal.com/tools/verda.md | | Cerebrium | D | 52.5 | 983 | compute.gpu, compute.serverless, compute.endpoints, compute.batch, compute.containers | no | https://www.anchorterminal.com/tools/cerebrium.md | | Nebius AI Cloud | BB | 71.2 | 167 | compute.gpu, compute.endpoints, compute.batch, compute.containers | no | https://www.anchorterminal.com/tools/nebius-ai-cloud.md | ## Panel reviews (0) Reviewed by the Anchor panel (https://www.anchorterminal.com/reviewers/index.md): . Desk reviews, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made. For a desk review, the outcome says whether the reviewer's questions could be answered from public material: success, partial or failure. How reviews work: https://www.anchorterminal.com/reviews/how-it-works.md ## Notable - Instances with an L4 or RTX PRO 6000 GPU and drivers pre-installed start in about 5 seconds, before the container loads its model, per the GPU page (source: ) - GPU services became generally available on 7 April 2025 and RTX PRO 6000 Blackwell support on 13 April 2026; jobs with GPUs can run up to 12 hours since 30 October 2026, per the release notes (source: ) - A project gets 3 GPUs of quota per region (zonal redundancy off) on its first GPU deployment, and more needs a quota request; quota without zonal redundancy is granted more readily (source: ) - The SLA gives GPU services 99.95% monthly uptime with zonal redundancy and 99.5% without (source: ) - The Google Cloud incident feed names Cloud Run in three multi-product incidents from 8 August to 6 November 2026, among them a service outage on 20 August (15:40 to 19:20 UTC) (source: ) - #2 of 22 in Best GPU and serverless compute for AI workloads: https://www.anchorterminal.com/best/gpu-compute/index.md - All 231 gpu compute comparisons: https://www.anchorterminal.com/compare/gpu-compute/index.md ## Compare - [Baseten vs Cloud Run GPUs](https://www.anchorterminal.com/compare/baseten-vs-cloud-run-gpus.md): B 62.7 vs B 68.4 - [Beam vs Cloud Run GPUs](https://www.anchorterminal.com/compare/beam-vs-cloud-run-gpus.md): C 56.2 vs B 68.4 - [Cerebrium vs Cloud Run GPUs](https://www.anchorterminal.com/compare/cerebrium-vs-cloud-run-gpus.md): D 52.5 vs B 68.4 - [Cloud Run GPUs vs CoreWeave](https://www.anchorterminal.com/compare/cloud-run-gpus-vs-coreweave.md): B 68.4 vs C 60.5 - [Cloud Run GPUs vs Crusoe Cloud](https://www.anchorterminal.com/compare/cloud-run-gpus-vs-crusoe-cloud.md): B 68.4 vs B 62.4 - [Cloud Run GPUs vs GPUsMarket](https://www.anchorterminal.com/compare/cloud-run-gpus-vs-gpusmarket.md): B 68.4 vs E 39.6 - [Cloud Run GPUs vs Hugging Face Inference Endpoints](https://www.anchorterminal.com/compare/cloud-run-gpus-vs-hugging-face-inference-endpoints.md): B 68.4 vs B 66.7 - [Cloud Run GPUs vs Hyperbolic](https://www.anchorterminal.com/compare/cloud-run-gpus-vs-hyperbolic.md): B 68.4 vs E 38.7 - [Cloud Run GPUs vs Lambda Cloud](https://www.anchorterminal.com/compare/cloud-run-gpus-vs-lambda.md): B 68.4 vs D 52.9 - [Cloud Run GPUs vs Massed Compute](https://www.anchorterminal.com/compare/cloud-run-gpus-vs-massed-compute.md): B 68.4 vs E 42.6 - [Cloud Run GPUs vs Nebius AI Cloud](https://www.anchorterminal.com/compare/cloud-run-gpus-vs-nebius-ai-cloud.md): B 68.4 vs BB 71.2 - [Cloud Run GPUs vs Northflank](https://www.anchorterminal.com/compare/cloud-run-gpus-vs-northflank.md): B 68.4 vs C 54 - [Cloud Run GPUs vs Thunder Compute](https://www.anchorterminal.com/compare/cloud-run-gpus-vs-thunder-compute.md): B 68.4 vs D 51.3 - [Cloud Run GPUs vs Together GPU Clusters](https://www.anchorterminal.com/compare/cloud-run-gpus-vs-together-gpu-clusters.md): B 68.4 vs C 58.1 - [Cloud Run GPUs vs Koyeb](https://www.anchorterminal.com/compare/cloud-run-gpus-vs-koyeb.md): B 68.4 vs D 46.6 - [Cloud Run GPUs vs Modal](https://www.anchorterminal.com/compare/cloud-run-gpus-vs-modal.md): B 68.4 vs B 62.7 - [Cloud Run GPUs vs Replicate Deployments](https://www.anchorterminal.com/compare/cloud-run-gpus-vs-replicate-deploy.md): B 68.4 vs B 65.2 - [Cloud Run GPUs vs Runpod](https://www.anchorterminal.com/compare/cloud-run-gpus-vs-runpod.md): B 68.4 vs C 55.6 - [Cloud Run GPUs vs Vast.ai](https://www.anchorterminal.com/compare/cloud-run-gpus-vs-vast-ai.md): B 68.4 vs C 56.4 - [Cloud Run GPUs vs Verda](https://www.anchorterminal.com/compare/cloud-run-gpus-vs-verda.md): B 68.4 vs D 53.3 ## Verify this listing For the vendor. The badge or a plain link to this page verifies the listing, from a page on google.com or one of its subdomains. It shows the listing is the vendor's and that the vendor knows it's here, and it never changes a grade, rank or review. The vendor sends the page's address to `POST https://www.anchorterminal.com/api/v1/verify` as `{"slug": "cloud-run-gpus", "url": "…"}`, or calls the `verify_listing` tool at https://www.anchorterminal.com/mcp. We fetch the page once, then again every week; two failed checks in a row and the verification lapses, and a later pass restores it. What we check: https://www.anchorterminal.com/builders/index.md#verify HTML badge: ```html Cloud Run GPUs on Anchor Terminal ``` Markdown badge, for a README: ```markdown [![Cloud Run GPUs on Anchor Terminal](https://www.anchorterminal.com/badges/cloud-run-gpus.svg)](https://www.anchorterminal.com/tools/cloud-run-gpus) ``` Plain link: ```html Cloud Run GPUs on Anchor Terminal ``` ## Share this listing For the vendor. Sharing assets for social media, two PNGs of 1200 × 630 that say Cloud Run GPUs is listed on Anchor Terminal, with the vendor's logo and this page's address and no grade or score. - Dark: https://www.anchorterminal.com/assets/share/cloud-run-gpus-dark.png - Light: https://www.anchorterminal.com/assets/share/cloud-run-gpus-light.png --- Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp