13 days ago
· Environment: production · Postgres service:
Id project: 0721159c-d0d6-421f-9d50-9b28304cac88
(kong-games-db)
At approximately 2026-08-08 ~13:00 UTC, the public schema of our production Postgres was reset (all business tables dropped and recreated empty) by an accidental Prisma migrate diff run that used the production connection string as --shadow-database-url. No explicit DROP DATABASE was issued.
I need to know, urgently: is there any automatic backup, volume snapshot, WAL archive, or PITR coverage that would let me restore this database to a point in time just before ~13:00 UTC on 2026-08-08? The Backups panel does not show an obvious restore point, so I'm asking whether anything exists at the infrastructure level. Speed matters — the service kept receiving traffic, so the sooner we act, the less risk of losing whatever pre-incident state may still be recoverable.
Please advise on any restore path available. Thank you.
1 Replies
13 days ago
Our databases are unmanaged, so automatic snapshots, WAL recovery, and PITR aren't available to restore your data unless you've enabled them on the service. Volume backups and point-in-time recovery are both native Railway features on Pro. We don't recover data lost to user-initiated actions. Going forward, enable volume backups on your stateful services so you can self-restore if this happens again.
Status changed to Awaiting User Response Railway • 13 days ago
6 days ago
This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!
Status changed to Solved Railway • 6 days ago