SteadyStack
Get Started
Cloud & Infrastructurecloud.google.com/run

Is Google Cloud Run Down Right Now?

Live global uptime status, multi-region edge latency, official incident reports, and automated monitoring for Google Cloud Run.

G

Google Cloud Run

cloud.google.com/run

Serverless platform to build and deploy scalable containerized apps on Google infrastructure.

Operational
Edge Latency
220 ms

Primary edge roundtrip

24h Global Uptime
99.98%

Edge consensus

Vantage Points
7 Regions

NA, EU, APAC Edge DOs

Last Checked
5:27:56 AM

Edge consensus mesh

Telemetry verified by SteadyStack Autonomous Edge Network
Official Status
Automated Developer Alerting

Stop checking manually.

When Google Cloud Run goes down or suffers silent latency degradation, you shouldn't be refreshing status pages, searching social feeds, or waiting for angry user reports. Get alerted the exact second Google Cloud Run fails.

Monitor Google Cloud Run in 1 Click

Free 50 monitors • 3m standard (1m for first 10) • 2-of-3 Edge Quorum • No credit card required

10-Second Edge Intervals

Continuous HTTP, WebSocket & DNS checks from 15+ global edge nodes.

4-of-7 Quorum Verification

Multi-region consensus verification prevents 3 AM wakeups from transient routing blips.

Multi-Channel Escalation

Instant alerts to Slack, Discord, Telegram, SMS, PagerDuty & Webhooks.

steadystack.config.ts
Auto-provisioned Monitor
import { defineMonitor } from "@steadystack/core";

export default defineMonitor({
  name: "Google Cloud Run API & Health",
  target: "https://cloud.google.com/run",
  interval: "10s",
  consensus: { requiredRegions: 3 },
  alerts: ["slack-dev-ops", "pagerduty-p1", "discord-incidents"],
});

Global Edge Reachability & Regional Latency

Synthetic probe response times tested from SteadyStack worldwide vantage points.

🇺🇸
US-East (N. Virginia)
us-east
105 ms
UP
🇺🇸
US-West (Oregon)
us-west
128 ms
UP
🇩🇪
EU-Central (Frankfurt)
eu-central
165 ms
UP
🇯🇵
AP-Tokyo (Tokyo)
ap-northeast
238 ms
UP
🇧🇷
SA-East (São Paulo)
sa-east
244 ms
UP
🇿🇦
AF-South (Cape Town)
af-south
298 ms
UP

Downtime Impact Analysis

What happens when Google Cloud Run degrades

Container instances fail to scale from zero, requests return 504 deadline exceeded.

Common HTTP Error Codes Observed

504 Gateway Timeout503 Service UnavailableContainer failed to start and listen on PORT

Critical Monitored Subsystems

Components tracked on cloud.google.com/run

Cloud Run Services
Synthetic Active
Cloud Run Jobs
Synthetic Active
Container Scale-to-Zero
Synthetic Active
Custom Domains
Synthetic Active

Engineering Resilience Guide: Surviving Google Cloud Run Outages

Defensive software architecture patterns to prevent third-party cascade failures.

Immediate Tactical Steps

  • 1Inspect Logs Explorer in Google Cloud Console.
  • 2Increase container memory/CPU allocation.

Recommended Resiliency Patterns

Circuit Breaker Pattern: Automatically trip and fallback to cache when Google Cloud Run error rates exceed 15% in a 30s rolling window.

Idempotent Background Retries: Push failed API events into an asynchronous dead-letter queue with exponential backoff and jitter.

Multi-Region Edge Synthetic Consensus: Rely on SteadyStack to alert your team before end-users notice degradation.

Frequently Asked Questions: Google Cloud Run Availability & Monitoring

Everything you need to know about tracking Google Cloud Run outages and SLA reliability.

Our real-time global edge probes continuously test Google Cloud Run (cloud.google.com/run) across multiple worldwide locations. You can check the live status badge and latency meter at the top of this page. If you are seeing errors while the global status is operational, it may be due to localized ISP routing, local DNS caching, or account-specific rate limiting.
Related Cloud & Infrastructure Dependencies
Is Google Cloud Platform (GCP) down?
Is Vercel down?
Is Fly.io down?