23 days ago
Category: Builds / Deployments
Severity: High. Production releases are blocked.
Project: Nocturne (production) Service: Project-Nocturne Project ID: 0d75b5da-29ad-44c9-9136-bedcafa589cc Environment ID: 44b48168-4f26-4f25-9c0f-495a1eff6fb1 Service ID: 398c4cf9-8bde-4eb5-818f-1db615066a7b Builder: Railpack 0.43.0, region sfo
What happens: Four consecutive deployments of commit 7aa54d5 (main) failed on 2026-10-28 UTC. The same commit deployed successfully at 06:37 (deployment 4afa7b68-8dd6-484a-89d0-a276b13c25d1). I made no code, dependency or config changes after that.
Deployment Time (UTC)
e811ec6e-4a26-47de-a53b-8945a45ab105 07:09
bf8496bc-8749-4452-b0e7-8099b599ed6a 07:27
6ee1a34f-a730-4e09-8bb8-bbc6569ccde9 07:54
56336fae-95f9-4347-964c-b6faebecf248 08:03 (manual redeploy, failed after about 5 minutes of building)
Error (first three):
Build Failed: build daemon returned an error < listing workers for Build: failed to list workers: Unavailable: connection error: desc = "error reading server preface: raw-read unix @->/run/buildkit/buildkitd.sock: use of closed network connection" >
The Railpack plan generates normally. The failure comes before any composer, npm or artisan step. Railway's own deployment diagnosis labels it infra_error.
Expected: The build completes, as it did at 06:37.
Request:
Root cause of the BuildKit daemon failures, not a "retry" answer.
Move my builds to a healthy builder, or fix the daemon, so I can ship.
Tell me whether credit applies for the failed builds and blocked releases.
Impact: I can't ship fixes or features to production. This kind of build infrastructure failure has happened to me repeatedly, and retrying doesn't resolve it.
2 Replies
Status changed to Awaiting Railway Response Railway • 23 days ago
23 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 • 23 days ago
23 days ago
The issue causing builds to fail in US West has been resolved. Builds are now completing normally. If a build failed during this incident, redeploying it should now succeed.
4 days 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 • 4 days ago