The Postgres service in your uat environment has no volume attached, and there are no unattached or orphaned volumes for it anywhere in the project. The service's data was stored on ephemeral container storage, which does not survive redeploys, so there is no volume, snapshot, or recoverable copy on our side. Going forward, attaching a volume to the Postgres service will ensure its data persists across redeploys.

Hi Railway team,

We need urgent help investigating a PostgreSQL service/volume in our UAT environment. Please do not modify any resources without confirming with us first.

Project: amused-consideration

Project ID: 830ddb17-f910-4606-a65d-b35349f30faa

Environment: uat

Environment ID: b1b33872-4999-41d2-b37b-bed2092f1af8

PostgreSQL service ID: 4f2a5666-5927-4f99-a4e1-18efdf0cf2f4

Previous PostgreSQL volume ID: d185803a-dffe-401a-9e49-02082022788b

Last known successful PostgreSQL deployment:

3b624669-8070-4800-9108-5bddb1231484

The Postgres service still exists, but Railway CLI/API currently show no active deployment and no attached volume. Our TalentIQ UAT application remains online, but /readyz returns 503 and the application logs show repeated database ENOTFOUND errors.

We previously had PostgreSQL running successfully and completed UAT validation against it.

Could you please confirm:

Whether the deleted/detached volume or underlying data can still be recovered.

Whether Railway has an internal snapshot or temporary recovery option.

The authoritative deletion/detachment timeline for the volume.

Whether another volume was attached after this volume was removed.

Whether the previous successful PostgreSQL deployment/storage can be temporarily restored for data recovery.

What operation caused or coincided with the removal.

Please do not create, attach, restore, redeploy or otherwise modify anything yet. We only want the event history and recovery options first.

Thank you,

Hassan

Grism L.L.C.

The Postgres service in your uat environment has no volume attached, and no volume belonging to it, attached or unattached, appears in the project. The data was on ephemeral container storage, which does not persist across redeploys. Attaching a volume to the Postgres service going forward will ensure its data survives redeploys.