a month ago
All new deployments fail instantly at CREATE_CONTAINER (“Failed to create deployment.”) — builds succeed, zero runtime logs
Project vulnintel (4e8ce325-069a-4583-a49a-be33afd7c451), service web (47fb6ec4-dad8-4107-b93f-749f97c4942c), env production. Since 2026-07-08 ~21:20 UTC, every deployment that builds a new image fails at the Create container step in <1s. Build always completes and logs “image push”. Your dashboard diagnosis says “Infrastructure Error”. Tried RAILPACK and NIXPACKS, and moving the service from legacy sfo to us-west2 — same failure. Failed deployment IDs: 191cbc35, a86866e9, 34411de9, 711d9e59, a4c631d6, 9528fdd9. Redeploying the existing image works (78155a06, SUCCESS 21:26 UTC), so only freshly built images are affected. Nothing changed on our side since the last successful build (June 12). Please check why containers can’t be created from newly built images for this service.
1 Replies
Status changed to Awaiting Railway Response Railway • about 1 month ago
a month ago
This was caused by a platform-side issue with deployments in US West that has since been resolved: Deployments failing in US West. A fresh build should succeed now.
Status changed to Awaiting User Response Railway • about 1 month ago
a month ago
This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!
Status changed to Solved Railway • about 1 month ago