Your Postgres service is crash-looping with a container init failure that started during our service disruption on 2026-05-20. The volume is intact but the container image layers were likely lost during the outage. To recover, try triggering a redeploy of your Postgres service from the service's deployments page (click the three-dot menu on the latest deployment and select "Redeploy"), which will pull fresh image layers while preserving your data on the volume.

FWIW, mine started workign again after hitting redeploy. I'm genuinly frustrated that Railway has called it resolved when its obvious so many people are still having Postgres issues.

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.