an hour ago
Hi railway team,
We just faced this issue (as documented on https://station.railway.com/questions/networking-outbound-connection-problem-caafa330)
Here is the deployment hash where it happened: 0bb948af
We managed to recover by manually re-deploying the pod again.
2 Replies
Status changed to Awaiting Railway Response Railway • about 1 hour ago
an hour ago
first occurrence of the 502 connectivity error happened at Jun 20, 2026, 10:29:49 PM GMT+8.
an hour ago
This has been happening constantly (almost every weekend for the past 2 months at this point) and we haven't received any of much support, which is pretty frustrating :(
If there is some inherent unknown issue with the internal mesh that the team needs live data to investigate, i get it, but having to manually redeploy with no programmatic way to monitor these connectivity issues and automatically trigger a redeploy in railway is what makes this even more frustrating. Is there a way that we could possibly expose the outbound connectivity issues with the health check and trigger a redeploy of an existing pod?