We are seeing the same issue on a separate production service using the same builder builder-bvqbzi. Seven consecutive clean deployments failed before the application build started, with the exact same NotFound: forwarding Ping: no such job error. We also reproduced it with NO_CACHE=1, so disabling build cache did not change the result. The previous production deployment remains healthy. Could Railway investigate this builder or route the affected builds to a healthy builder? We can provide deployment IDs privately if needed.

Same issue on our separate production service. Builds started failing on builder-bvqbzi this morning before any application build output, across both Railpack and Dockerfile attempts. Our sibling services deploy successfully on another builder. This is blocking merged production fixes; deployment IDs available privately.

Same here on a third separate production service (BrickRoster, US West, Hobby). Every build since 2026-09-16 ~20:00 ET has failed on builder-bvqbzi before any app output: six in a row, from GitHub pushes and railway up. Railpack builds fail with "railpack prepare exited with an error", and a Dockerfile build failed with "build daemon returned an error: NotFound: forwarding Ping: no such job". Our last successful build was 2026-09-16 17:46 ET and that deployment is still serving fine. Could you route our builds to a healthy builder? Deployment IDs available privately.

We’ve taken the affected builder out of rotation. Please retry your failed deployment and let us know if it still fails.