11 hours ago
Hi Railway team,
My production MySQL database lost all of its user-created data and reset to
its initial seed state. I need help recovering it as urgently as possible.
WHAT HAPPENED
-
Around June 18–19, 2026 — coinciding with upgrading to a paid plan and
reorganizing into two projects — the MySQL database in my "patient-radiance"
project lost all data created by my app.
-
It now contains only initial seed data: the
userstable has just 1 row(the seed admin), and
SELECT COUNT(*) FROM vcards;returns 1, when itpreviously held many records.
-
My app lives in the "balanced-solace" project and connects to this MySQL.
WHAT I'VE ALREADY CHECKED
-
A persistent volume ("mysql-volume", ~150 MB) is attached to the MySQL service.
-
No backups exist (Backups are Pro-only and I'm not on Pro).
-
Binary logging is disabled (log_bin = OFF), so I can't replay from binlogs.
-
There is only one database service — I have no second/older copy and never
used any other database host.
-
I suspect a database service was deleted, or the volume/instance was
reinitialized, during the June 18–19 restructure/upgrade.
MY REQUESTS
-
Can you restore this MySQL volume or instance to a state from BEFORE
June 18, 2026?
-
If a database service was deleted around that date, can you recover the
deleted service or its underlying volume?
-
Do you retain any infrastructure-level volume snapshots for this service
(even on my current plan) that could be restored?
-
If recovery is possible, what is the retention window / how fast must I act?
IDENTIFIERS
- Database project: patient-radiance (MySQL)
- App project: balanced-solace
- Account email: [your Railway account email]
- Service IDs available on request.
This is time-sensitive — any data older than a few days is at risk of being
unrecoverable, so I'd appreciate a fast response. Thank you.
1 Replies
Status changed to Awaiting Railway Response Railway • about 11 hours ago
10 hours ago
We can see the volume attached to your MySQL service still holds roughly 200 MB of data, which is well beyond a fresh seed, so your earlier data is very likely still present on disk even though the running database only shows the seed tables. Please do not restart or redeploy the MySQL service in the meantime, as that can trigger a re-initialization and risk overwriting what's there. Our team will mount the volume to inspect and recover the older data, and we'll follow up here. (For context: backups are a Pro feature and none were configured on this service, and binary logging was off, so this manual recovery from the volume is the path forward.)
Status changed to Awaiting Railway Response angelo-railway • about 10 hours ago
Status changed to Awaiting User Response brody • about 5 hours ago