a month ago
Hi Railway team,
I'm experiencing intermittent connectivity issues with my PostgreSQL database via the Railway proxy.
Database:
switchyard.proxy.rlwy.net:35587
Database name: nubill_db
Symptoms:
- Prisma throws initialization error P1001:
"Can't reach database server at switchyard.proxy.rlwy.net:35587"
- Application fails to start because DB becomes unreachable.
- External clients (TablePlus) connect and then disconnect randomly.
- Sometimes queries work, sometimes connection drops immediately.
- Even simple queries fail intermittently.
Important observations:
- Only 1 active connection exists in pg_stat_activity when issue occurs, so this is NOT connection saturation.
- The same deployment worked correctly 2 days ago with no code changes.
- Issue started during the current Railway deployment/metal outage shown on status page.
- Build logs also show "context canceled" errors during rebuilds.
This strongly suggests proxy/network instability rather than application-side issues.
Questions:
1) Is the PostgreSQL proxy affected by the current incident?
2) Is there any recommended workaround while the incident is ongoing?
3) Should we expect intermittent connectivity until incident resolution?
Thanks.
1 Replies
a month ago
Hey there!
It looks like this was a part of a recent incident we have. I just checked and it should be good to go now. Can you give it a look and let me know what you're seeing?
Post mortem is here in case you're interested in reading it.
https://blog.railway.com/p/incident-report-february-11-2026
Status changed to Awaiting User Response Railway • 26 days ago
19 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 • 19 days ago