My deployment builds and starts successfully, with internal health checks passing, but all external HTTP connections timeout.

Project: EquationParadise Web

Service: equation-paradise-web

Region: us-east4-eqdc4a

Domain: equation-paradise-web-production.up.railway.app

Port: 8080

Symptoms:

Deploy logs show: "Now listening on: http://[::]:8080" and "Application started"

Railway health check shows: "[1/1] Healthcheck succeeded!"

HTTP Logs tab is empty (no requests reaching container)

External curl/browser requests timeout after ~21 seconds

Ping to 66.33.22.102 times out (100% packet loss)

This worked correctly yesterday with identical configuration

What I've tried:

Regenerating the domain

Enabling Metal Build Environment

Restarting the service

Verifying PORT=8080 configuration

Confirmed app listens on 0.0.0.0:8080 (http://[::]:8080)

The container is running correctly - traffic simply isn't being routed from the public domain to it.