Google Cloud statusManual checkVerified May 24, 2026Source: status.cloud.google.com
Is Google Cloud down?
Live status check · No widespread incident reported.
Most recent manual verification mirrored from status.cloud.google.com. Below: the components that can break, what to do during an incident, and how to keep your scheduled jobs running independently.
About Google Cloud status
Google Cloud Platform powers Cloud Run, GKE, Cloud Functions, BigQuery, Firestore, and the Google Workspace APIs. Most outages are regional and tied to a specific product; the status page is one of the best in the industry, with clear product × region breakdowns.
Components and surfaces that can break
- Surface 01
Cloud Run, Cloud Functions, GKE, App Engine.
- Surface 02
Cloud SQL, Firestore, BigQuery, Cloud Storage, Pub/Sub.
- Surface 03
Cloud Scheduler, IAM, Cloud Logging, the Cloud Console.
Recent Google Cloud incidents
Google Cloud maintains a public incident history. Read the latest entries to see whether you're hitting a known issue, and look at the post-mortems for context on how long similar incidents typically take to clear.
What to do if Google Cloud is actually down
Use the product × region matrix
status.cloud.google.com shows a clickable grid: rows are products, columns are regions. The cell color tells you instantly whether the problem is your region or the global control plane.
Cloud Scheduler skips do not auto-retry
Default Cloud Scheduler jobs have at-most-once semantics. A skipped fire during an incident is gone unless you've set max retry attempts. Run the same handler URL from an external scheduler if you need strict cadence.
Verify Cloud Run cold-start budget after recovery
If Cloud Run autoscaled to zero during the outage, the first requests after recovery pay full cold-start cost. Pre-warm with a few probes from your terminal or from Crontap before traffic returns.
Keep firing through the incident
Schedule your own Google Cloud health check with Crontap
Cloud Run + Cloud Scheduler is the standard GCP cron pattern, but Cloud Scheduler is billed per job and skips silently on platform incidents. Crontap calls your .run.app URL directly, no Cloud Scheduler resource to create, and Pro pricing is a flat fee instead of per-job.
External HTTP cron hits your endpoint on the cadence you pick, stores every response, and emails you the moment a run fails. Pro schedules down to 1 minute; $3.25/mo annual flat for unlimited jobs.
Go deeper
Google Cloud status: FAQ
- Where do I check Google Cloud status?
- status.cloud.google.com has a per-product, per-region matrix. The JSON feed at /incidents.json is good for scripting. The Cloud Console also surfaces active incidents that affect your project specifically.
- Why did my Cloud Scheduler job miss a run?
- Cloud Scheduler is at-most-once by default. Skipped runs are not retried. You can configure retry attempts and deadlines per job, but the platform itself does not catch up missed fires.
- How do I cron a Cloud Run service without Cloud Scheduler?
- Make your Cloud Run service publicly invocable (or signed by Crontap's IP) and call the .run.app URL from Crontap on the cadence you want. Less GCP-side wiring, retries on failure, and a single dashboard if you also run cron against non-GCP targets. Full walkthrough in the Cloud Run cron without Cloud Scheduler post.