Azure Database for PostgreSQL Flexible Server stuck Unavailable after planned maintenance — Restart grayed out, 5+ hours

Question

Environment

• Resource: Azure Database for PostgreSQL Flexible Server
• Region: East US 2
• Issue started: April 8, 2026 ~4:24 AM ET

Problem

My PostgreSQL Flexible Server has been unavailable since a planned maintenance event began this morning at 4:24 AM ET. The maintenance is showing as ongoing after 5+ hours, which is far beyond the expected window.

Current state in the Portal:

• Resource Health shows: Unavailable (Planned) — status ongoing
• Restart button is grayed out (not clickable)
• Restore option is available

The server appears to be stuck in a post-maintenance broken state and has not recovered automatically.

What I've tried

• Monitored Resource Health — no resolution updates
• Attempted manual restart — option is not available (grayed out)
• Attempted to open a support ticket — plan only includes Microsoft Q&A access

Ask

Can a support engineer investigate why this server is stuck post-maintenance and either recover it or advise on next steps short of a full restore? Given that Restore is available but creates a new server instance, I want to avoid that path if the original server can be recovered.Problem

My PostgreSQL Flexible Server has been unavailable since a planned maintenance event began this morning at 4:24 AM ET. The maintenance is showing as ongoing after 5+ hours, which is far beyond the expected window.

Current state in the Portal:

• Resource Health shows: Unavailable (Planned) — status ongoing
• Restart button is grayed out (not clickable)
• Restore option is available

The server appears to be stuck in a post-maintenance broken state and has not recovered automatically.

What I've tried

• Monitored Resource Health — no resolution updates
• Attempted manual restart — option is not available (grayed out)
• Attempted to open a support ticket — plan only includes Microsoft Q&A access

Ask

Can a support engineer investigate why this server is stuck post-maintenance and either recover it or advise on next steps short of a full restore? Given that Restore is available but creates a new server instance, I want to avoid that path if the original server can be recovered.

Answer 1

Hi @Ruchit Tripathi

We’re currently coordinating with the PG team to recover the issue at the service container level.

To unblock you sooner, we recommend proceeding with a restore (for example, Point‑in‑Time Restore, if backups are available) to create a new PostgreSQL Flexible Server and resume operations.

Please note from a billing perspective:

The restored server will start incurring charges as a new instance (compute and storage).

The original server will continue to incur charges while it exists, even if it’s unavailable.

Once you confirm the restored server is working as expected and delete the original server, billing for the old server will stop.

We’ll continue to monitor progress with the engineering team and share updates, but restoring is currently the fastest way to minimize downtime.