Hi Railway Team,

I'm experiencing a networking issue with one of my services where external access is completely
unreachable via TCP, despite the deployment health check passing successfully.

Service: flyerjam-staging.up.railway.app

Symptoms:
- Health check during deployment succeeds: [1/1] Healthcheck succeeded! (path: /api/health)
- DNS resolves correctly to 66.33.23.1
- TCP connection times out on both port 80 and port 443

curl -v --max-time 10 https://flyerjam-staging.up.railway.app/api/health
→ Trying 66.33.23.1:443... Connection timed out after 10006 milliseconds

What this means:
The service is running (internal health check passes), but Railway's edge proxy does not appear to be
routing external traffic to this service. This has been ongoing for several days.

What I've tried:
- Redeploying the service
- Verifying the public domain is configured in Networking settings
- Confirmed the start command uses --host=0.0.0.0 --port=$PORT

Could you please investigate why external traffic is not being routed to this service?

Thank you.