Your Postgres service in the "authentic-essence" project is confirmed CRASHED, and the timing aligns with the ongoing major service disruption. Corrupted container images (missing pid1 binary) are a known consequence of the GCP infrastructure issues we are recovering from. Once recovery is further along, you should be able to redeploy the Postgres service to pull a fresh image. Your volume data should be intact since, as you noted, the volume mounts are fine. Try triggering a new deployment from the service's settings page to get a clean image.

2026-05-19T05:17:36.987464604Z [err] 202

2026-05-20T05:45:40.375248571Z [inf] Mounting volume on: /var/lib/containers/railwayapp/bind-mounts/71611532-90ab-46cf-9d17-7c4dc88ce606/vol_zw9hqmnq6s3512qm

ERROR (catatonit:2): failed to exec pid1: No such file or directory

mine is crashing too,no such file, tried redeploying and it still crashed

The Postgres service in "authentic-essence" is now showing a successful deployment as of 05:48 UTC today. The corrupted image issue was caused by the ongoing service disruption, and it looks like the latest redeploy pulled a clean image. If you're still seeing the pid1 error after this deployment, please try one more redeploy as the image registry has stabilized further since then.

hi there, tried to restart postgres 2 more times and it crashed immediately same error

Still facing the same issue , it keeps crashing , request this to be solved soon , facing a lot of heat from my clients .

Thanks for reaching out all. We sincerely apologize for the service disruption.

We're seeing recovery in our API, builds, and deployments. Your services should be back up now. If your services are having an issue, please try to give it a redeploy, not a restart. We'll publish a public postmortem covering what happened when we're fully recovered.

For all customers, we’ll publish a detailed postmortem outlining what happened and the steps we’re taking to prevent similar incidents in the future. For Enterprise customers, service credits are covered under our SLA and will be reviewed as part of our post-incident process. For ongoing context while we work on a post-mortem, you can read our FAQ here