a month ago
Our PostgreSQL database (Railway project "tranquil-insight", Hobby plan, service connected via kodama.proxy.rlwy.net:33277, database name railway) had all of its data wiped after running npx prisma migrate dev from our backend application. We believe Prisma detected schema drift between our migration history and the live database, and a reset was applied, resulting in all tables being emptied. We had real production data in this database (users, orders, chefs, payments, etc.) and no application-level backup, and we understand automatic backups aren't included on the Hobby plan.
What we're asking:
Even though our plan doesn't include standard backups, does Railway retain any storage-level snapshots or point-in-time recovery for Postgres volumes that could let us recover the database contents as they existed before this incident — even as a paid one-off recovery service, if that exists?
Timing:
The data loss happened today, July 16, 2026, approximately between 1:00 AM and 4:00 AM EAT.
Error messages/logs:
No error was thrown during the migration — the command completed, but tables were left empty afterward. Happy to share our Prisma migration history or terminal output if useful.
Project details:
Project: tranquil-insight
Environment: production
Service: Postgres (railway database)
Connection host: kodama.proxy.rlwy.net:33277
1 Replies
Status changed to Awaiting Railway Response Railway • about 1 month ago
a month ago
We're sorry about the data loss. We don't offer data restoration for user-initiated actions like this, including as a paid service. Going forward, you can enable volume backups or point-in-time recovery on your Postgres service so you can self-restore if this happens again.
Status changed to Awaiting User Response Railway • about 1 month ago
a month 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 • 29 days ago