20 days ago
Service stuck failing after GCP outage recovery
Project: delightful-passion
Service: JBaerowebsite
Environment: production
Region: us-east4-eqdc4a
4 consecutive deploys have failed since the May 19 GCP outage.
Each sits ~10 min in INITIALIZING then flips to FAILED with no
build logs accessible via CLI. Last successful deploy was May 15.
Failed deploy IDs:
- e5588bf7-5c9e-431d-aea9-83414ecd25f0 (May 21 11:26 CDT)
- ec001eed-19e9-4ccd-9f41-4163f2627db7 (May 20 20:21 CDT)
- fc8fcda9-0482-4b76-a95d-26431b885c4d (May 20 18:12 CDT)
- 15e14415-12f6-43a0-ba27-693dc73dc9bb (May 20 14:21 CDT)
Tried both railway up CLI and GitHub auto-deploys — same result.
Suspect builder node assignment from the recovery backlog.
Can you manually unstick? I have other sites hosted as well but haven't tried pushing anything to them. Anyway to preemtively check those as well?
Thanks!
2 Replies
Status changed to Awaiting Railway Response Railway • 20 days ago
19 days ago
Hey! We've identified an issue with our deploy pipeline that can cause railway up deploys to time out during initialization. We've just shipped a fix that should help — can you try deploying again and let us know how it goes?
If it's still failing, try deploying via GitHub instead as a workaround — push to your connected branch and the deploy will trigger automatically. That uses a different path and shouldn't be affected.
For your other services — they'd only be impacted when deploying, so anything already running is fine. If you run into the same issue deploying those, the GitHub workaround applies there too.
Status changed to Awaiting User Response Railway • 19 days ago
19 days ago
It looks like it's working. Thanks!
Status changed to Awaiting Railway Response Railway • 19 days ago
Status changed to Solved Railway • 19 days ago