Is anyone else experiencing intermittent deployment issues with Cloud Run revisions using startup probes since Friday, January 9th?
I am deploying more than 10 containers simultaneously. The startup probes are very simple (returning a 200 HTTP status code), and this setup has been working perfectly for years. However, it has suddenly started failing randomly without any changes on our side.
(I didn’t made any update to my network configuration : firewall, load balancer..)
I’m using last version of gcloud CLI.
Any insights or similar observations would be appreciated.
We are seeing the exact same behavior. We manage a microservice architecture of roughly 30 services (mix of Cloud Run and Cloud Functions). Like you, our setup has been stable for years, but we began seeing random deployment failures starting January 7th.
We deploy via both Terraform (resource updates) and gcloud SDK via Cloud Scheduler. After some troubleshooting yesterday, we tried reducing the Terraform parallelism flag. While we’ve only run about 5 deployments since the change, we haven’t seen a failure since.
It’s still early, but reducing parallelism seems to mitigate the issue. We would also appreciate any insights, as this is currently causing unpredictable disruptions in our production environments.
Hey Mathieu, thanks for sharing potential workaround with me. I’ve already tried to deploy less container at the same time but the error still occurred
We are experiencing an issue with Cloud Run and Google Cloud Functions beginning on Tuesday, 2026-01-06 20:25 PST. Our engineering team continues to investigate the issue. We will provide an update by Wednesday, 2026-01-14 03:30 PST with current details. We apologize to all who are affected by the disruption.
Incident Resolved