5 months ago
- Project ID: a87120e9-c9bf-474d-8c96-ae9bf089950f
- Environment: production
- Postgres Service ID: 7df67e90-480d-4606-853d-d4f54869401d
- Endpoint: shortline.proxy.rlwy.net (line 25868)
- Symptom: TCP reachable, but psql/Prisma immediately fail with server closed the connection unexpectedly / P1001
- Time window: around 2026-02-11 22:57 UTC
- Repro commands:
- railway connect Postgres
- pg_isready -h shortline.proxy.rlwy.net -p 25868 -U postgres -d railway
Please verify proxy-to-instance health and safe restart guidance with existing volume preserved.
1 Replies
5 months 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 • 5 months ago
5 months 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 • 5 months ago