I'm experiencing 502 Bad Gateway errors across multiple projects on Railway.

All services show as "Online" with running replicas, but external requests

are not being routed to them.

Affected Projects:

• Project 1: 5a33e931-2604-4918-9714-402b1ef1338e (RemoteRide)
• Project 2: 8f000353-63d5-4509-a1de-fefb90033f77

Affected Services:

• https://remoterideweb.up.railway.app/ → 502
• https://remoteride.up.railway.app/swagger/index.html → 502
• Other services in second project also returning 502

Issue Details:

• All services show status: "Online"
• All replicas: Running (1/1)
• No crashes or deployment failures
• Internal health checks passing (e.g., /health-status endpoints responding)
• External requests timing out with 502 Bad Gateway
• Issue started: May 20, 2026
• Multiple projects affected simultaneously

What I've tried:

• Restarted services (no change)
• Verified services are healthy (they are)
• Checked logs (no startup errors)

Diagnosis:

This appears to be a Railway edge network/load balancer routing issue,

not a service crash or code problem. Services are healthy but unreachable

from outside.

Please investigate the routing layer for these projects.

Thank you.