a month ago
Project: 0fd283e0-c2b6-4f8b-9488-80915242201b
▎ Postgres service: 68c6a8a2-34ef-4dfa-b2ec-6cbbceac3167
▎ Crashed deployment: 8a502899-3b8d-441c-b189-9472f57e1824
▎ Volume: vol_g74y4zehmsjbutbf
▎
▎ The Image Registry (Metal) incident has left our Postgres service unable to start: container
▎ crash-loops with ERROR (catatonit:2): failed to exec pid1: No such file or directory since
▎ 2026-05-19 22:14 UTC. Volume mounts cleanly every attempt, so data is intact — the image rootfs is
▎ broken. railway redeploy is blocked by the hobby-plan deploy pause, and we have no prior healthy
▎ deployment to roll back to (only one ever). Please rebuild/repin the Postgres image for this
▎ service so the next restart pulls a clean copy. Do not reset the volume — it holds production
▎ data.
2 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
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.
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 • about 1 month ago