All builds for my service scanner (project 40e31277-ca72-4caf-9b76-746b3005f3bc, service 06e32daa-3698-440d-b01b-1acc5e921c04) have failed since 2026-07-14 ~08:39 UTC. Production is still Online, serving from the last successful image.

This looks like the same class of issue as the recent "All builds FAIL on Metal builder builder-ryvidd" thread — a Metal builder wedged, not a build-config problem.

Every failed build logs only:

scheduling build on Metal builder "builder-nhmelg"

then fails in under 30 seconds with NO build output and zero instances created (it never reaches "fetching snapshot").

Already tried:

• Multiple railway up direct uploads — same result, always routed to builder-nhmelg
• Region pin on the service — did not change the builder assignment (reverted)
• Redeploying the last successful image (usePreviousImageTag) — works fine; only NEW builds fail
• Confirmed the web service in the SAME project builds fine on a different builder (builder-sskgan), and the Dockerfile builds locally

Please either:

1. Remove/repair builder-nhmelg from the pool, or
2. Re-route my scanner service to a different Metal builder, or
3. Disable Metal builder for this service so it uses the legacy non-Metal builder.

Happy to trigger a fresh build on request. Thanks!