2 months ago
Hello, we’re experiencing high levels of ECONNRESET errors from our next.js app (not hosted on railway) when connecting to our production Postgres database (hosted on railway) connected over the public railway network
We haven’t made any changes to the railway configuration or our code in a while, and it just started failing connections seemingly out of nowhere.
If anyone else is experiencing this please let me know, or if Railway staff is aware of the problem.
I’m currently not at my work computer and have just been messaged repeatedly that it is happening, but I can see that it (Postgres) seems to be online and that CPU and memory are consistent with what we’d expect. I don’t have access to logs or other metrics right now and will provide them when I’m able to I just know that it’s a big problem and I want to see if it’s happening from Railway’s side.
4 Replies
2 months ago
Your Postgres service experienced an improper shutdown around 14:18 UTC today and restarted at 14:20 UTC, during which it performed automatic crash recovery. The database is currently online and accepting connections. The ECONNRESET errors your app is seeing are consistent with that restart event, as active connections would have been dropped when the container stopped.
Status changed to Awaiting User Response Railway • 2 months ago
2 months ago
Update: other people are also experiencing this (from the Discord)
I also moved the service from US East to US West, waiting to see if that improves anything
Status changed to Awaiting Railway Response Railway • 2 months ago
2 months ago
Thanks for reporting this. As noted above, your database experienced a brief interruption at ~14:18 UTC due to some transient platform instability. It automatically recovered by ~14:20 UTC - the logs show a clean crash recovery with no data loss.
The issue resolved on its own before you moved regions. That said, if you prefer to stay on US West going forward, that's fine too.
Let us know if you see any further issues.
Apologies for the interruption.
Status changed to Awaiting User Response Railway • 2 months ago
Status changed to Awaiting Railway Response Railway • 2 months ago
Status changed to Solved proudparrot2 • 2 months ago