Your database and its data are intact, nothing was erased. The notice you saw was a temporary outage banner: a host running your Postgres had a brief hardware issue, and as it stated, your service resumed automatically on the same volume once that resolved. Your Postgres has been running continuously since it was first created, on the same persistent volume, and it is serving connections now. The volume's usage showing 0 bytes is a known display glitch in the metrics panel and does not reflect what is actually stored, your data is still on disk. If you connect to the database you will see your tables and rows as before.

Thanks for the reply. I went through the logs and diagnostics and realized that after the fix was implemented, the PG instance remained stale and in a state or constant reboot. I had to stop services and redeploy and that worked and restored my instance. Maybe something to add for user later on. But thank you! I understand the challenges your team face must be a great deal of work! We'll try to stick around as you grow. Cheers

Glad to hear the stop-and-redeploy got your Postgres back to normal. Thanks for sharing what worked - that's useful feedback and we appreciate you sticking with us.