Is Azure down?
Current Azure status is UP

We are investigating an issue impacting Azure Services in the West Europe region. We will provide more details as they become available.
This message was last updated at 08:24 UTC on 20 October 2023

Starting at approximately 07:33 UTC on 16 Sep 2023, a subset of customers in East US region are experiencing errors when trying to connect to their Azure SQL Databases. We are aware of this issue and actively working to recover the affected resources. More information will be provided within 60 minutes, when we expect to know more about the root cause and mitigation workstreams.
This message was last updated at 16:37 UTC on 16 September 2023

Impact Statement: Starting at approximately 08:30 UTC on 30 August 2023, a utility power surge in the Australia East region tripped a subset of the cooling units offline in one datacenter, within one of the Availability Zones. While working to restore cooling, temperatures in the datacenter increased so we proactively powered down a small subset of selected compute and storage scale units, to avoid damage to hardware. Multiple downstream services were impacted, with targeted communications being distributed via Azure Service Health.
Current Status: Having successfully recovered 99% of storage services and 99% of impacted Virtual Machines, we are beginning to see the recovery on the impacted nodes. At this stage, we believe most downstream services that are still experiencing impact are the result of dependencies on one of three services with recovery ongoing.
Power has been restored to all clusters hosting Cosmos DB. Accounts that were not failed over should see recovery in Australia East. Accounts failed over to alternate regions will continue to operate in these alternate regions; the Cosmos DB team has begun to bring Australia East region online.
Over 99% of impacted Azure storage accounts are now fully recovered. Due to thermal damage, we continue working on recovering a small number of resources to bring the remaining impacted storage accounts back online. We have recovered 75% of the remaining impacted resources, and as we continue making progress, additional services are displaying indications of improvement.
Azure SQL is continuing to recover impact to a single backend cluster, impacting a small subset of databases instances. Additionally, we are taking steps to reduce the overall zonal load to facilitate improved resource allocation and recovery.
Further updates on these remaining recovery efforts will be provided 2 hours, or as events warrant.
This message was last updated at 14:47 UTC on 31 August 2023

Impact Statement: Starting at approximately 08:30 UTC on 30 August 2023, a utility power surge in the Australia East region tripped a subset of the cooling units offline in one datacenter, within one of the Availability Zones. While working to restore cooling, temperatures in the datacenter increased so we proactively powered down a small subset of selected compute and storage scale units, to avoid damage to hardware. Multiple downstream services were impacted, with targeted communications being distributed via Azure Service Health.
Current Status: Having successfully recovered 99% of storage services and 99% of impacted Virtual Machines, we are beginning to see the recovery on the impacted nodes. At this stage, we believe most downstream services that are still experiencing impact are the result of dependencies on one of three services with recovery ongoing.
Power has been restored to all clusters hosting Cosmos DB. Accounts that were not failed over should see recovery in Australia East. Accounts failed over to alternate regions will continue to operate in these alternate regions; the Cosmos DB team has begun to bring Australia East region online.
Over 99% of impacted Azure storage accounts are now fully recovered. Due to thermal damage, we continue working on recovering a small number of resources to bring the remaining impacted storage accounts back online. We have recovered 75% of the remaining impacted resources, and as we continue making progress, additional services are displaying indications of improvement.
Azure SQL is continuing to recover impact to a single backend cluster, impacting a small subset of databases instances. Additionally, we are taking steps to reduce the overall zonal load to facilitate improved resource allocation and recovery.
Further updates on these remaining recovery efforts will be provided 2 hours, or as events warrant.
This message was last updated at 12:44 UTC on 31 August 2023

Impact Statement: Starting at approximately 08:30 UTC on 30 August 2023, a utility power surge in the Australia East region tripped a subset of the cooling units offline in one datacenter, within one of the Availability Zones. While working to restore cooling, temperatures in the datacenter increased so we proactively powered down a small subset of selected compute and storage scale units, to avoid damage to hardware. Multiple downstream services were impacted, with targeted communications being distributed via Azure Service Health.
Current Status: Having successfully recovered 99% of storage services and 99% of impacted Virtual Machines, we are actively investigating individual downstream services to confirm their recovery status and mitigate remaining issues. At this stage, we believe most downstream services that are still experiencing impact are the result of dependencies on one of three services with investigations ongoing.
Over 90% of Cosmos DB clusters in the Australia East region have been successfully recovered. Cosmos DB Accounts, that were not failed over to alternate read/write regions, should now begin to see signs of recovery. Once all clusters are fully restored, the Cosmos DB team will initiate the process of bringing this region back online for accounts that were previously failed over.
Over 99% of impacted Azure storage accounts are now fully recovered, a small number resources are currently being replaced or repaired due to thermal damage in order to bring the remaining impacted storage accounts back online.
Azure SQL is continuing to recover impact to a single backend cluster, impacting a small subset of databases instances. Additionally, we are taking steps to reduce the overall zonal load to facilitate improved resource allocation and recovery.
Further updates on these remaining recovery efforts will be provided in 60 minutes, or as events warrant.
This message was last updated at 04:11 UTC on 31 August 2023