24 days ago
Production Postgres deployment will not stay running. Database tab shows "The database deployment has stopped running." Repeated crashes since your ongoing incident.
Deploy logs showed: ERROR (catatonit:2): failed to exec pid1: No such file or directory
App cannot connect: write CONNECT_TIMEOUT postgres.railway.internal:5432
Volume ID: vol_q6prg0sl2nz6nggo
Region: EU West
My entire production app is down. Please stabilize the Postgres deployment or re-attach the volume to a healthy container. Urgent — production outage.
1 Replies
Status changed to Awaiting Railway Response Railway • 24 days ago
24 days ago
Apologies for this canned message but in an effort to help all our customers get back up and running, we are sending this bulk message. As you may know, we had a major interruption to our services yesterday. We've published a post-mortem if you'd like more information on the incident. It describes what happened and what we are doing to prevent it in the future. We are deeply sorry for the impact that it has had on you.
It is taking some time to bring everything back up, but we are working on it as fast as we can. In general, a redeployment should fix most service issues. Due to the volume of customers redeploying right now, builds and deploys may take longer than normal to process.
You can track recovery status here: https://status.railway.com/incident/KVZ1Z8GY
If you are still having other issues that might be related to the incident you can read more here: https://station.railway.com/community/road-to-recovery-post-gcp-outage-builds-d362e48c
Feel free to respond if your question has not been addressed.
Status changed to Awaiting User Response Railway • 24 days ago
17 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 • 17 days ago