a month ago
I'm running a Django web application and a Django-Q worker in separate deployments, both of which connect to a Postgres instance. This has been stable for months and no changes have been made for 4 months. Now I see this message repeated in logs:
django.db.utils.OperationalError: connection to server at "postgres.railway.internal" (fd12:83b6:c8e:0:1000:1f:4b9e:1615), port 5432 failed: Connection timed out
Is the server running on that host and accepting TCP/IP connections?
Is there a way to get the DB up and running (or accepting connections again)? Any idea why this would start happening?
Thanks!
1 Replies
a month ago
Hello,
We had an incident earlier that caused some running workloads to be unexpectedly terminated while the status in the UI didn't properly update. This has since been resolved, but in some cases, you may need to redeploy your services.
You can find the post-mortem for the incident here: https://blog.railway.com/p/incident-report-february-11-2026
Our deepest apologies for the inconvenience this has caused.
Status changed to Awaiting User Response Railway • 27 days ago
20 days 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 • 20 days ago