43 minutes ago
Hello Railway Team,
Our production service has experienced two consecutive BUILD_IMAGE failures today (October 28, 2026), with the exact same BuildKit error:
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" >
Both builds failed before npm install or application code execution.
The same service deployed successfully approximately 1.5 hours earlier, with no application code or Railway configuration changes.
We also noticed another recent community report describing the identical BuildKit error.
Could Railway please confirm whether this is a known builder infrastructure issue and recommend the safest recovery procedure?
Our previous deployment remains operational, and we have paused further deployment attempts.
Thank you.
4 Replies
Status changed to Awaiting Railway Response Railway • 42 minutes ago
41 minutes ago
Same problem here
Status changed to Awaiting Railway Response Railway • 41 minutes ago
Status changed to Awaiting User Response Railway • 40 minutes ago
22 minutes ago
same here
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" >
Status changed to Awaiting Railway Response Railway • 22 minutes ago
Status changed to Awaiting User Response Railway • 22 minutes ago
vssy
same here 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" >
17 minutes ago
It's really frustrating because since that attack, the railway has not been the same.
Status changed to Awaiting Railway Response Railway • 17 minutes ago
Status changed to Awaiting User Response Railway • 17 minutes ago
muntazimkhan
It's really frustrating because since that attack, the railway has not been the same.
5 minutes ago
Same error on failing builds
Status changed to Awaiting Railway Response Railway • 5 minutes ago
Status changed to Awaiting User Response Railway • 5 minutes ago
