6 hours ago
Subject: URGENT – Production Postgres data accidentally wiped, need volume restore
Hi Railway team,
Our production Postgres database was accidentally reset today (Oct 19, 2026, around 16:00 BRT / 19:00 UTC) by a Prisma "migrate diff" command that used it as the shadow database. All tables were dropped and recreated empty.
Project: juventude sincera
Environment: produção
Service: Postgres (volume: postgres-volume)
We do not have backups enabled (Hobby plan). Could you please check whether there is any internal snapshot of this volume from before the incident and restore it? We are willing to upgrade to Pro if needed.
Please do not let the volume be overwritten. Thank you!
3 Replies
6 hours ago
We don't offer data restoration for user-initiated actions like this. Going forward, upgrading to Pro unlocks native volume backups on your service so it can self-restore if this happens again.
Status changed to Awaiting User Response Railway • about 6 hours ago
Railway
We don't offer data restoration for user-initiated actions like this. Going forward, upgrading to Pro unlocks native volume backups on your service so it can self-restore if this happens again.
6 hours ago
I understand restores are not offered for user-initiated actions. Still, could a Railway team member please check whether any infrastructure-level snapshot of this volume exists from before Oct 19, 2026 19:00 UTC? This is a small business's entire production data. We will upgrade to Pro right away if that helps. Thank you.
Status changed to Awaiting Railway Response Railway • about 6 hours ago
4 hours ago
We keep platform-level storage backups only to recover the platform itself after a failure on our side, such as a host or storage incident, so they aren't used to roll back a database after a migration or command run against it.
One thing worth checking yourself: if the Postgres service's Backups tab lists a restore point from before 19:00 UTC on Oct 19, upgrading to Pro unlocks restoring it, and you run that restore yourself from the same tab.
Status changed to Awaiting User Response brody • about 4 hours ago