Hi Railway team,

After the GCP outage on May 19-20, 2026, my Postgres service has been

stuck in a crash loop for ~18 hours and won't recover, even though the

rest of the platform is now Fully Operational (per status.railway.com).

== Symptoms ==

• App service selfless-integrity is Online and serves static routes

  (e.g. /login renders fine)

• Postgres service is in crash loop, repeatedly showing "Crashed N

  minutes ago" in the dashboard

• Error in deploy logs: catatonit:2 failed to exec pid1: No such file

  or directory

• Any route that needs DB hangs indefinitely (/pedidos, /importacoes)

• Volume postgres-volume appears intact (data not lost, just can't boot)

• Source image: ghcr.io/railwayapp-templates/postgres-ssl

== Context ==

@marcolombardini (community member, PRO plan) mentioned yesterday in a

similar thread that this failure mode requires manual intervention on

the platform side: "a human agent will need to investigate the container

creation failures on the platform side."

I am on Hobby plan, but my production app (a furniture logistics

operation in Brazil) has been fully blocked by this for ~18 hours.

== Project info ==

• Project ID: 0597ee55-88e4-4c48-90f1-532f934bd010
• Environment ID: 8f755185-2ab8-476a-8235-913be0df5c0a
• Postgres Service ID: 44796b1c-5ebe-429a-b778-a55b7ea9d8dd
• App that depends on it: selfless-integrity
• Region: [VOU_COMPLETAR_DEPOIS_DO_PASSO_1.3]
• Last known healthy: May 19, ~22:20 UTC (just before GCP outage)

Could a Railway engineer please inspect the container creation for this

Postgres service and restore it? The volume appears intact, the issue

is purely on the container init side. Thanks a lot.