Subject: Postgres service stuck in DEPLOYING state - cannot connect to database

Hi Railway Support,

I'm experiencing an issue with my Postgres service in project "intown" (Project ID: 8a768293-e7c2-4d6b-8731-b3b022e96a93).

Problem:

The Postgres service (Service ID: 09dad55c-cfe8-427a-8522-e27398a7e2aa) has been stuck in "DEPLOYING" state for over 20 minutes. Multiple deployment attempts have failed:

- Deployment 92bf034c-bcbb-4c0d-a27c-c621c25fbee5 - stuck in DEPLOYING

- Deployment dd2b9b6f-1142-4e88-946b-59910b9f9326 - FAILED

- Several previous deployments also FAILED

Symptoms:

- No logs are available for the deployments

- Cannot connect to the database via public proxy (turntable.proxy.rlwy.net:31743)

- Connection attempts return "server closed the connection unexpectedly"

- The service uses image: ghcr.io/railwayapp-templates/postgres-ssl:17

Impact:

- My backend service cannot start because it depends on this Postgres database

- The database contains important production data (~220MB in postgres-volume)

- I cannot make a backup because the database is unreachable

What I've tried:

- Redeploy via CLI railway deployment redeploy)

- Waiting for deployment to complete (20+ minutes)

- Checking if there's a custom start command (there isn't)

Request:

Could you please:

1. Check why the Postgres service is stuck

2. Restart or fix the service without losing the data in postgres-volume

3. Help restore database connectivity

Environment: production

Volume: postgres-volume (ID: 7837ff68-a318-4789-8a64-7007dd718fe9)

Thank you for your help!