Unfortunately, once the volume data has been replaced with a fresh volume, we have no way to recover the previous data. Our database services are unmanaged, and we do not maintain internal snapshots or point-in-time recovery unless you had previously enabled volume backups on the service. Going forward, we strongly recommend enabling scheduled backups on your MongoDB volume from the service's Backups tab to protect against future data loss.

Thanks for the update.

I understand that backups were not enabled on my service, however this data loss happened immediately after the Railway platform incident and after following the recovery guidance provided in this thread.

Before considering this case closed, I would like to request a deeper verification from the infrastructure/storage team regarding the original volume attached to both MongoDB and Redis.

Specifically, I would like confirmation on:

• Whether the original volume IDs still exist internally
• Whether any temporary snapshots or recovery points were generated during the incident
• Whether the previous volumes can be re-attached in read-only mode for recovery attempts
• Whether the “fresh volume” deployment permanently replaced the original storage allocation

At the moment, it appears that following the suggested recovery steps resulted in irreversible data loss after a platform-side incident, so I would appreciate escalation to a human engineer for a final technical verification before the report is closed.

Thank you.

I just took a look at your account and it looks like a redeploy solved this for you. Are you back up and running? Please let me know if you're still having any issues. Sorry for the delay here.