20 days ago
I'm experiencing a transient container routing issue on my Node.js service. The app starts correctly, binds to 0.0.0.0:8080 (the Railway-provided PORT), and logs show it's running — but all healthcheck attempts return "service unavailable" and zero HTTP requests are reaching the app.
The exact same code and configuration passed the healthcheck successfully 8 minutes earlier on the same service. No code changes were made between the passing and failing deploys.
I've already tried redeploying multiple times with no success. This appears to be an infrastructure-level routing issue on Railway's end, not an application error.
Could you please investigate? My service is Backend and Postgres in project anotou-app.
Thank you.
1 Replies
20 days ago
Your production backend deployment at 12:09 UTC today shows the app starting and binding to port 8080, but the container was stopped about 7 minutes later, likely due to a healthcheck timeout with no requests reaching the service. This coincides with a major service disruption earlier today that has since been resolved, and a build performance issue that is still being monitored. Your homol environment deployment succeeded at 10:15 UTC, suggesting this is tied to residual effects from the incident rather than a code issue. Please try redeploying your production service now, as conditions have stabilized since these incidents were addressed.
Status changed to Awaiting User Response Railway • 20 days ago
Status changed to Solved ricardobsjunior • 19 days ago