I'm experiencing an issue where all new deployments hang indefinitely at the "Creating containers..." stage after the Railway Metal upgrade, while an older deployment continues to work.

Working Deployment:

- Commit: "fix analyitcs error" (b0c8cee)

- Status: ACTIVE and running successfully for 2+ hours

- Deployed before the Railway Metal upgrade

Failing Deployments:

- All new deployments after the upgrade hang at "Deploy > Creating containers..." for 9+ minutes

- Build completes successfully (~60-90 seconds)

- Container never starts - hangs indefinitely at container creation

What I've verified:

1. Code is identical to the working deployment (reset backend to exact working commit)

2. Dockerfile is identical to working version

3. Build logs show successful build completion

4. No code changes between working and failing deployments

5. Issue started immediately after Railway Metal upgrade notification

Build logs show:

- Build completes successfully

- All Docker layers cached/created properly

- Prisma client generated successfully

- No build errors

Container logs:

- Container creation starts but never completes

- No error messages visible

- Deployment stuck at "Creating containers..." indefinitely

Environment:

- Region: us-east4-eqdc4a

- Service: agent-phone

- Dockerfile-based deployment

- Python 3.11-slim base image

Question:

Is this a known issue with Railway Metal migration? The old deployment works fine, but new deployments on Metal infrastructure hang. Should I roll back to the old region, or is there a fix in progress?