Project: resilient-benevolence Project ID: fdc67388-c9c4-41c8-82cb-6f015b23300b Service: teampunch Service ID: 5e43bde0-be31-4533-a521-175fbc741636 Environment: production

Every deploy attempt via railway up has failed for the last several hours with the same error:

scheduling build on Metal builder "builder-xfqjvp"

fetched snapshot sha256:... (~107 kB)

fetching snapshot

unpacking archive

using build driver railpack-v0.38.0

railpack prepare exited with an error

The build fails immediately after "using build driver railpack-v0.38.0", before any install/build steps run, and before any further detail is logged.

Failed deployment IDs (all same error, same builder node "builder-xfqjvp"):

6a9bc3a5-ec9b-407b-a8d7-a852d82cf68e

0e124893-da55-4826-9ae9-051c251e4961

2f5147ad-51d4-44fc-a78d-929a94566866

eac51dd5-94df-4bcb-bc19-9507de65684a

d4542ca4-448a-42fd-bf3e-3075014e92ea

4cc78697-d8b4-4f17-bea0-49254512e5a7

08ffb43c-134d-4acd-9619-c50405e4aae3

352d59be-ae3e-4fa3-9ae2-3f40e1f5ded7

c1aeea3f-2c1c-4191-86d7-425079ec9538

89cdaeba-ea6b-415a-b051-26453d58bee1

c4e696ed-c885-485f-92d9-6981f4943fc4

efdbc7ab-2a72-46a6-8649-964c3dd8d3b0

I've ruled out a code-side cause: I redeployed the exact same source tree as our last successful production deployment (no changes at all) and it failed with the identical error. I also tried forcing "builder": "NIXPACKS" in railway.json, but the build logs still show railpack-v0.38.0 being used and the same failure.

This is a Node.js/Express + Prisma backend, previously deploying successfully on this same service. Nothing about the service's build/start commands has changed.

Could you check the health of builder node "builder-xfqjvp" for this service, or reset whatever cached build state might be causing "railpack prepare" to fail immediately? Happy to provide any additional deployment IDs or logs.

Thanks!