a month ago
Project: natural-analysis (c20874fb-cd16-433e-a2e9-7e1732f5a69c)
Environment: production
PostgreSQL service ID: 04ae4f3f-a5de-48ef-8ef0-7c432b9bbe56
Issue: Hardware failure notification at 12:37 UTC July 14. Service shows online but won't accept database connections. API logs show "P1001: Can't reach database server at postgres.railway.internal:5432" since ~12:59 UTC
What you've tried: Attempted restart and redeploy — neither took effect
Region: europe-west4-drams3a
5 Replies
a month ago
Your Postgres service's latest deployment is stuck in DEPLOYING state, which is why your API cannot reach it. To fix this, open the Postgres service in your project, press Cmd+K (or Ctrl+K) to open the command palette, and select "Redeploy source image" - this re-pulls a fresh container image. A normal redeploy or restart from the 3-dot menu will not resolve this. Once Postgres is back up, redeploy your API service so it can re-establish connections.
Status changed to Awaiting User Response Railway • about 1 month ago
a month ago
Redeployment from source image is also stuck, and whole service is not answering for more than an hour
Status changed to Awaiting Railway Response Railway • about 1 month ago
a month ago
I have the same problem. Postgres up but unavailable because of a hw failure. same region btw
a month ago
Theres a hardware problem at the moment, and you're probably affected. You can follow the status by the banner above the dashboard. You should also have received an email if you were impacted
Status changed to Awaiting User Response Railway • about 1 month ago
a month ago
Ok, we are back
Status changed to Awaiting Railway Response Railway • about 1 month ago
Status changed to Solved staticdjacobs • about 1 month ago