Is Cloud Run down?

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