Hi Railway team,

I'm experiencing a persistent infrastructure issue where every deployment

fails at the "Create container" stage, despite no code or config changes.

Project details:

- Deployment ID: 128b7441-a9c1-413b-b029-b54b513a7246

- Last successful deploy: 7a9169a6 (April 15) - currently running

- Failed deploys since: 6 consecutive CREATE_CONTAINER failures

- Build phase: succeeds every time

- Image push: succeeds every time

- Container creation: fails in 8-9 seconds with "Failed to create deployment"

What I've already verified (with the help of the Railway AI agent):

- Code unchanged since April 15

- Config unchanged (railway.toml identical)

- DATABASE_URL correctly referenced to Postgres service

- Tested without volumes - still failed at CREATE_CONTAINER

- Plan was upgraded to Hobby - issue persists

The diagnosis from your AI agent points to an infrastructure-level issue

in the container scheduling layer.

Can you please investigate? My production service is stuck on the April 15

build and I cannot deploy any updates.

Thank you!