Unplanned downtime with "Unknown Reason" / Platform Initiated cause – Azure Database for PostgreSQL Flexible Server

Vito Bahtijarević 20 Reputation points
2026-07-10T07:17:03.34+00:00

On July 7, 2026, 9:14 AM (local time) our production Azure Database for PostgreSQL – Flexible Server instance experienced an unplanned outage. We restarted the server manually, which restored connectivity.

A Resource Health event was generated with the following details:

  • currentHealthStatus: Unavailable (previous HealthStatus: Available)
  • cause: PlatformInitiated
  • title: "Unknown Reason"
  • details: "An unexpected problem is preventing restoring access to your Azure Database for PostgreSQL - Flexible server. We are working on resolving the problem." (no further detail provided)
  • type: Downtime

We were unable to find any further explanation in the Activity Log, Resource Health history, or Server Logs.

  1. Can you provide the root cause analysis (RCA) for this specific health event / outage?
  2. Was this related to a platform-side incident affecting the underlying compute/storage node, an automatic failover, patching, or another internal maintenance operation?

Please let us know if you need additional logs or diagnostic data from our side.On July 7, 2026, 9:14 AM (local time) our production Azure Database for PostgreSQL – Flexible Server instance experienced an unplanned outage. We restarted the server manually, which restored connectivity.

Azure Database for PostgreSQL
Answer accepted by question author
Manoj Kumar Boyini 19,590 Reputation points Microsoft External Staff Moderator
2026-07-22T18:41:37.31+00:00

Hi @Vito Bahtijarević

Your Azure Database for PostgreSQL Flexible Server underwent scheduled maintenance between the applicable maintenance start and end times. During this maintenance window, the server experienced a restart as part of Microsoft's routine maintenance process to keep the managed database service secure, stable, and up to date. These maintenance activities may include platform updates, security patches, and service improvements.

As a result, a brief interruption in connectivity can occur while the maintenance is being performed.

Please note that maintenance notifications may be issued at a regional level and can cover multiple PostgreSQL Flexible Server instances. Resource-specific maintenance details can be viewed in the Impacted Resources section of the corresponding Service Health notification.

Reference:
https://learn.microsoft.com/en-us/azure/postgresql/release-notes-maintenance/2026-april

Was this answer helpful?

1 person found this answer helpful.
0 comments

2 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Sina Salam 31,456 Reputation points Volunteer Moderator
    2026-07-13T14:44:50.5266667+00:00

    Hello Vito Bahtijarević,

    Welcome to the Microsoft Q&A and thank you for posting your questions here.

    I understand that your production Azure Database for PostgreSQL Flexible Server experienced unplanned downtime.

    Since the event is already classified as platform initiated, which means the reliable next step is to obtain Microsoft backend RCA for that exact Resource Health event. Azure Resource Health is the correct authority for resource-specific Azure platform impact and is designed to help diagnose and open support for service issues affecting a resource and since PCS is attending to this, hopefully it get resolve to time.

    The manual restart restored the service, but it did not identify the cause. So, open a support request directly from the affected server’s Resource Health event and request Microsoft backend RCA. This is required because customer-side PostgreSQL logs and Activity Logs may show symptoms, but they cannot expose all Azure fabric, compute, storage, or control-plane telemetry. Resource Health can classify platform, planned, unplanned, and user-initiated impact, but the exact internal cause must come from Microsoft backend investigation. - https://learn.microsoft.com/en-us/azure/service-health/resource-health-faq, and https://learn.microsoft.com/en-us/azure/service-health/resource-health-overview

    I hope this is helpful. Please! Do not hesitate to let me know if you have any other questions, steps or clarifications.

    Please do not close the thread by upvoting and accepting the answer if any part of it is helpful.

    Was this answer helpful?

    0 comments
  2. Christos Panagiotidis 3,551 Reputation points
    2026-07-13T13:43:56.36+00:00

    Hi! Resource Health’s “PlatformInitiated / Unknown Reason” message confirms the service detected a platform-side interruption, but it does not contain the internal root cause. Only Azure Support can correlate that timestamp with host, storage, maintenance, or failover telemetry and produce an RCA. Open a support request with the server resource ID, region, precise UTC interval, and Resource Health event ID. For production workloads, also review zone-redundant high availability.

    Was this answer helpful?

    0 comments

Your answer

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