@RuttorfChristian-9443
This could have happened cause of the planned maintenance for the underlying resources for the Azure Database for Postgresql. Here is the document that explains the same.
You need to contact support to find if that exactly happened as they have telemetry to find that. Also the best approach to prevent this is below:
1) Retry Logic
2) Planned restart notification set up
Hope this helps.
Regards
Navtej S