The host hardware event from September 6 at 10:08 UTC has been resolved and your volume data (about 221 MB) is intact. What happened is that the container was re-placed onto a healthy host during recovery but the Postgres process never finished starting, which is an occasional edge case after a host migration. A fresh deploy from your side will bring it back. Open the Postgres service, press Cmd+K (Ctrl+K on Windows/Linux) to open the command palette, and select "Redeploy source image". This re-pulls a clean image and starts a new container on the healthy host. Your volume data is preserved through the redeploy, so nothing will be lost. For mission-critical workloads we advise implementing a high-availability configuration when possible, so a single-host event does not take production down.