Is Azure Resource Manager down?
Current Azure Resource Manager status is UP

Impact Statement: Starting at 02:41 UTC on 23 Mar 2023, A subset of customers in West Europe may experience errors while performing azure resource manager create/update/read/delete operations.  
Current Status: We are aware of this issue and are actively investigating. The next update will be provided in 60 minutes, or as events warrant.
This message was last updated at 06:08 UTC on 23 March 2023

Impact Statement:
Starting around 20:19 UTC on 7 February 2023, a utility power surge in the Southeast Asia region tripped a subset of cooling units offline in one of the Availability Zones. While working to restore the cooling units, temperatures in the datacenter increased and we have proactively powered down a number of compute and storage units to avoid damage to hardware and reduce cooling system load. All impacted storage and compute scale units are in the same datacenter, within one of the region’s three Availability Zones (AZs).Multiple downstream services have been identified as impacted. 
Current Status – 12:05 UTC
We have made progress in restoring some of the affected cooling units and are continuing to work to restore the remaining units in parallel. The restoration of cooling units is helping with reducing temperatures towards normal operation thresholds in the impacted areas of the datacenter. Once operational threshold temperatures have stabilized, we will begin work on the structured restoration of Compute and Storage resources which were proactively shut down.
We will continue to provide updates as we have further progress towards service restoration. For workloads protected by Azure Site Recovery or Azure Backup, we recommend initiating a failover to the recovery region or to use Cross Region Restore. Newly deployed resources will by design bypass the impacted scale units.
We will provide our next update in 60 minutes or as events warrant.
This message was last updated at 12:46 UTC on 08 February 2023

Impact Statement: Starting around 20:19 UTC on 7 February 2023, a utility power surge in the Southeast Asia region tripped a subset of the cooling units offline in one of the Availability zones. While working to restore the cooling units, temperatures in the datacenter increased so we have proactively powered down a small subset of selected compute and storage scale units, to avoid damage to hardware and reduce cooling system load. All impacted storage and compute scale units are in the same datacenter, within one of the region’s three Availability Zones (AZs). Multiple downstream services have been identified as impacted.
Current Status: We do not have an exact ETA at this time, we currently expect an extended period of time to fully restore all cooling capacity. The Azure service recovery process will commence at this time and is expected to progressively return over a number of hours. Due to the nature of this issue our storage scale units are expected to require significant recovery efforts to ensure all resources return in a consistent state. Note that any new allocations for resources will automatically avoid the impacted scale units. If your workloads are protected by Azure Site Recovery or Azure Backup, we recommend to either initiate a failover to the recovery region or recover using Cross Region Restore.
Customers using services that are zonally-aware may consider failing out of the impacted zone, physical zone AZ-03. Note that physical zones are mapped to logical zones in your Azure subscription, Refer to: https://learn.microsoft.com/rest/api/resources/subscriptions/check-zone-peers.
This message was last updated at 12:21 UTC on 08 February 2023

Impact Statement: Starting around 20:19 UTC on 7 February 2023, a utility power surge in the Southeast Asia region tripped a subset of the cooling units offline in one of the Availability zones. While working to restore the cooling units, temperatures in the datacenter increased so we have proactively powered down a small subset of selected compute and storage scale units, to avoid damage to hardware and reduce cooling system load. All impacted storage and compute scale units are in the same datacenter, within one of the region’s three Availability Zones (AZs). Multiple downstream services have been identified as impacted.
Current Status: We do not have an exact ETA at this time, we currently expect an extended period of time to fully restore all cooling capacity. The Azure service recovery process will commence at this time and is expected to progressively return over a number of hours. Due to the nature of this issue our storage scale units are expected to require significant recovery efforts to ensure all resources return in a consistent state. Note that any new allocations for resources will automatically avoid the impacted scale units. If your workloads are protected by Azure Site Recovery or Azure Backup, we recommend to either initiate a failover to the recovery region or recover using Cross Region Restore.
Customers using services that are zonally-aware may consider failing out of the impacted zone, physical zone AZ-03. Note that physical zones are mapped to logical zones in your Azure subscription, Refer to: https://learn.microsoft.com/rest/api/resources/subscriptions/check-zone-peers.
This message was last updated at 12:06 UTC on 08 February 2023

Impact Statement: Starting around 20:19 UTC on 7 February 2023, a utility power surge in the Southeast Asia region tripped a subset of the cooling units offline in one of the Availability zones. While working to restore the cooling units, temperatures in the datacenter increased so we have proactively powered down a small subset of selected compute and storage scale units, to avoid damage to hardware and reduce cooling system load. All impacted storage and compute scale units are in the same datacenter, within one of the region’s three Availability Zones (AZs). Multiple downstream services have been identified as impacted.
Current Status: We do not have an exact ETA at this time, we currently expect an extended period of time to fully restore all cooling capacity. The Azure service recovery process will commence at this time and is expected to progressively return over a number of hours. Due to the nature of this issue our storage scale units are expected to require significant recovery efforts to ensure all resources return in a consistent state. Note that any new allocations for resources will automatically avoid the impacted scale units. If your workloads are protected by Azure Site Recovery or Azure Backup, we recommend to either initiate a failover to the recovery region or recover using Cross Region Restore.
Customers using services that are zonally-aware may consider failing out of the impacted zone, physical zone AZ-03. Note that physical zones are mapped to logical zones in your Azure subscription, Refer to: https://learn.microsoft.com/rest/api/resources/subscriptions/check-zone-peers.
This message was last updated at 07:40 UTC on 08 February 2023