4 months ago
Hi team, I need help with a data recovery issue.
After a billing suspension, Railway created a new Postgres instance instead of restoring the previous one. My appointments table is now empty, although other tables like clients and users still have data.
The logs show appointment activity up to July 31st (2025-07-31), just before the suspension.
Is there any way to recover the old volume or data?
Incident date: August 1–2
Postgres service: Created yesterday via Docker image
Thanks in advance for any help you can provide 🙏
1 Replies
4 months ago
It is not possible to recover your old data. This is why backups are important!
4 months ago
It’s also near impossible that the downtime could have wiped one specific table if it’s in the same database as the others. This is very likely user error, not the fault of Railway
Thanks a lot for taking the time to respond and clarify things — I really appreciate the support 🙏
Just to be clear: no one on the team ran any manual operation or deletion on the database. The first thing I did was check the logs — and they confirm appointment insertions up to July 31st, then nothing. Other tables (clients, users, etc.) remain intact, and no migrations were triggered.
I understand if recovery is impossible, but is there absolutely no way Railway could access a backup or volume snapshot from before the suspension? Even if unofficial, I'd really appreciate any lead.
Thanks again for your help!
4 months ago
If you did not take a backup, then there is no backup, sorry!
4 months ago
Piggybacking on this thread—can I prepay for 2 months in advance (e.g., via credits) to avoid suspension risks if I forget to make a payment?
4 months ago
Please open your own thread if you have questions. That is completely unrelated to the issue at hand here
4 months ago
!s
Status changed to Solved adam • 4 months ago