Hello Railway team,

I'm experiencing a critical issue with my Postgres service that has been failing repeatedly for the past few hours.

Project Details:

• Project: KBZUmaster_bot (ID: 658d7f0c-643d-476d-a025-7ed4e8e5e4c7)

• Service: Postgres

• Plan: Hobby Plan (paid)

• Deployment ID: 02e13b59

Issue: The Postgres service keeps crashing with the error:

Symptoms:

1. Postgres service status shows "Failed" (red)

2. My application cannot connect to the database (ETIMEDOUT errors)

3. Both internal (postgres.railway.internal) and external (gondola.proxy.rlwy.net) addresses are unreachable

4. Manual restarts don't help - service fails immediately

5. The issue started after a routine deployment

What I've tried:

• Restarting the Postgres service multiple times

• Redeploying the application service

• Checking database connection strings (they are correct)

• Rolling back application code to previous working version

• Using ${{Postgres.DATABASE_URL}} reference instead of hardcoded URL

Impact: This is affecting production - my Telegram bot is completely down and cannot serve users.

Questions:

1. Is there a known issue with Postgres deployments right now?

2. How can I recover my Postgres service without losing data?

3. Should I create a new Postgres service and migrate data?

Any help would be greatly appreciated. This is urgent as it's affecting my production service.

Thank you!