24 days ago
Hi Railway team,
My service calli-new-server (project: trustworthy-surprise, environment: production) keeps failing at "Build > Build image" with an infrastructure error. Your own diagnosis says: "the build daemon connection closed (buildkitd.sock: use of closed network connection) before any install or build step ran, and your Railway config was read correctly."
Failed deployment IDs: 4ecfca61 (10:39 GMT+2, Oct 28 2026), plus two more redeploys of the same commit (6390a2e) that failed the same way, and an earlier one at 10:24 GMT+2.
The same code base built successfully about an hour earlier (an earlier commit, deployment 6ce8b0c8, healthcheck passed), so this looks like a builder-side issue, possibly a faulty builder being assigned to my project.
I have redeployed 3 times without success. Could you please check the builder assigned to this service, clear its cache or route my builds to a different builder, and confirm when I can redeploy?
Thank you.
1 Reply
Status changed to Awaiting Railway Response Railway • 24 days ago
24 days ago
This is on our side. There is an active incident on our build infrastructure (https://status.railway.com/incident/ILLVW9WG, "Builds failing in US West"): builds are failing before any of your build steps run, with the build daemon connection dropping or the build machine never coming up, which is exactly what your deployments show. Your source, build configuration and dependencies are not at fault, and nothing needs to change on your end.
Running services are not affected. A fresh deployment of the same commit may get through in the meantime; otherwise please follow the status page for the all-clear, and redeploy once it is posted.
Status changed to Awaiting User Response Railway • 24 days ago
Status changed to Solved cocacocomai-create • 24 days ago