DEV Community

Honey Kiran
Honey Kiran

Posted on Originally published at honeykiran.substack.com on

Cloud Run Is Reliable. Your Defaults Are the Risk.

A public r/googlecloud thread asked: "How reliable is Cloud Run, really?" The asker was weighing a move off Heroku for a latency-sensitive service.

Fair question. Slightly the wrong one.

Cloud Run is reliable at the layer Google runs. Your agents' first month is decided by yours: the defaults nobody touched because the first deploy worked.

Illustration: a Cloud Run service at night shows a green 'SLA 99.95% - kept' badge while five factory-default dials sit grey; a request clock reaches 300 seconds, the timeout dial swings into the red and a 504 stamp lands. Text: The platform is fine. The dials are not.

What the SLA actually promises

The SLA promises 99.95% monthly uptime for non-GPU services in most regions. Now read what counts as "down".

Downtime means more than 1% of requests failing with a 5xx from Cloud Run's own infrastructure, over at least 100 requests. Errors from your own software don't count. A slow response that finally returns 200 counts as uptime.

The remedy: service credits of 10%, 25% or 50%. Not cash. Ask within 30 days.

The SLA counts errors, not slowness. Your users count both.

The platform kept its promise. Your defaults wrote yours.

Illustration: on the left, an SLA badge of 99.95% and an error rate flat at 0.0%; on the right, one request's latency bar stretches to 28 seconds, returns 200 OK and is marked 'counted as uptime' over a red zone labelled 'slow is not downtime'.

The five defaults

Three of these bite agent backends directly.

Cold starts. Minimum instances default to 0. With no traffic, the service scales to zero, and the next request pays the start-up: your latency tail. Minimum instances keep containers warm and ready. They are billed, and best-effort, not guaranteed.

Concurrency. The console default is 80 requests per instance. From the CLI or Terraform, a new service gets 80 × its vCPUs. The number is a ceiling, not a promise: if the CPU is already saturated, Cloud Run may send fewer and scale out. Agent code written for one job at a time meets 80. Code unsafe in parallel? Set concurrency to 1.

CPU and billing mode. The default is request-based billing: CPU exists only during a request. Between calls, an agent's background loop starves in the dark. Background work needs instance-based billing (--no-cpu-throttling), which charges for the whole instance life.

Timeout. Default 300 seconds, maximum 60 minutes. A long agent task hits that wall: the connection closes with a 504. The container is not terminated. It may keep processing work nobody is waiting for; on instance-based billing, that time is billed.

Max instances. The cap protects your database and your wallet. At the cap, requests queue briefly, then fail with 429.

Five setting gauges flip from grey 'factory' to orange 'on purpose', each needle swinging to its new position: min instances 0 to 1, concurrency 80 to measured, CPU on request to matched to background work, timeout 300s to matched to the work, max instances unset to 20. Text: Same service. Different night.

The tuned deploy

Four of the five defaults, set on purpose. Billing mode stays default.

gcloud run deploy my-service \
  --image us-docker.pkg.dev/PROJECT_ID/REPO/my-service:TAG \
  --region us-central1 \
  --min-instances 1 \
  --max-instances 20 \
  --concurrency 40 \
  --cpu 1 \
  --memory 512Mi \
  --timeout 60s \
  --cpu-boost
Enter fullscreen mode Exit fullscreen mode

Your numbers will differ. The habit must not.

Revisions and the way back

Cloud Run does this part beautifully. Every change ships a new revision.

Deploy it with no traffic. Tag it. Send it 5%. Watch. Rollback is one command: 100% back to the previous revision.

Illustration: revision v1 holds 100% of traffic; v2 deploys with no traffic and a canary tag, receives 5%, shows 5xx errors, and traffic is sent back to v1 at 100% with one command. Text: Rollback is one command: 100% back to the previous revision.

# deploy new revision with no traffic, then send it 5%
gcloud run deploy my-service \
  --image us-docker.pkg.dev/PROJECT_ID/REPO/my-service:TAG \
  --region us-central1 \
  --no-traffic --tag canary

gcloud run services update-traffic my-service \
  --region us-central1 \
  --to-tags canary=5

# rollback: send 100% back to the previous revision
gcloud run services update-traffic my-service \
  --region us-central1 \
  --to-revisions PREVIOUS_REVISION=100
Enter fullscreen mode Exit fullscreen mode

Traffic shifts are not instant, and in-flight requests are not dropped.

The pre-flight checklist

  • Min instances chosen: idle cost known, best-effort limits accepted.
  • Concurrency measured, not defaulted: load-tested at your value; unsafe in parallel means 1.
  • Billing mode matched to background work: an agent loop outside a request needs instance-based billing.
  • Timeout matched to the longest agent task: just above your honest worst case, not 300 by accident.
  • Max instances set: a cap your database can survive.
  • Canary before full traffic: no traffic, tag, 5%, then up.
  • Rollback command rehearsed: run in staging first.
  • SLA read before it is needed: platform 5xx errors count, slowness doesn't, credits are claimed within 30 days.

A 15-second animation. A caller's request reaches a Cloud Run service whose timeout still sits at the factory 300 seconds. The agent task runs long, the caller waits, and the wire breaks at the wall with a 504. Five gauges then flip from factory to on purpose, each needle swinging. Text: Trust the platform. Audit the defaults.

A dark checklist card titled 'Before you ship: the Cloud Run defaults audit' with eight checkboxes: min instances chosen, concurrency measured, CPU matched, timeout matched, max instances set, new revision ships dark, canary watched, rollback rehearsed. Footer: Trust the platform. Audit the defaults. 3AM Files.

So, how reliable is Cloud Run, really? Very, at its layer. Your agents' reliability is written in five settings most teams never open. Trust the platform. Audit the defaults.

Which default is still factory-set on your busiest service? Tell me in the comments.

New here? 3AM Files is one short, useful read a day on AI doing real DevOps work. Follow along so the next one finds you.


© 2026 Honey Kiran. All rights reserved.

Honey Kiran · DevOps & Platform Engineering

Cloud, Kubernetes, DevOps, SRE, and platform engineering — explained the practical way.

Moving something latency-sensitive to Cloud Run — or already there and wondering which default is quietly taxing you? Tell me which setting bit you first in the comments.

Examples are illustrative — validate in your own environment before running in production.

Disclaimer

  • This post describes my personal experience with my own systems and accounts, in my own words. It is a first-person account of what I observed and what I do in my own work — not a statement of any company’s intentions, policies, or internal decisions. Where I do not know something, the post says so.
  • I am not affiliated with, endorsed by, or speaking for any company, product, or vendor named in this post. All product and company names are trademarks of their respective owners and are mentioned only to describe the experience accurately.
  • Any error messages, documentation excerpts, or figures quoted here are reproduced from my own records or from the public sources linked in the post, believed accurate at the time of writing. Product behavior changes over time; verify against current official documentation before relying on any detail.
  • Nothing in this post is professional, financial, legal, or security advice for your specific situation. Examples are illustrative — validate in your own environment before running anything in production.
  • Corrections are welcome. If any company named here publishes an official statement, or if any detail is wrong, I will update this post and note the correction. The goal is an accurate public record, not a verdict.

Top comments (0)