a month ago
Hi, my PostgreSQL service crashed with OOM last night (2026-04-09 around 15:48 UTC). After restarting both PostgreSQL and the backend service multiple times, the backend still cannot connect via postgres.railway.internal:5432 (connection timeout). External connection via maglev.proxy.rlwy.net:57754 also fails.
Project: oopsFrogs
Service: PostgreSQL (and oopsfrog-backend)
Error: connection to server at "postgres.railway.internal" port 5432 failed: timeout expired
Both services show as "Active" in the dashboard but the internal networking seems broken after the OOM crash. Please help.
3 Replies
Someone please help! I've been stuck with this problem and my App has been down for almost 1 day!!
a month ago
Is there anything that stands out (eg, errors) in the deployment logs for your Postgres service?
a month ago
Hey! Thank you for your reply, the condition resolved spontaneously, I don't know exactly what happened, but I did mistakenly add another project linked to the same service, I found it and deleted it, and the issue resolved spontaneously about 1 hour later.
Status changed to Solved 0x5b62656e5d • about 1 month ago