This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(83.2, 74%, 18%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAD%3C/text%3E%3C/svg%3E)
The flexible PostgreSQL server became suddenly unavailable on June 22 around 11:50 PM EST and has remained unavailable since. Attempting to restart the database has not worked and returns an error from the Azure Portal. I tried stopping the database to start it again after, but it is now stuck in a stopping state.
The Azure Resource Health tool is confirming these availability issues, but its diagnostics do not find any issues. I am not sure what I need to do to resolve this.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(220.8, 47%, 31%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMS%3C/text%3E%3C/svg%3E)
Greeting!!
As I Understand that, your Azure PostgreSQL Flexible Database Server is unresponsive.
If your Azure PostgreSQL Flexible Server is unresponsive and not reacting to restart or stop commands, you're likely facing a deeper platform-level issue. Here's what might be going on and what you can do:
Possible Causes:
Service Health Incident: There may be an ongoing Azure outage or maintenance in your region. Check the Azure Service Health Dashboard for any alerts.
Stalled Restart: If the server status isn’t “Ready,” the restart option won’t be available in the portal.
Backend Failure: Some users have reported internal server errors when attempting restarts via CLI, even when resource usage (CPU, memory, storage) is normal.
What You Can Do:
az postgres flexible-server restart --name <server-name> --resource-group <resource-group>
We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution, please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.
Hi Malliah, I am not familiar with this forum, but I had posted an earlier answer, although I don't seem to be able to accept it or otherwise close this thread?
I’m glad to know that your issue has been resolved. Please continue using the Microsoft Q&A forum for any future queries.
Eventually after 40min the start option became available, although during that time nothing was communicated on the progress other than it was in a stopping state. After the manual start the database was available again.