Is there any issue currently happening or that recently occurred with database VMs in West US 3 Zone?

Nilesh Jadhav 0 Reputation points
2026-08-24T22:21:15.5433333+00:00

Event 1139, FailoverClustering

The cluster service has detected an Azure host maintenance event has been scheduled. This maintenance event may cause the virtual machine hosting this node to become unavailable during this time.

I noticed this issue on two of our database VMs.

SQL Server on Azure Virtual Machines

2 answers

Sort by: Oldest
Most helpful Newest Oldest

  1. AI answer

    2026-08-24T22:21:34.6933333+00:00

    The event indicates Azure scheduled host maintenance for the VM host infrastructure. That can cause a brief pause, live migration, or a reboot depending on the maintenance type.

    Supported facts for this scenario:

    1. Azure periodically performs host infrastructure maintenance for VMs to improve reliability, performance, and security.
    2. If maintenance does not require a reboot, the VM can be paused briefly while the host is updated or live-migrated to another host.
    3. If maintenance does require a reboot, Azure provides planned maintenance notice and a self-maintenance window. Typical windows are about 35 days for host maintenance unless the maintenance is urgent, and about 14 days for hardware decommissioning.
    4. Inside the VM, Scheduled Events provides advance notice of upcoming availability impacts. These events are intended for automated handling, not manual operator action.
    5. A scheduled event proceeds after the NotBefore time unless it is acknowledged.
    6. In rare cases, Azure can cancel a scheduled event before impact, in which case the VM is not interrupted.

    For the specific question of whether there is a current or recent issue in West US 3 Zone affecting database VMs, the available information does not confirm a region-wide incident. It confirms that the two VMs received a scheduled host maintenance notification.

    To verify what is happening on those VMs:

    1. Query Scheduled Events from inside each VM using the Azure Instance Metadata Service endpoint:
      • curl -H Metadata:true http://169.254.169.254/metadata/scheduledevents?api-version=2020-07-01
    2. Check the event fields:
      • EventStatus to see whether it is Scheduled, Started, Completed, or Canceled
      • NotBefore for the earliest start time
      • Description to understand the maintenance action
      • EventSource to confirm whether it is platform-initiated or user-initiated
    3. If the workload is prepared, acknowledge the event so Azure can proceed before the timeout. Acknowledgment can be sent through the Maintenance Resource Provider endpoint with Azure CLI.

    Azure CLI example:

    az maintenance scheduledevents acknowledge --resource-group {resourceGroupName} --resource-type "virtualMachines" --resource-name {VMname} --scheduled-event-id {scheduledEventId} --subscription {subscriptionId}

    If both database VMs are in the same placement group or otherwise included in the same scheduled event, one acknowledgment allows the event to proceed for all resources listed in that event.

    References:

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

  2. Himaja Y 455 Reputation points Microsoft External Staff Moderator
    2026-08-25T09:22:48.6366667+00:00

    Hi @Nilesh Jadhav ,

    Thank you for reaching out to the Microsoft Q&A forum. 

    Based on the information provided, the Event ID 1139 (FailoverClustering) message indicates that Azure has scheduled maintenance on the underlying host infrastructure that is running the VM. This notification by itself does not confirm a service outage or a region-wide incident in West US 3. Instead, it is commonly generated when Azure performs planned platform maintenance to improve the reliability, security, or performance of the host infrastructure.

    During such maintenance activities, Azure may:

    • Live migrate the VM to another host with minimal interruption.
    • Briefly pause the VM while the host is updated.
    • Reboot the VM in cases where the maintenance requires a restart.

    Since you observed the notification on two database VMs, it is possible that both VMs are hosted on infrastructure included in the same maintenance wave or placement group. Azure Scheduled Events can be used to verify whether the maintenance notification originated from a planned platform operation. According to Microsoft documentation, Scheduled Events provide advance notice of host maintenance, reboots, live migrations, and other platform-initiated actions.

    At this time, the information shared does not indicate a confirmed West US 3 region-wide issue. To validate whether the VMs are part of a planned maintenance event, please check:

    1. Azure Service Health for any Planned Maintenance notifications affecting your subscription.
    2. Scheduled Events from within each VM using the Azure Instance Metadata Service (IMDS).
    3. Resource Health to determine whether the VM experienced any maintenance-related availability impact.

    If possible, please provide:

    • The VM Resource IDs (or VM names),
    • The output of the Scheduled Events query,
    • Any corresponding Service Health notification IDs,

    and we can help determine whether the notification was generated by a planned maintenance event or by another infrastructure activity.

    References:

    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.