a month ago
Hi Railway Team,
An accidental database reset occurred on our production MySQL service container today, August 31, 2026, at ~16:05 UTC.
Project & Service Details:
- Account: jabedakhter
- Project ID: 018f9acd-a450-4e0b-b15e-d316a552bc14
- Environment ID: 6f9cd5bf-bdc2-453f-a066-8446ecafe592
- Service: MySQL
- Public Host: reseau.proxy.rlwy.net:51845
- Database: railway
- Incident Time: August 31, 2026 at ~16:05 UTC
Could a Railway engineer please assist in rolling back/restoring the persistent storage volume for this MySQL container to the automated volume snapshot taken before 16:00 UTC today?
Thank you!
1 Replies
a month 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 • 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 • 28 days ago