Skip to main content
gcpdown

Is Cloud Run down?

OperationalLast checked Oct 15, 2026, 12:19 AM UTC

Last 90 days

99.734% uptime · 2 incidents
2026-07-18: operational2026-07-19: operational2026-07-20: operational2026-07-21: operational2026-07-22: operational2026-07-23: operational2026-07-24: operational2026-07-25: operational2026-07-26: operational2026-07-27: operational2026-07-28: operational2026-07-29: operational2026-07-30: operational2026-07-31: operational2026-08-01: operational2026-08-02: operational2026-08-03: operational2026-08-04: operational2026-08-05: operational2026-08-06: operational2026-08-07: operational2026-08-08: operational2026-08-09: operational2026-08-10: operational2026-08-11: operational2026-08-12: operational2026-08-13: operational2026-08-14: operational2026-08-15: operational2026-08-16: operational2026-08-17: operational2026-08-18: operational2026-08-19: operational2026-08-20: outage2026-08-21: operational2026-08-22: operational2026-08-23: operational2026-08-24: operational2026-08-25: operational2026-08-26: operational2026-08-27: operational2026-08-28: operational2026-08-29: operational2026-08-30: operational2026-08-31: operational2026-09-01: degraded2026-09-02: operational2026-09-03: operational2026-09-04: operational2026-09-05: operational2026-09-06: operational2026-09-07: operational2026-09-08: operational2026-09-09: operational2026-09-10: operational2026-09-11: operational2026-09-12: operational2026-09-13: operational2026-09-14: operational2026-09-15: operational2026-09-16: operational2026-09-17: operational2026-09-18: operational2026-09-19: operational2026-09-20: operational2026-09-21: operational2026-09-22: operational2026-09-23: operational2026-09-24: operational2026-09-25: operational2026-09-26: operational2026-09-27: operational2026-09-28: operational2026-09-29: operational2026-09-30: operational2026-10-01: operational2026-10-02: operational2026-10-03: operational2026-10-04: operational2026-10-05: operational2026-10-06: operational2026-10-07: operational2026-10-08: operational2026-10-09: operational2026-10-10: operational2026-10-11: operational2026-10-12: operational2026-10-13: operational2026-10-14: operational2026-10-15: operational
2026-07-182026-10-15

What Cloud Run does - and how it fails

Cloud Run executes containers serverlessly and scales them to zero - which means it inherits the health of everything underneath it: the regional serving infrastructure, container registry reads, and the build path if you deploy from source. Incidents usually show up as elevated cold-start latency, request 5xx in one region, or deploys failing while running revisions keep serving.

  • Elevated cold-start latency after capacity or scheduler events
  • Request 5xx rates in one region while other regions stay healthy
  • New deploys or revisions failing (image pulls, build path) while the serving revision is fine
  • Event-driven invocations lagging because Pub/Sub or Eventarc delivery is delayed upstream

Recent Cloud Run incidents

  • Multiple products in us-central1-b are experiencing network service degradation.

    September 1, 2026 · 4h 8m

    Multiple products in us-central1-b are experiencing network service degradation.

  • We are investigating an issue where customers may experience timeouts, service degradations, errors, and elevated latencies across multiple products in the us-west1 region.

    August 20, 2026 · 3h 40m

    We are investigating an issue where customers may experience timeouts, service degradations, errors, and elevated latencies across multiple products in the us-west1 region.

Full analyses live in the post-mortem archive.

Cloud Run questions

Is Cloud Run down right now?

The live status above reflects our latest check. Cloud Run failures are almost always regional - if you serve from a single region, that region’s health is your availability. Multi-region behind a global load balancer is the standard fix.

Why did my Cloud Run latency spike during a GCP incident?

Cold starts amplify upstream incidents: if instances are recycled or scaled during an event, every new instance pays image-pull and startup cost simultaneously. Setting min-instances above zero for latency-sensitive services buys you through most of it.

Does Cloud Run have an SLA?

Yes - 99.95% monthly uptime for requests served. Tiered credits apply below target, claimed within 30 days, capped at 50% of the month’s Cloud Run charges.

Get alerted when Cloud Run breaks

Instant email the moment we detect an incident - affected services and regions included.

Get outage alerts