Hi Railway team,

My web service deploys have been failing since today's private networking/traffic outage (incident started ~12:24 PM). The builds complete successfully but deploys hang indefinitely at "Starting Container" with no further output.

Project details:

• Region: us-east4

• Service: Web (Rails app using Dockerfile.web)

• Database: Railway-managed PostgreSQL

What's happening:

• The container starts and runs bin/rails db:migrate via the Docker entrypoint

• The migration step attempts to connect to Postgres and the TCP connection hangs forever — no timeout error, no output, just silence

• The build step completes fine (9 seconds cached, 331 seconds uncached)

What I've tried:

1. Restarted the Postgres service (shows healthy/online)

2. Switched DATABASE_URL to the private internal URL (fd12:...) — hangs

3. Switched DATABASE_URL to ${{database.DATABASE_PUBLIC_URL}} ([redacted].proxy.rlwy.net:[port]) — also hangs

4. Multiple redeploys after each change

5. Waited 10+ minutes per deploy attempt

Error from earlier deploy (when it did eventually timeout on private URL):

ActiveRecord::ConnectionNotEstablished: connection to server at "fd12:xxxx:xxxx:...", port 5432 failed: Connection timed out

Timeline:

• App was last deployed successfully ~3 months ago and was running fine

• No code changes — this started during today's networking outage

• Status page shows the incident as resolved, but connectivity is still broken for my project on both private and public endpoints

It appears the networking outage recovery didn't fully restore connectivity for my project/region. Could someone look into this? Happy to provide project ID or any other details via DM.

Thanks!