Hello Railway Support,

I need platform-level assistance investigating a possible PostgreSQL volume/data mismatch and safely recovering production data.

Project: miraculous-creation

Environment: production

Service: PostgreSQL used by AI Hair Architect

I found the solved Central Station thread:

“Postgres data missing after apparent automatic major-version upgrade (16→18)”

I understand from Railway's response there that apparent upgrade evidence can be misleading, and that Railway staff can verify the actual volume/service history at platform level.

I would therefore prefer not to make assumptions about what happened in my project.

CURRENT EVIDENCE

1. The application's current production database connection has been checked read-only and reports zero application tables.

2. However, Railway's Database UI for the PostgreSQL service has displayed application tables including _prisma_migrations, AIUsageEvent, Analysis, AnalysisProposal, Appointment, and others.

3. PostgreSQL → Backups shows one backup:

Name: Pre-Security-Patch Backup

Age shown: 8 days ago

Size: 119 MB

There is no configured backup schedule.

1. I have NOT clicked Restore.

2. I have NOT deployed a restored volume.

3. I have NOT run Prisma migrations against the currently empty database.

4. I have NOT intentionally deleted the production database volume.

REQUEST

Could Railway please investigate this project at platform level and confirm:

• the complete PostgreSQL service/volume history around the last 2 weeks;
• which volume contained the historical production database;
• whether any volume was created, detached, replaced, deleted, or migrated;
• whether any such action originated from my account, Railway infrastructure, a deployment, or another operation;
• the exact source and timestamp of Pre-Security-Patch Backup;
• which volume that 119 MB backup belongs to;
• the PostgreSQL major version represented by that backup;
• whether the backup contains the previous production database volume;
• why Railway Database UI can display application tables while the current application database connection reports zero tables;
• whether the 119 MB backup can be safely restored and inspected;
• the safest Railway-supported recovery procedure.

If possible, please verify whether historical production data still exists inside that backup BEFORE I perform a restore.

Please DO NOT initiate a restore, migration, volume replacement, deletion, or other write operation without my explicit approval.

The priority is preservation and recovery of the historical production database and the existing Pre-Security-Patch Backup.

Thank you.