Latest posts
-
Impact to Azure Virtual Machines in multiple regions
Impact Statement: Starting at 01:37 UTC on 26 June 2025, an alert for Virtual Machines is being investigated where customers using Virtual Machines may experience issues while performing service management operations (CRUD) create, read, update, and delete hosted in multiple regions.Current Status: We are actively investigating the impact, and the next update will be provided within 60…
-
Mitigated – Networking reduced availability in East US
What happened? Between 13:09 UTC and 18:51 UTC on 18 March 2025, a platform issue resulted in an impact to a subset of Azure customers in the East US region. Customers may have experienced intermittent connectivity loss and increased network latency sending traffic within as well as in and out of Azure’s US East Region. …
-
Active – Networking reduced availability in East US.
What happened? Between 13:09 UTC and 18:51 UTC on 18 March 2025, a platform issue resulted in an impact to a subset of Azure customers in the East US region. Customers may have experienced intermittent connectivity loss and increased network latency sending traffic within as well as in and out of Azure’s US East Region. …
-
Active – Networking degraded availability in East US
Starting at 13:09 UTC on 18 March 2025, a subset of Azure customers in the East US region may experience intermittent connectivity loss and increased network latency. We are aware of the issue and are actively working on mitigation workstreams to reroute traffic and reduce the impact for customers. The next update will be provided…
-
Mitigated – Power Event in West US region
Starting at 15:51 UTC and 17:15 UTC on 28 Feb 2025, a power event occurred in the West US region. This caused service disruptions to Azure services in the region. This incident is now mitigated. Impacted customers will continue receive detailed communications through their service health portal. This post will be removed in 10 minutes.…
-
Unexpected VM reboots – Applying Mitigation
Impact Statement: Starting at approximately 01:40 UTC on 25 Feb 2025, Azure customers in East US 2 may have experienced VM reboots and/or increased response latencies in the region. Current Status: A configuration change to a host health monitoring system in East US 2 caused the system to erroneously conclude that network devices on the…