Skip to content
Build daemon connection error — 3 consecutive failed deploys, service
api
Anonymous
OP

23 days ago

Subject: Build daemon connection error — 3 consecutive failed deploys, service api

Project: api (ID 18a0b511-d994-42e7-83fc-fb2f24eb474a)

Service: api (ID f4751d18-2210-4172-bc7f-35d6e71b76bd)

Environment: production (ID c97c521e-54d5-466d-bec5-46d1d0b07626)

Region: sfo

Three consecutive deploys have failed with the identical error, across two different trigger methods (dashboard retry and railway up from the CLI):

  • 590877eb-efc3-47bf-bd61-8a89f1ed05da — 2026-10-28 07:58:27 UTC
  • 0c7625ec-69ba-4e10-bcbe-0daa36ef441a — 2026-10-28 08:06:23 UTC (dashboard retry)
  • 2fdaf25d-1bb4-4484-b0b1-d7a64423b9ba — 2026-10-28 08:15:41 UTC (CLI deploy, railway up)

Error (identical on all 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" >

It fails before any install/build step runs (npm ci/npm run build never start) — it's dying while allocating a build worker. The build logs also show 🚂 All aboard, next stop: builder v4 immediately beforehand, so this may be tied to the v4 builder rollout. The service itself is still online on the last successful deploy (98b062aa-99ab-4049-9afc-bfc7c105fefc, 2026-10-28 00:47:06 UTC) — this is only blocking new deploys, not causing downtime.

Can you check the build-daemon health for this project/region, or re-route the next build attempt to a different worker?

Solved

5 Replies

Status changed to Awaiting Railway Response Railway • 23 days ago


23 days ago

Thank you very much for reporting this issue, the issue has been raised to the team. Apologies for the inconvenience, will update once we have more info!


23 days ago

Apologies for the wait, the team opened an incident, you can track the issue here: https://status.railway.com/incident/ILLVW9WG


dizzydes90
EMPLOYEE

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


chandrika
EMPLOYEE

23 days ago

Sorry for the trouble. The build failures you're seeing ("build daemon returned an error" before any build step runs) are caused by an issue with our build infrastructure in US West, not by anything in your project or code. You don't need to change anything on your side.

We're working on a fix and tracking it here: https://status.railway.com/incident/ILLVW9WG

Your running services aren't affected. Redeploying may work in the meantime, but it can fail again until the fix is in. Once the incident is resolved, redeploying the same commit should build normally.


chandrika
EMPLOYEE

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.


Railway
BOT

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


Welcome!

Sign in to your Railway account to join the conversation.

Loading...