2 months ago
Hello, we are getting consistent timeouts when we are querying our backend api. We understand that the issue is marked as resolved, but our api health checks are still 503ing. We have suspicion that railway API has changed, and thus our checks to Postgres is totally failing. Please help, this is urgent. Our application is completely down as a result.
3 Replies
2 months ago
Your service and Postgres are both showing a successful deployment status, and your application logs show it is actively processing jobs with no errors or connection failures visible. We do not guarantee static outbound IPs unless you explicitly enable the Static Outbound IPs feature in your service settings, so if your external health checks rely on a specific IP, it may have changed. If you are connecting to an external Postgres (not the one in your project), you may need to update any IP allowlists on that database.
Status changed to Awaiting User Response Railway • about 2 months ago
2 months ago
We seem to be getting the same issue.
Status changed to Awaiting Railway Response Railway • about 2 months ago
2 months ago
The IP has not changed; the outbound IP listed in your service settings is accurate and correct.
Status changed to Awaiting User Response Railway • about 2 months ago
a month ago
This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!
Status changed to Solved Railway • about 1 month ago