mee to

We experienced a platform-wide service disruption on May 20 between 02:25 UTC and 07:57 UTC that affected all regions. Looking at your account, your Postgres service in the Repsify Production environment has been in a crashed state since April 24 UTC, and your Repsify-Server in the Testing environment has been crashed since May 17 UTC, both predating this incident. Your other services (including Repsify-Server in Production) currently show a healthy status. Now that the incident is resolved, please try redeploying the two crashed services. If they continue to crash after redeploying, check the deploy logs in your dashboard for any error messages that appear on startup.

Services continue to crash any time I restart them

Redeploy the service, not restart.

Redeploys are now paused?

Unfortunately Hobby, Free, and Trial deployments had to be paused due to a huge backlog.

https://status.railway.com/incident/KVZ1Z8GY

My production database continues to crash every after a redeployment

any additional info what's happening? logs?

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

looks like this is spamming occasionally within the deploy logs

This exact catatonit: failed to exec pid1 error has been reported in multiple Postgres/Railway services today after the May 19/20 platform incident (https://blog.railway.com/p/incident-report-may-19-2026-gcp-account-outage)

Try to do a redeploy of a database service (deploys should be working now, they're resolved it). If redeploy succeeds, redeploy the dependent app service after the DB is healthy.