Hi @Akel Saleh
Thank you for contacting to Microsoft QA, we will review your concern ad get back to you with the updates. Meanwhile could you provide a details requested in private message section.
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
At Tuesday 16 December 2025 at 4:09:07 am GMT+11, the Azure monitoring system received the following information regarding your Azure Database for PostgreSQL Flexible Server:
Your Azure Database for PostgreSQL - Flexible server is currently unavailable. We are working to resolve the problem.
This is the latest of many resource health alerts on the same resource for the past few days. We need this database back up and running, I've seen suggestions of restarting and can confirm that restarting via both the cli and the portal result in an error
Hi @Akel Saleh
Thank you for contacting to Microsoft QA, we will review your concern ad get back to you with the updates. Meanwhile could you provide a details requested in private message section.
Hello @Akel Saleh
If your Azure Database for PostgreSQL Flexible Server is currently unavailable, it may be due to unplanned downtime caused by issues such as hardware faults, networking problems, or software bugs. In such cases, Azure automatically performs recovery operations. If the database server is configured with high availability, a standby replica is activated, allowing clients to resume operations. If high availability is not configured and a restart attempt fails, a new database server is provisioned automatically. While Azure strives for high availability, outages can still occur, impacting your application. You can check for service outages through the Azure portal, where notifications will appear if your subscription is affected. Additionally, if you have set up alerts, you will receive email notifications regarding service issues impacting your resources
If the Answer is helpful, please click Accept Answer and Up-Vote 👍, so that this can be beneficial to other community members.
Hi @Akel Saleh
The mitigation steps have been provided by our internal team via the support case. Kindly follow them to proceed with resolving the issue.