Unexpected unavailable Azure Database for PostgreSQL Flexible Server

Philipp John 5 Reputation points
2025-05-12T08:58:32.1833333+00:00

Resource Type: Azure Database for PostgreSQL Flexible Server

Location: switzerlandnorth Availability

Status: undefined (Unplanned)

Title: UnknownReason Summary: Your Azure Database for PostgreSQL - Flexible server is currently unavailable. We are working to resolve the problem.

Azure Database for PostgreSQL
{count} votes

1 answer

Sort by: Most helpful
  1. PratikLad 1,745 Reputation points Microsoft External Staff Moderator
    2025-05-15T16:47:50.8533333+00:00

    Hi @ Philipp John

    Microsoft has identified an issue impacting your Azure Database for PostgreSQL – Flexible Server. The current undefined status and UnknownReason suggest that this is an early-stage incident still under investigation. As a result, service availability may be temporarily affected for Flexible Server instances in the impacted region.

    Here are some checks you can perform, along with possible reasons for the issue:

    • Check Azure Service Health: Go to the Azure Status Page and filter by Switzerland North Or, check the Azure Service Health blade in the Azure Portal for personalized impact and updates.
    • Set Up Alerts: Go to Resource health under Help and create a Resource Health alert to notify you when the issue is resolved or escalated.

    enter image description here

    • Azure Database for PostgreSQL Flexible Server goes through regular maintenance to ensure your database stays secure, stable, and up to date. During these maintenance windows, the server receives updates, patches, and new features. While some downtime may occur, the duration typically depends on how busy the server is with transactions at the time.
    • Failover Strategy: If your Server has geo-redundancy or backups in another region, consider failing over to a healthy region or restoring backups.

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.