a month ago
Hello ,
I experienced an issue with my PostgreSQL service on Railway. The PostgreSQL service suddenly crashed, and after I restarted it, the service started working again.
However, I noticed that some data is missing. Specifically, the records I had inserted approximately one day before the crash are no longer visible in the database.
Could you please help me investigate what happened? I would like to understand whether there was a storage/persistence issue, rollback, backup restore, or any other problem that may have caused recent data loss.
Project details:
Service: PostgreSQL
Issue: Service crashed, then restarted successfully
Problem after restart: Data entered about one day before the crash is missing
Expected result: Previously inserted data should still exist after restart
Please let me know if you need any additional information from my side, such as project ID, service ID, logs, or approximate crash time.
Thank you.
4 Replies
a month ago
Your PostgreSQL service crash aligns with the major platform outage on May 19-20 that disrupted services across all regions, and your Postgres redeployed at 08:00 UTC on May 20, right as the incident resolved. Railway databases are unmanaged, so we do not have internal snapshots, WAL archives, or point-in-time recovery unless you had explicitly enabled backups or PITR before the crash, meaning we unfortunately cannot recover the missing data. Going forward, we strongly recommend enabling scheduled backups and/or PITR on your Postgres service's Backups tab to protect against future data loss.
Status changed to Awaiting User Response Railway • 26 days ago
a month ago
We have the same issue and the data is not recovering from the backups!
Status changed to Awaiting Railway Response Railway • 26 days ago
a month ago
Thank you for the clarification.
I understand that the PostgreSQL service was affected by the May 19–20 platform outage and that my database was redeployed around 08:00 UTC on May 20.
However, I would like to confirm one important technical detail: was there any storage volume replacement, database redeployment, or internal rollback during this incident that could explain why data inserted before the crash disappeared?
Could you please check whether the service was restarted using the same persistent volume, or whether a new volume/database instance was created during the recovery process?
I also understand that my current plan/package may not include automatic backups or PITR, and therefore I did not have a backup option enabled. However, this data loss appears to have happened as a result of a platform-level incident, not because of an action on my side.
Because of this, I am now facing data loss and operational difficulties caused by an issue outside of my control. I do not believe it is fair or reasonable for the full impact of this incident to fall entirely on me as the customer, especially when the outage originated from the platform side.
I understand that recovery may not be possible if no backups or PITR were enabled, but I would still appreciate a more detailed explanation of what exactly happened to my PostgreSQL service and its persistent storage during the incident.
Also, please let me know if there is any possible remediation, credit, or support option Railway can provide in this situation, considering that the data loss was related to a platform outage.
Thank you.
Status changed to Solved formince • 26 days ago
solocommercenl
We have the same issue and the data is not recovering from the backups!
a month ago
Do you know of any way to save it?
Status changed to Awaiting Railway Response Railway • 26 days ago
Status changed to Solved formince • 25 days ago