Postgres auto-update wiped all production data 18 hours ago
manugav7
PROOP

25 days ago

My Postgres service (project: SaumellAuto, service ID: d0ebaa63-0c10-4e5e-89c0-909d8a902aee)

was automatically redeployed ~18 hours ago via Docker auto-update (postgres:16).

After this redeployment, all data in the database was lost — tables exist but are empty.

Before this incident, the database had months of production data including delivery records.

Please check if there is any way to recover the data from before the redeployment

(snapshots, volume backups, WAL archives, etc.).

Timeline:

  • Previous Postgres deployment: 2 months ago
  • Auto-update redeployment that caused data loss: ~18 hours ago (July 26, 2026)
  • Discovery: July 27, 2026 ~9:00 AM

Database name: saumellauto

Project: SaumellAuto

Environment: production

Solved

3 Replies

Railway
BOT

25 days ago

Your Postgres service in SaumellAuto had no persistent volume attached, so the database was writing to ephemeral container storage, which is discarded on every redeploy. Our databases are unmanaged, so automatic snapshots, WAL recovery, and PITR aren't available unless you set up volume backups or PITR yourself. Going forward, attach a volume to your Postgres service so data persists across redeploys, and consider upgrading to Pro to enable native volume backups for an additional safety net.


Status changed to Awaiting User Response Railway 25 days ago


manugav7
PROOP

25 days ago

okay... so there is no way i can recover my data?


Status changed to Awaiting Railway Response Railway 25 days ago


Railway
BOT

25 days ago

The volume on your Postgres service was created after the auto-update redeployment, so at the time of the redeploy the database was writing to ephemeral container storage, which was discarded. We don't recover data lost in this scenario. The volume you've now attached will persist data across future redeploys.


Status changed to Awaiting User Response Railway 25 days ago


Railway
BOT

18 days 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 18 days ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...