Is Azure Virtual Machines down?
Current Azure Virtual Machines status is UP

We checked the official Azure Virtual Machines Status Page 3 min. 26 sec. ago. Learn more
Having a problem? Help Allie Gator keep this page accurate!

Report an Issue

Stay informed of future downtime with dashboards and notifications

Recent Azure Virtual Machines Outages and Issues

Follow the recent outages and downtime for Azure Virtual Machines in the table below.

Start Time

Type

Length

Message

Details

July 19, 2024 17:48 UTC

WARN

less than a minute

Awareness - Virtual Machines

See more
Start Time

July 19, 2024 17:48 UTC

Type WARN
Affected Components

Mexico Central - Virtual Machines

Spain Central - Virtual Machines

Message

Awareness - Virtual Machines

Details

We are aware of an issue that started on July 18, which resulted in customers experiencing unresponsiveness and startup failures on Windows machines using the CrowdStrike Falcon agent, affecting both on-premises and various cloud platforms (Azure, AWS, and Google Cloud).
It’s important to clarify that this incident is separate from the resolved Central US Azure outage (Tracking Id: 1K80-N_8). Microsoft is actively providing support to assist customers in their recovery on our platforms, offering additional guidance and technical assistance.
CrowdStrike has released a public statement on Windows Sensor Update - crowdstrike.com addressing the matter, and it includes recommended steps for a workaround. For environments specific to Azure, further instructions are provided below:
Updated: We approximate impact started as early as 04:09 UTC on the 18th of July, when this update started rolling out.
Update as of 10:30 UTC on 19 July 2024:
We have received reports of successful recovery from some customers attempting multiple Virtual Machine restart operations on affected Virtual Machines. Customers can attempt to do so as follows:
https://learn.microsoft.com/en-us/cli/azure/vm?view=azure-cli-latest#az-vm-restart
We have received feedback from customers that several reboots (as many as 15 have been reported) may be required, but overall feedback is that reboots are an effective troubleshooting step at this stage.
Additional options for recovery:
We recommend customers that are able to, to restore from a backup, preferably from before 04:09 UTC on the 18th of July, when this faulty update started rolling out.
How to restore Azure VM data in Azure portal
Troubleshoot a Windows VM by attaching the OS disk to a repair VM through the Azure portal
Once the disk is attached, customers can attempt to delete the following file:
Windows/System32/Drivers/CrowdStrike/C-00000291*.sys
The disk can then be attached and re-attached to the original VM.
We can confirm the affected update has been pulled by CrowdStrike. Customers that are continuing to experience issues should reach out to CrowdStrike for additional assistance.
Additionally, we're continuing to investigate additional mitigation options for customers and will share more information as it becomes known.
This message was last updated at 17:43 UTC on 19 July 2024

July 19, 2024 17:48 UTC

WARN

about 16 hours

Awareness - Virtual Machines

See more
Start Time

July 19, 2024 17:48 UTC

Type WARN
Affected Components

Mexico Central - Virtual Machines

Spain Central - Virtual Machines

Message

Awareness - Virtual Machines

Details

We are aware of an issue that started on July 18, which resulted in customers experiencing unresponsiveness and startup failures on Windows machines using the CrowdStrike Falcon agent, affecting both on-premises and various cloud platforms (Azure, AWS, and Google Cloud).
It’s important to clarify that this incident is separate from the resolved Central US Azure outage (Tracking Id: 1K80-N_8). Microsoft is actively providing support to assist customers in their recovery on our platforms, offering additional guidance and technical assistance.
CrowdStrike has released a public statement on Windows Sensor Update - crowdstrike.com addressing the matter, and it includes recommended steps for a workaround. For environments specific to Azure, further instructions are provided below:
Updated: We approximate impact started as early as 04:09 UTC on the 18th of July, when this update started rolling out.
Update as of 10:30 UTC on 19 July 2024:
We have received reports of successful recovery from some customers attempting multiple Virtual Machine restart operations on affected Virtual Machines. Customers can attempt to do so as follows:
https://learn.microsoft.com/en-us/cli/azure/vm?view=azure-cli-latest#az-vm-restart
We have received feedback from customers that several reboots (as many as 15 have been reported) may be required, but overall feedback is that reboots are an effective troubleshooting step at this stage.
Additional options for recovery:
We recommend customers that are able to, to restore from a backup, preferably from before 04:09 UTC on the 18th of July, when this faulty update started rolling out.
How to restore Azure VM data in Azure portal
Troubleshoot a Windows VM by attaching the OS disk to a repair VM through the Azure portal
Once the disk is attached, customers can attempt to delete the following file:
Windows/System32/Drivers/CrowdStrike/C-00000291*.sys
The disk can then be attached and re-attached to the original VM.
We can confirm the affected update has been pulled by CrowdStrike. Customers that are continuing to experience issues should reach out to CrowdStrike for additional assistance.
Additionally, we're continuing to investigate additional mitigation options for customers and will share more information as it becomes known.
This message was last updated at 17:43 UTC on 19 July 2024

July 19, 2024 09:28 UTC

WARN

less than a minute

Awareness - Virtual Machines

See more
Start Time

July 19, 2024 09:28 UTC

Type WARN
Affected Components

Israel Central - Virtual Machines

West US - Virtual Machines

Jio India West - Virtual Machines

Jio India Central - Virtual Machines

East US 2 - Virtual Machines

West Central US - Virtual Machines

West US 2 - Virtual Machines

‡West US 3 - Virtual Machines

Canada East - Virtual Machines

UK South - Virtual Machines

Switzerland North - Virtual Machines

Switzerland West - Virtual Machines

Brazil South - Virtual Machines

Brazil Southeast - Virtual Machines

East US - Virtual Machines

Central US - Virtual Machines

North Central US - Virtual Machines

South Central US - Virtual Machines

Canada Central - Virtual Machines

North Europe - Virtual Machines

West Europe - Virtual Machines

France Central - Virtual Machines

France South - Virtual Machines

UK West - Virtual Machines

Norway East - Virtual Machines

Norway West - Virtual Machines

Germany North - Virtual Machines

Germany West Central - Virtual Machines

Sweden Central - Virtual Machines

‡Sweden South - Virtual Machines

Poland Central - Virtual Machines

Italy North - Virtual Machines

Southeast Asia - Virtual Machines

East Asia - Virtual Machines

Australia East - Virtual Machines

Australia Southeast - Virtual Machines

Australia Central - Virtual Machines

Australia Central 2 - Virtual Machines

Central India - Virtual Machines

Japan East - Virtual Machines

Korea Central - Virtual Machines

South Africa West - Virtual Machines

South Africa North - Virtual Machines

UAE Central - Virtual Machines

UAE North - Virtual Machines

‡Qatar Central - Virtual Machines

West India - Virtual Machines

South India - Virtual Machines

Japan West - Virtual Machines

Korea South - Virtual Machines

Message

Awareness - Virtual Machines

Details

We have been made aware of an issue impacting Virtual Machines running Windows Client and Windows Server, running the CrowdStrike Falcon agent, which may encounter a bug check (BSOD) and get stuck in a restarting state. We approximate impact started around 19:00 UTC on the 18th of July.
We recommend customers that are able to, to restore from a backup from before this time.
Alternatively, customers can attempt to repair the OS disk offline by following these instructions: 
Attach an unmanaged disk to a VM for offline repair
Disks that are encrypted may need these additional instructions:
Unlocking an encrypted disk for offline repair
Once the disk is attached, customers can attempt to delete the following file. 
Windows/System/System32/Drivers/CrowdStrike/C00000291*.sys
The disk can then be attached and re-attached to the original VM.
We recommend customers that are continuing to experience issues to reach out to CrowdStrike for additional assistance.
Additionally, we are continuing to investigate additional mitigation options for customers and will share more information as it becomes known.
This message was last updated at 09:26 UTC on 19 July 2024

July 19, 2024 09:28 UTC

WARN

about 8 hours

Awareness - Virtual Machines

See more
Start Time

July 19, 2024 09:28 UTC

Type WARN
Affected Components

Israel Central - Virtual Machines

West US - Virtual Machines

Jio India West - Virtual Machines

Jio India Central - Virtual Machines

East US 2 - Virtual Machines

West Central US - Virtual Machines

West US 2 - Virtual Machines

‡West US 3 - Virtual Machines

Canada East - Virtual Machines

UK South - Virtual Machines

Switzerland North - Virtual Machines

Switzerland West - Virtual Machines

Brazil South - Virtual Machines

Brazil Southeast - Virtual Machines

East US - Virtual Machines

Central US - Virtual Machines

North Central US - Virtual Machines

South Central US - Virtual Machines

Canada Central - Virtual Machines

North Europe - Virtual Machines

West Europe - Virtual Machines

France Central - Virtual Machines

France South - Virtual Machines

UK West - Virtual Machines

Norway East - Virtual Machines

Norway West - Virtual Machines

Germany North - Virtual Machines

Germany West Central - Virtual Machines

Sweden Central - Virtual Machines

‡Sweden South - Virtual Machines

Poland Central - Virtual Machines

Italy North - Virtual Machines

Southeast Asia - Virtual Machines

East Asia - Virtual Machines

Australia East - Virtual Machines

Australia Southeast - Virtual Machines

Australia Central - Virtual Machines

Australia Central 2 - Virtual Machines

Central India - Virtual Machines

Japan East - Virtual Machines

Korea Central - Virtual Machines

South Africa West - Virtual Machines

South Africa North - Virtual Machines

UAE Central - Virtual Machines

UAE North - Virtual Machines

‡Qatar Central - Virtual Machines

West India - Virtual Machines

South India - Virtual Machines

Japan West - Virtual Machines

Korea South - Virtual Machines

Message

Awareness - Virtual Machines

Details

We have been made aware of an issue impacting Virtual Machines running Windows Client and Windows Server, running the CrowdStrike Falcon agent, which may encounter a bug check (BSOD) and get stuck in a restarting state. We approximate impact started around 19:00 UTC on the 18th of July.
We recommend customers that are able to, to restore from a backup from before this time.
Alternatively, customers can attempt to repair the OS disk offline by following these instructions: 
Attach an unmanaged disk to a VM for offline repair
Disks that are encrypted may need these additional instructions:
Unlocking an encrypted disk for offline repair
Once the disk is attached, customers can attempt to delete the following file. 
Windows/System/System32/Drivers/CrowdStrike/C00000291*.sys
The disk can then be attached and re-attached to the original VM.
We recommend customers that are continuing to experience issues to reach out to CrowdStrike for additional assistance.
Additionally, we are continuing to investigate additional mitigation options for customers and will share more information as it becomes known.
This message was last updated at 09:26 UTC on 19 July 2024

July 19, 2024 04:43 UTC

WARN

about 5 hours

Investigating issues in the Central US region

See more
Start Time

July 19, 2024 04:43 UTC

Type WARN
Affected Components

Central US - Automation

Central US - Azure AI Metrics Advisor

Central US - Azure AI Search

Central US - Azure AI Anomaly Detector

Central US - Azure AI Immersive Reader

Central US - Azure AI Vision

Central US - Content Moderator

Central US - Face API

Central US - Language Understanding (LUIS)

Central US - Azure AI Video Indexer

Central US - Azure Analysis Services

Central US - Azure Arc enabled data services

Central US - Azure Arc enabled Kubernetes

Central US - Azure Arc enabled servers

Central US - Azure Cache for Redis

Central US - Azure Chaos Studio

Central US - Azure Communications Gateway

Central US - Azure Container Apps

Central US - Azure Container Instances

Central US - Azure Container Registry

Central US - Azure Container Service

Central US - Azure Cosmos DB

Central US - Azure Data Explorer

Central US - Azure Data Factory

Central US - Azure Data Lake Storage Gen1

Central US - Azure Data Share

Central US - Azure Database for PostgreSQL

Central US - Azure Database for PostgreSQL flexible servers

Central US - Azure Database Migration Service

Central US - Azure Database Migration Service (classic)

Central US - Azure Databricks

Central US - Azure DDoS Protection

Central US - Azure Dev Spaces

Central US - Azure DevTest Labs

Central US - Azure Firewall

Central US - Azure Firewall Manager

Central US - Azure Functions

Central US - Azure HPC Cache

Central US - Azure IoT Central

Central US - Azure IoT Hub

Central US - IoT Hub Device Provisioning Service

Central US - Azure Key Vault Managed HSM

Central US - Azure Kubernetes Service (AKS)

Central US - Azure Machine Learning

Central US - Application Insights

Central US - AutoScale

Central US - Log Analytics

Central US - Azure Red Hat OpenShift

Central US - Azure Route Server

Central US - Azure Service Fabric

Central US - Azure SignalR Service

Central US - Azure Site Recovery

Central US - Azure Spring Cloud

Central US - Azure SQL Database

Central US - Azure Stream Analytics

Central US - Azure Synapse Analytics

Central US - Azure Time Series Insights

Central US - Azure Update Manager

Central US - Azure Virtual Network Manager

Central US - Azure VMware Solution

Central US - Azure Web PubSub

Central US - Cloud Services

Central US - Data Lake Analytics

Central US - Event Grid

Central US - Event Hubs

Central US - ExpressRoute Circuits

Central US - ExpressRoute Gateways

Central US - HDInsight

Central US - Microsoft Entra Domain Services

Central US - Network Infrastructure

Central US - Network Watcher

Central US - Notification Hubs

Central US - Scheduler

Central US - Service Bus

Central US - SQL Server Stretch Database

Central US - Storage Accounts

Central US - Virtual Machine Scale Sets

Central US - Virtual Machines

Central US - Virtual Network

Central US - Virtual WAN

Central US - VPN Gateway

Central US - Web Application Firewall

Non-Regional - Azure Virtual Desktop

Non-Regional - Azure Front Door

Non-Regional - Azure AI Translator

Non-Regional - Azure Managed Applications

Non-Regional - Universal Print

Non-Regional - Azure Migrate

Central US - Azure AI Speech

Central US - Azure File Sync

Central US - Application Gateway

Central US - Azure Backup

Central US - Azure Managed Instance for Apache Cassandra

Central US - Azure AI services

Central US - Azure Automanage

Central US - Azure NetApp Files

Central US - Azure Private Link

Central US - Azure AI Language

Central US - Media Services

Central US - Azure NAT Gateway

Central US - Batch

Central US - Key Vault

Central US - Load Balancer

Central US - Logic Apps

Central US - Microsoft Azure Attestation

Central US - API Management

Central US - App Configuration

Central US - App Service

Central US - App Service (Linux)

Central US - Web Apps Linux

Central US - Application Gateway for Containers

Message

Investigating issues in the Central US region

Details

Impact Statement: Starting at approximately 21:56 UTC on 18 Jul 2024, a subset of customers may experience issues with multiple Azure services in the Central US region including failures with service management operations and connectivity or availability of services.
Current Status: We are aware of this issue and have engaged multiple teams. We’ve determined the underlying cause. A backend cluster management workflow deployed a configuration change causing backend access to be blocked between a subset of Azure Storage clusters and compute resources in the Central US region. This resulted in the compute resources automatically restarting when connectivity was lost to virtual disks. Mitigation has been confirmed for all Azure Storage clusters, the majority of services are now recovered. A small subset of services is still experiencing residual impact. Impacted customers will be continuing to communicate throuhg Azure service health portal. The next update will be provided in 60 minutes, or as events warrant.
https://learn.microsoft.com/azure/architecture/resiliency/recovery-loss-azure-region .
This message was last updated at 04:38 UTC on 19 July 2024

2024-07-20 18:01:51 UTC UTC

STATUS

? minutes

Sign in to view more status history.

See more

2024-07-20 18:01:51 UTC UTC

STATUS

? minutes

Sign in to view more status history.

See more

2024-07-20 18:01:51 UTC UTC

STATUS

? minutes

Sign in to view more status history.

See more

2024-07-20 18:01:51 UTC UTC

STATUS

? minutes

Sign in to view more status history.

See more

2024-07-20 18:01:51 UTC UTC

STATUS

? minutes

Sign in to view more status history.

See more

Sign Up for More Azure Virtual Machines History

StatusGator has over 9 years of Azure Virtual Machines status history.

No outages or status changes in the last 24 hours

Azure Virtual Machines status, last 24 hours:

7:00 PM
1:00 AM
7:00 AM
1:00 PM
7:00 PM
7:00 PM
7:00 AM
7:00 PM
  • Up: 24 hours

  • Warn: 0 minutes

  • Down: 0 minutes

Azure Virtual Machines Outage and Status History

We've been monitoring Azure Virtual Machines outages since March 22, 2015.
Here's the history of service outages we've observed from the Azure Virtual Machines Status Page:

Instant enriched data from
3,970 status pages

About Our Azure Virtual Machines Status Page Integration

Azure Virtual Machines is a Cloud Infrastructure and Microsoft solution that StatusGator has been monitoring since March 2015. Over the past over 9 years, we have collected data on on more than 1,804 outages that affected Azure Virtual Machines users. When Azure Virtual Machines publishes downtime on their status page, they do so across 5,887 components and 65 groups using 3 different statuses: up, warn, and down which we use to provide granular uptime metrics and notifications.

More than 2,400 StatusGator users monitor Azure Virtual Machines to get notified when it's down or has an outage. This makes it one of the most popular cloud infrastructure services monitored on our platform. We've sent more than 169,900 notifications to our users about Azure Virtual Machines incidents, providing transparency and peace of mind. You can get alerts by signing up for a free StatusGator account.

If Azure Virtual Machines is having system outages or experiencing other critical issues, red down notifications appear on the status page. In most cases, it means that core functions are not working properly, or there is some other serious customer-impacting event underway.

Warn notifications are used when Azure Virtual Machines is undergoing a non-critical issue like minor service issues, performance degradation, non-core bugs, capacity issues, or problems affecting a small number of users.

Azure Virtual Machines does not post separate notifications for planned maintenance work so we are unable to send notifications when maintenance windows begin. If you need Azure Virtual Machines maintenance notifications, please email us.

Azure Virtual Machines does not publish a feed of proactive maintenance events on their status page at this time. If they do, be sure to let us know and we'll aggregate Azure Virtual Machines maintenance events into your unified calendar.

When Azure Virtual Machines posts issues on their status page, we collect the main headline message and include that brief information or overview in notifications to StatusGator subscribers.

When Azure Virtual Machines has outages or other service-impacting events on their status page, we pull down the detailed informational updates and include them in notifications. These messages often include the current details about how the problem is being mitigated, or when the next update will occur.

Because Azure Virtual Machines has several components, each with their individual statuses, StatusGator can differentiate the status of each component in our notifications to you. This means, you can filter your status page notifications based on the services, regions, or components you utilize. This is an essential feature for complex services with many components or services spread out across many regions.

Frequently Asked Questions

Can’t find your question? Email us to arrange a time to discuss. We’d love to chat!

Azure Virtual Machines Down?

Are you experiencing issues with Azure Virtual Machines? Sign up to receive notifications when Azure Virtual Machines publishes outages.

Azure Virtual Machines Down or not working? Never be taken by surprise again.

StatusGator tells you when your cloud services have problems or their statuses change. We monitor the official status pages of more than 3,970 cloud services in real-time, aggregate the data, and send you alerts via email, Slack, Teams, SMS, and more.

Looking for recent downtime and outages of Azure Virtual Machines?

Sign up for StatusGator and see all historical information about Azure Virtual Machines outages and performance issues. Get free, instant notifications when Azure Virtual Machines goes down.

No outages or status changes in the last 24 hours

Azure Virtual Machines status, last 24 hours:

7:00 PM
1:00 AM
7:00 AM
1:00 PM
7:00 PM
7:00 PM
7:00 AM
7:00 PM
  • Up: 24 hours

  • Warn: 0 minutes

  • Down: 0 minutes

Azure Virtual Machines Outage and Status History

We've been monitoring Azure Virtual Machines outages since March 22, 2015.
Here's the history of service outages we've observed from the Azure Virtual Machines Status Page: