Symptoms: * Deployment briefly shows “successful” then immediately changes to “crashed” * Local connections to DATABASE_URL now fail * No backups/snapshots are available for this volume Relevant logs: received fast shutdown request database system is shut down Then later: ERROR (catatonit:2): failed to exec pid1: No such file or directory Current behavior: * Service starts for a few seconds * Then crashes repeatedly Postgres logs mostly show normal checkpoints plus: * invalid length of startup packet * SSL negotiation errors * no PANIC/WAL corruption/fatal database errors visible Things already tried: * Restarting service * Redeploying * Attempting local DB connection * Checking backups (none available)

Postgres service sudden crash - Railway Central Station

Postgres service sudden crash

chrishalaby

PROOP

a month ago

Symptoms:

Deployment briefly shows “successful” then immediately changes to “crashed”
Local connections to DATABASE_URL now fail
No backups/snapshots are available for this volume

Relevant logs:

received fast shutdown request

database system is shut down

Then later:

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

Current behavior:

Service starts for a few seconds
Then crashes repeatedly

Postgres logs mostly show normal checkpoints plus:

invalid length of startup packet
SSL negotiation errors
no PANIC/WAL corruption/fatal database errors visible

Things already tried:

Restarting service
Redeploying
Attempting local DB connection
Checking backups (none available)

Solved

2 Replies

Status changed to Awaiting Railway Response Railway • about 1 month ago

mykal

EMPLOYEE

a month ago

Thanks for reaching out. 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 other services are having an issue, please try to give it a redeploy. 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-morterm, you can read our FAQ here

Status changed to Awaiting User Response Railway • about 1 month ago

Status changed to Solved mykal • about 1 month ago

mykal

Thanks for reaching out. 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 other services are having an issue, please try to give it a redeploy. 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-morterm, [you can read our FAQ here](https://station.railway.com/community/what-we-know-so-far-may-19th-2026-86354cdd)

chrishalaby

PROOP

a month ago

yes just redeoployed and works fine, thank you!

Status changed to Awaiting Railway Response Railway • about 1 month ago

Status changed to Solved Railway • about 1 month ago

Welcome!