a month ago
Hi, my PostgreSQL service in project zooming-eagerness (Project ID: 9947aabc-2123-4476-b1aa-66fb287a2841, Service ID: b468957b-5217-449c-b5c5-ee0c6c49c5c8) has been down for over 30 minutes.
The latest deployment (76b3bc99) failed with the error: "The container was never created as the CREATE_CONTAINER step stayed pending and never completed." Your own AI diagnosis said this is a transient scheduling issue and to redeploy — I have tried redeploying multiple times but every attempt fails the same way.
The database is also unreachable externally at shinkansen.proxy.rlwy.net:34310 (getting P1001: Can't reach database server).
My entire production website (frenchiefomo.com) is down because of this. The previous successful deployment was on May 5th. Can you please force-schedule the container on a healthy node or restore from the last working state?
Region: europe-west4 Docker Image: ghcr.io/railwayapp-templates/postgres-ssl:17
1 Replies
Status changed to Awaiting Railway Response Railway • about 1 month ago
a month 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 • about 1 month ago
a month 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 • 28 days ago