Postgres data volume randomly set to be destroyed?

Hey all. I have an application running for a client one fly “app” is a Laravel app and the Other is a postgres database (timescale).

The client contacted me and said that the app has a 500 error when they try to login. I go check and it turns out the volume for the database is set to be destroyed, and a new volume was created a couple days ago and is now attached to the machine.

I’ve created volumes from all of the snapshots on the volume that’s set to be destroyed and none seems to have the data.

I don’t have an explanation on how this could occur unless there was a hardware failure of some sort?

Has anyone experienced anything like this?

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.