Heya y'all!
Thanks for surfacing this and as mentioned in the above linked thread, this may be due to a maxed-out CPU and connection count for your database. Do you know if any heavy queries or workflows were running at the time you experienced this?
Also, when you are able to view the DB, would you be able to let me know how much storage you are currently utilizing?
We are also looking into this on our end but one thing you can do to mitigate this when you experience this again would be to connect to your DB using the provided connection string shown under the Connection tab in the screenshot above. You can then still view and modify your DB - assuming the connection still works.