Puzzle Technology
Back to all services
MA

Microsoft Azure

Microsoft · Cloud

OK
Status Page
https://status.azure.com/

View Microsoft Status History & Stats

Last 30 Days
2 incidents

Current state: Operational

Recent incidents

  1. Issues connecting to resources in West US

    Major · 23 Jul 2026, 17:29 · resolved 18 days ago

    • resolved

      Auto-resolved by the status page: the vendor stopped reporting this incident in their feed.

    • investigating

      Starting at approximately 14:44 UTC on 23 July 2026, customers may have experienced intermittent connectivity failures, increased latency, or difficulty accessing Azure and other Microsoft cloud (https://status.cloud.microsoft/) services associated with the West US region. Customers whose traffic traverses affected West US network infrastructure may also experience downstream impact. Impacted services include: Application Gateway, Application Insights, Azure AD B2C, Azure AI Speech, Azure API Management, Azure Bastion, Azure Bot Service, Azure Data Explorer, Azure Firewall, Azure Kubernetes Service (AKS), Azure Monitor, Azure Virtual Desktop, Azure VMware Solution, Log Analytics, Microsoft Graph, Microsoft Sentinel, Partner Center, Power BI Embedded, Virtual WAN Current Status: We identified a recent change that was strongly correlated with the onset of impact. We have completed the rollback of this change and telemetry across services are continuing to show signs of recovery. Customer should be observing recovery at this time. We are closely monitoring service health and downstream recovery and will provide additional updates as we validate restoration.

    • investigating

      Starting at approximately 14:44 UTC on 23 July 2026, customers may have experienced intermittent connectivity failures, increased latency, or difficulty accessing Azure and other Microsoft cloud (https://status.cloud.microsoft/) services associated with the West US region. Customers whose traffic traverses affected West US network infrastructure may also experience downstream impact. Impacted services include: Application Gateway, Application Insights, Azure AD B2C, Azure AI Search, Azure AI Speech, Azure API Management, Azure Bastion, Azure Bot Service, Azure Data Explorer, Azure Firewall, Azure Kubernetes Service (AKS), Azure Monitor, Azure Virtual Desktop, Azure VMware Solution, Log Analytics, Microsoft Graph, Microsoft Sentinel, Partner Center, Power BI Embedded, Virtual WAN Current Status: We identified a recent change that was strongly correlated with the onset of impact. We have completed the rollback of this change and telemetry across services are continuing to show signs of recovery. Customer should be observing recovery at this time. We are closely monitoring service health and downstream recovery and will provide additional updates as we validate restoration.

    • investigating

      Starting at approximately 14:44 UTC on 23 July 2026, customers may have experienced intermittent connectivity failures, increased latency, or difficulty accessing Azure and other Microsoft cloud (https://status.cloud.microsoft/) services associated with the West US region. Customers whose traffic traverses affected West US network infrastructure may also experience downstream impact. Impacted services include: Application Gateway, Application Insights, Azure AD B2C, Azure AI Search, Azure AI Speech, Azure API Management, Azure Bastion, Azure Bot Service, Azure Data Explorer, Azure Database for PostgreSQL, Azure Databricks, Azure Firewall, Azure Kubernetes Service (AKS), Azure Monitoring Essentials, Azure Virtual Desktop, Azure VMware Solution, Log Analytics, Microsoft Graph, Microsoft Sentinel, Partner Center, Power BI Embedded, Virtual WAN Current Status: We identified a recent change that was strongly correlated with the onset of impact. We have completed the rollback of this change and telemetry across services are continuing to show signs of recovery. Customer should be observing recovery at this time. We are closely monitoring service health and downstream recovery and will provide additional updates as we validate restoration.

    • investigating

      Starting at approximately 14:44 UTC on 23 July 2026, customers may have experienced intermittent connectivity failures, increased latency, or difficulty accessing Azure and other Microsoft cloud (https://status.cloud.microsoft/) services associated with the West US region. Customers whose traffic traverses affected West US network infrastructure may also experience downstream impact. Impacted services include: Application Gateway, Application Insights, Azure AD B2C, Azure AI Search, Azure AI Speech, Azure API Management, Azure Bastion, Azure Bot Service, Azure Data Explorer, Azure Database for PostgreSQL, Azure Databricks, Azure Firewall, Azure Kubernetes Service (AKS), Azure Monitoring Essentials, Azure Virtual Desktop, Azure VMware Solution, ExpressRoute Circuits, ExpressRoute Gateways, Log Analytics, Microsoft Sentinel, Partner Center, Power BI Embedded, Virtual WAN, VPN Gateway Current Status: We identified a recent change that was strongly correlated with the onset of impact. We have completed the rollback of this change and telemetry across services are continuing to show signs of recovery. We are closely monitoring service health and downstream recovery and will provide additional updates as we validate restoration

    • investigating

      Starting at approximately 14:44 UTC on 23 July 2026, customers may have experienced intermittent connectivity failures, increased latency, or difficulty accessing Azure and other Microsoft cloud (https://status.cloud.microsoft/) services associated with the West US region. Customers whose traffic traverses affected West US network infrastructure may also experience downstream impact. Impacted services include: Application Gateway, Application Insights, Azure AD B2C, Azure AI Search, Azure AI Speech, Azure API Management, Azure Bastion, Azure Bot Service, Azure Data Explorer, Azure Database for PostgreSQL, Azure Databricks, Azure Firewall, Azure Kubernetes Service (AKS), Azure Monitoring Essentials, Azure Virtual Desktop, Azure VMware Solution, ExpressRoute Circuits, ExpressRoute Gateways, Log Analytics, Microsoft Sentinel, Partner Center, Power BI Embedded, Virtual WAN, VPN Gateway Current Status: We identified a recent change that was strongly correlated with the onset of impact. We have completed the rollback of this change and telemetry across services are continuing to show signs of recovery. Customer should be observing recovery at this time. We are closely monitoring service health and downstream recovery and will provide additional updates as we validate restoration

    • investigating

      Starting at approximately 14:44 UTC on 23 July 2026, customers may have experienced intermittent connectivity failures, increased latency, or difficulty accessing Azure and other Microsoft cloud (https://status.cloud.microsoft/) services associated with the West US region. Customers whose traffic traverses affected West US network infrastructure may also experience downstream impact. Impacted services include: Application Gateway, Azure AD B2C, Azure AI Search, Azure AI Speech, Azure API Management, Azure Bastion, Azure Bot Service, Azure Data Explorer, Azure Database for PostgreSQL, Azure Databricks, Azure Firewall, Azure Kubernetes Service (AKS), Azure Virtual Desktop, Azure VMware Solution, ExpressRoute Circuits, ExpressRoute Gateways, Partner Center, Power BI Embedded, Virtual WAN, VPN Gateway Current Status: We identified a recent change that was strongly correlated with the onset of impact and have initiated rollback actions. The rollback is currently in progress and making steady progress toward completion. Telemetry across services is beginning to show signs of recovery. We are closely monitoring service health and traffic recovery as these actions are completed and will provide additional updates as we confirm measurable improvement.

    • investigating

      Starting at approximately 14:44 UTC on 23 July 2026, customers may have experienced intermittent connectivity failures, increased latency, or difficulty accessing Azure and other Microsoft cloud (https://status.cloud.microsoft/) services associated with the West US region. Customers whose traffic traverses affected West US network infrastructure may also experience downstream impact. Impacted services include: App Service, Application Gateway, Azure AD B2C, Azure AI Search, Azure API Management, Azure Bastion, Azure Bot Service, Azure Database for PostgreSQL - Flexible Server, Azure Databricks, Azure Firewall, Azure Kubernetes Service (AKS), Azure Virtual Desktop, Azure VMware Solution, ExpressRoute Circuits, ExpressRoute Gateways, Partner Center, Power BI Embedded, Virtual WAN, VPN Gateway Current Status: We may have identified the likely cause of the issue and are actively deploying mitigation actions. Based on our current progress, we expect to have additional information on the effectiveness of these actions within approximately 30 minutes. We are closely monitoring service recovery as this action is rolling out.

    • investigating

      Starting at approximately 14:44 UTC on 23 July 2026, customers may have experienced intermittent connectivity failures, increased latency, or difficulty accessing Azure and other Microsoft cloud (https://status.cloud.microsoft/) services associated with the West US region. Customers whose traffic traverses affected West US network infrastructure may also experience downstream impact. Impacted services include: App Service, Application Gateway, Azure AD B2C, Azure AI Search, Azure API Management, Azure Bastion, Azure Bot Service, Azure Database for PostgreSQL - Flexible Server, Azure Databricks, Azure Firewall, Azure Kubernetes Service (AKS), Azure Virtual Desktop, Azure VMware Solution, ExpressRoute Circuits, ExpressRoute Gateways, Partner Center, Power BI Embedded, Virtual WAN, VPN Gateway Current Status: We may have identified the likely cause of the issue and are actively deploying mitigation actions. Based on our current progress, we expect to have additional information on the effectiveness of these actions within approximately 30 minutes. We are closely monitoring service recovery as this action is rolling out.

    • investigating

      Starting at approximately 14:44 UTC on 23 July 2026, customers may have experienced intermittent connectivity failures, increased latency, or difficulty accessing Azure and other Microsoft cloud (https://status.cloud.microsoft/) services associated with the West US region. Customers whose traffic traverses affected West US network infrastructure may also experience downstream impact. Impacted services include: API Management, Application Gateway, Azure AD B2C, Azure AI Search, Azure Bastion, Azure Bot Service, Azure Database for PostgreSQL, Azure Databricks, Azure Firewall, Azure Kubernetes Service (AKS), Azure VMware Solutions, ExpressRoute Circuits, ExpressRoute Gateways, Network Infrastructure, Power BI Embedded, Virtual WAN, VPN Gateway We are actively investigating networking and traffic-routing anomalies associated with the onset of impact. We have successfully redirected portions of traffic away from potentially affected network paths and tested mitigation actions. At this time, those actions have not produced a broad improvement in impacted service telemetry. Engineering teams continue investigating routing and network-path anomalies that align with the start of the incident and are evaluating additional mitigation options. While we do not have an estimated time for mitigation at this stage, we will provide updates as they become available. Customers may wish to review their business continuity and disaster recovery plans and take actions appropriate for their environment.

    • investigating

      Starting at approximately 14:44 UTC on 23 July 2026, customers may have experienced intermittent connectivity failures, increased latency, or difficulty accessing Azure and other Microsoft cloud services (https://status.cloud.microsoft/) services associated with the West US region. Customers whose traffic traverses affected West US network infrastructure may also experience downstream impact. Impacted services include: API Management, Application Gateway, Azure AD B2C, Azure AI Search, Azure Bastion, Azure Bot Service, Azure Database for PostgreSQL, Azure Databricks, Azure Firewall, Azure Kubernetes Service (AKS), Azure VMware Solutions, ExpressRoute Circuits, ExpressRoute Gateways, Network Infrastructure, Power BI Embedded, Virtual WAN, VPN Gateway We are actively investigating networking and traffic-routing anomalies associated with the onset of impact. We have successfully redirected portions of traffic away from potentially affected network paths and tested mitigation actions. At this time, those actions have not produced a broad improvement in impacted service telemetry. Engineering teams continue investigating routing and network-path anomalies that align with the start of the incident and are evaluating additional mitigation options. While we do not have an estimated time for mitigation at this stage, we will provide updates as they become available. Customers may wish to review their business continuity and disaster recovery plans and take actions appropriate for their environment.

    • investigating

      Starting at approximately 14:44 UTC on 23 July 2026, customers may have experienced intermittent connectivity failures, increased latency, or difficulty accessing Azure services associated with the West US region. Customers whose traffic traverses affected West US network infrastructure may also experience downstream impact. Impacted services include: API Management, Application Gateway, Azure AD B2C, Azure AI Search, Azure Bastion, Azure Bot Service, Azure Database for PostgreSQL, Azure Databricks, Azure Firewall, Azure Kubernetes Service (AKS), Azure VMware Solutions, ExpressRoute Circuits, ExpressRoute Gateways, Network Infrastructure, Power BI Embedded, Virtual WAN, VPN Gateway We are actively investigating networking and traffic-routing anomalies associated with the onset of impact. We have successfully redirected portions of traffic away from potentially affected network paths and tested mitigation actions. At this time, those actions have not produced a broad improvement in impacted service telemetry. Engineering teams continue investigating routing and network-path anomalies that align with the start of the incident and are evaluating additional mitigation options. While we do not have an estimated time for mitigation at this stage, we will provide updates as they become available. Customers may wish to review their business continuity and disaster recovery plans and take actions appropriate for their environment. If you are unable to access the Azure portal or create a support request during this event, contact Microsoft Customer Service using the phone number for your country or region listed here: https://support.microsoft.com/en-us/contactus

    • investigating

      Starting at approximately 14:44 UTC on 23 July 2026, customers may have experienced intermittent connectivity failures, increased latency, or difficulty accessing Azure services associated with the West US region. Customers whose traffic traverses affected West US network infrastructure may also experience downstream impact. Impacted services include: API Management, Application Gateway, Azure AD B2C, Azure AI Search, Azure Bastion, Azure Bot Service, Azure Database for PostgreSQL, Azure Databricks, Azure Firewall, Azure Kubernetes Service (AKS), Azure VMware Solutions, ExpressRoute Circuits, ExpressRoute Gateways, Network Infrastructure, Power BI Embedded, Virtual WAN, VPN Gateway We are actively investigating networking and traffic-routing anomalies associated with the onset of impact. We have successfully redirected portions of traffic away from potentially affected network paths and tested mitigation actions. At this time, those actions have not produced a broad improvement in impacted service telemetry. Engineering teams continue investigating routing and network-path anomalies that align with the start of the incident and are evaluating additional mitigation options. While we do not have an estimated time for mitigation at this stage, we will provide updates as they become available. Customers may wish to review their business continuity and disaster recovery plans and take actions appropriate for their environment. If you are unable to access the Azure portal or create a support request during this event, contact Microsoft Customer Service using the phone number for your country or region listed here: https://support.microsoft.com/en-us/contactus

    • investigating

      Starting at 14:44 UTC on 23 July, 2026, customers may have experienced intermittent connectivity failures, increased latency, or difficulty accessing Azure services in West US region. Customers with traffic traversing the West US region may also experience downstream impact. Impacted services include, but are not limited to: API Management, Application Gateway, Azure Database for PostgreSQL, Azure Kubernetes Service (AKS), ExpressRoute Circuits, ExpressRoute Gateways, Network Infrastructure, Power BI Embedded, Virtual WAN, VPN Gateway We have identified a potential trigger and are isolating certain impacted devices and redirecting portions of traffic to healthier devices as part of a mitigation plan. We are actively monitoring traffic patterns and service recovery. We will continue to evaluate the effectiveness of mitigation, assess customer impact, and investigate contributing factors. We will provide additional information as soon as it becomes available.

    • investigating

      Starting at 14:44 UTC on 23 July, 2026, customers may have experienced intermittent connectivity failures, increased latency, or difficulty accessing Azure services in West US region. Customers with traffic traversing the West US region may also experience downstream impact. Impacted services include, but are not limited to: API Management, Application Gateway, Azure Database for PostgreSQL, Azure Kubernetes Service (AKS), ExpressRoute Circuits, ExpressRoute Gateways, Network Infrastructure, Power BI Embedded, Virtual WAN, VPN Gateway We have identified a potential trigger and are isolating certain impacted devices and redirecting portions of traffic to healthier devices as part of a mitigation plan. We are actively monitoring traffic patterns and service recovery. We will continue to evaluate the effectiveness of mitigation, assess customer impact, and investigate contributing factors. We will provide additional information as soon as it becomes available.

    • investigating

      Starting at 14:44 UTC on 23 July, 2026, we began investigating a networking issue affecting connectivity to Azure services in the West US region. Impacted customers may be experiencing intermittent connectivity failures, increased latency, or difficulty accessing Azure services. Customers with traffic traversing the West US region may also experience downstream impact. Our investigation is currently focused on network infrastructure within the affected region. We have implemented mitigation actions on affected network components by removing the problematic devices from rotation, redirecting portions of traffic, and are actively monitoring traffic patterns and service recovery. Initial findings indicate the issue may be related to network path disruption within the affected infrastructure; however, analysis remains ongoing. We continue to evaluate the effectiveness of mitigations, assess customer impact, and investigate contributing factors. We will provide additional information as it becomes available.

    • investigating

      We are investigating a networking issue affecting connectivity to Azure services in the West US region. Impacted customers may experience intermittent connectivity failures, increased latency, or difficulty accessing Azure services. Customers with traffic traversing the West US region may also experience downstream impact. We are exploring mitigation options on affected network devices. Early indications suggest the issue is related to network traffic flow through the impacted infrastructure; however our analysis remains ongoing. We are closely monitoring traffic while continuing our investigation. We will provide additional information as it becomes available.

  2. Active – Connectivity Issues Affecting Azure Services in West US

    Major · 23 Jul 2026, 16:50 · resolved 18 days ago

    • resolved

      Auto-resolved by the status page: the vendor stopped reporting this incident in their feed.

    • investigating

      We are investigating an issue affecting connectivity to Azure services for a subset of customers in the West US region. Impacted customers may experience intermittent issues when accessing Azure services.We will provide more information as it becomes available.

  3. GitHub Issue

    Major · 8 Jul 2026, 20:41 · resolved about 1 month ago

    • resolved

      Auto-resolved by the status page: the vendor stopped reporting this incident in their feed.

    • investigating

      GitHub Enterprise Cloud with Data Residency is experiencing a service outage impacting all services, issue identified and mitigation in progress. For details please go here: : https://us.githubstatus.com/posts/details/PBJ0QTY

    • investigating

      GitHub Enterprise Cloud is experiencing a service outage impacting all services, issue identified and mitigation in progress. For details please go here: GitHub Enterprise Cloud - US: https://us.githubstatus.com/posts/details/PBJ0QTY

    • investigating

      GitHub Enterprise Cloud is experiencing a service outage impacting all services, issue identified and mitigation in progress. For details please go here: GitHub Enterprise Cloud - US

    • resolved

      Auto-resolved by the status page: the vendor stopped reporting this incident in their feed.

    • investigating

      What happened?Between 21:45 UTC and 23:23 UTC on 15 June 2026, Azure customers leveraging services which depend upon Microsoft Artifact Registry (MAR) may have experienced 401 authentication errors when attempting to pull images from MAR . This incident is now mitigated. Further details will be provided directly to impacted customers through the Azure Portal.

    • resolved

      Auto-resolved by the status page: the vendor stopped reporting this incident in their feed.

    • investigating

      Impact Statement: Starting at 21:45 UTC on 15 June 2026, a subset of Azure customers leveraging services which depend upon MCR (Microsoft Container Registry) for storing images may experience 401 authentication errors for requests attempting to pull Microsoft images from mcr.microsoft.com.Current Status: We detected this issue via internal service monitoring upon identifying a spike of 401 errors. We’ve identified a potential underlying factor to be a recent update which introduced a code regression, and we've completed roll out of a hotfix to address the code regression and mitigate impact for affected customers. We are closely monitoring internal telemetry to validate full mitigation and prevent further occurrences. The next update will be provided within 60 minutes, or as events warrant.

  4. Investigating a spike in 401 authentication errors

    Major · 16 Jun 2026, 00:04 · resolved about 2 months ago

    • resolved

      Auto-resolved by the status page: the vendor stopped reporting this incident in their feed.

    • investigating

      We are actively investigating customer alerts of 401 authentication errors when pulling images from mcr.microsoft.com. We’ve identified a potential underlying factor related to a recent update made to a backed service and we are actively working on determining mitigation workstreams. More information will be provided shortly.

  5. Active - Azure OpenAI Service Elevated Error Rates in multiple regions

    Major · 29 May 2026, 10:39 · resolved 2 months ago

    • resolved

      Auto-resolved by the status page: the vendor stopped reporting this incident in their feed.

    • investigating

      Impact Statement: Starting at 09:39 UTC on 29 May 2026, customers using Azure OpenAI service in multiple regions who may experience degraded request success where some requests returned errors or failed to complete. Current Status: We identified this issue through internal automated service monitoring after detecting a drop in call success rates. Our investigation indicates that the issue is linked to elevated server-side errors within a backend service layer in the affected region. We are actively investigating and working to determine the full scope and mitigation steps. The next update will be provided within 60 minutes, or sooner if there are significant developments.

    • investigating

      Impact Statement: Starting at 09:39 UTC on 29 May 2026, you have been identified as a subset of customers using Azure OpenAI service in multiple regions who may experience degraded request success where some requests returned errors or failed to complete. Current Status: We identified this issue through internal automated service monitoring after detecting a drop in call success rates. Our investigation indicates that the issue is linked to elevated server-side errors within a backend service layer in the affected region. We are actively investigating and working to determine the full scope and mitigation steps. The next update will be provided within 60 minutes, or sooner if there are significant developments.

  6. Active – Network connectivity degradation in West US 2

    Major · 29 May 2026, 07:57 · resolved 2 months ago

    • resolved

      Auto-resolved by the status page: the vendor stopped reporting this incident in their feed.

    • investigating

      Impact Statement- Starting at 04:27 UTC on 29 May 2026, customers may experience increased latency, intermittent connectivity, or timeouts when accessing resources hosted in the West US 2 region, due to a power event. We are in process of recovering power and working to restore infrastructure in the region. We started seeing partial recovery and will be sending targeted communications to impacted customers through the Azure Service Health dashboard. The next update will be provided within 60 minutes.

    • investigating

      Impact Statement- Starting at 04:27 UTC on 29 May 2026, customers may experience increased latency, intermittent connectivity, or timeouts when accessing resources hosted in the West US 2 region. Engineers are actively investigating the issue and working to restore network stability. Some requests may succeed upon retry as connectivity intermittently recovers. We are sending targeted communications to impacted customers through the Azure Service Health dashboard. The next update will be provided within 60 minutes.

  7. Active – Multi Service degradation in West US 2

    Major · 29 May 2026, 05:27 · resolved 2 months ago

    • resolved

      Auto-resolved by the status page: the vendor stopped reporting this incident in their feed.

    • investigating

      Impact Statement: Starting at 04:27 UTC on 29 May 2026, a severe thunderstorm caused widespread utility power loss to our West US 2 datacenter facilities, resulting in a multi-service outage. Datacenter power and network infrastructure have been fully restored. The majority of services have recovered, with residual impact limited to storage-dependent workloads on two remaining storage stamps undergoing tail recovery. Customers with dependencies on two outstanding storage stamps may still experience intermittent connectivity or elevated latency. All other services are operating normally or nearing full restoration. Currently affected Azure services include, but are not limited to (recovery validation underway): Azure Functions, Azure Database for MySQL Flexible Servers, Azure Database for PostgreSQL Flexible Server, Azure SQL, Azure Managed Grafana, Virtual Machines, Virtual Machine Scale Sets, Azure Kubernetes Service, Storage, Application Insights, Azure Monitor, and Azure Log Analytics Current Status: A severe weather event, including multiple lightning strikes, affected several datacenter facilities in the West US 2 region, resulting in concurrent utility power interruptions across multiple availability zones. Backup generators activated as designed; however, during the transition to sustained generator operation, a subset of generator systems were unable to fully synchronize under the sudden facility load, while others subsequently shut down due to thermal protection mechanisms as cooling systems were impacted by the broader power disruption. These events occurred across multiple facilities within the same timeframe, thus resulting in multiple zones being impacted concurrently. Datacenter utility power has been fully restored, and network infrastructure is fully operational. HVAC systems have returned to normal operation, and ambient temperatures are within expected ranges. The majority of storage infrastructure has recovered successfully, with two storage stamps currently completing final recovery and integrity validation activities. On-site teams continue to perform validation and bring the remaining resources online. Services dependent on these storage stamps are expected to recover as these final activities are completed. The following services have been confirmed restored and are operating normally: Service Bus, App Service (Web Apps), Azure Site Recovery, Backup (MAB), Azure Cosmos DB, Azure Resource Manager, Data Explorer, Azure IoT Hub, Microsoft Defender for Cloud Apps, Azure Container Registry, Azure Policy, Azure NetApp Files, Azure Resource Graph, Azure Data Factory, Azure Databricks, Redis, and Azure Synapse Estimated Time to Resolution: With datacenter power back online, our network infrastructure fully restored and with majority of storage back online, remaining recovery is limited to two storage stamps completing the final stages of recovery and data integrity checks. We estimate full service restoration within approximately 3–4 hours. Individual services dependent on these stamps will come back online progressively as validation completes. Customer Guidance: If you have resources in paired or alternate regions, consider failing over traffic away from West US 2 until we confirm full recovery. Single-region workloads will recover automatically as infrastructure is restored — no customer action is required. We recommend pausing new deployments to West US 2 until this incident is resolved; use alternate regions if urgent. Monitor Azure Status (https://azure.status.microsoft/en-us/status) and Service Health in the portal for real-time updates specific to your subscriptions. Next update: We will provide our next status update within the next 60 minutes, or sooner if events warrant.

    • investigating

      Impact Statement: Starting at 04:27 UTC on 29 May 2026, a severe thunderstorm caused widespread utility power loss to our West US 2 datacenter facilities, resulting in a multi-service outage. Datacenter power and network infrastructure have been fully restored. The majority of services have recovered, with residual impact limited to storage-dependent workloads on two remaining storage stamps undergoing tail recovery. Customers with dependencies on two outstanding storage stamps may still experience intermittent connectivity or elevated latency. All other services are operating normally or nearing full restoration. Currently affected Azure services include, but are not limited to (recovery validation underway): Azure Functions, Azure Database for MySQL Flexible Servers, Azure Database for PostgreSQL Flexible Server, Azure Databricks, Redis, Azure SQL, Azure Managed Grafana, Virtual Machines, Virtual Machine Scale Sets, Azure Kubernetes Service, Storage, Application Insights, Azure Monitor, and Azure Log Analytics Current Status: A severe weather event, including multiple lightning strikes, affected several datacenter facilities in the West US 2 region, resulting in concurrent utility power interruptions across multiple availability zones. Backup generators activated as designed; however, during the transition to sustained generator operation, a subset of generator systems were unable to fully synchronize under the sudden facility load, while others subsequently shut down due to thermal protection mechanisms as cooling systems were impacted by the broader power disruption. These events occurred across multiple facilities within the same timeframe, thus resulting in multiple zones being impacted concurrently. Datacenter utility power has been fully restored, and network infrastructure is fully operational. HVAC systems have returned to normal operation, and ambient temperatures are within expected ranges. The majority of storage infrastructure has recovered successfully, with two storage stamps currently completing final recovery and integrity validation activities. On-site teams continue to perform validation and bring the remaining resources online. Services dependent on these storage stamps are expected to recover as these final activities are completed. The following services have been confirmed restored and are operating normally: Service Bus, App Service (Web Apps), Azure Site Recovery, Backup (MAB), Azure Cosmos DB, Azure Resource Manager, Data Explorer, Azure IoT Hub, Microsoft Defender for Cloud Apps, Azure Container Registry, Azure Policy, Azure NetApp Files, Azure Resource Graph, Azure Data Factory, and Azure Synapse Estimated Time to Resolution: With datacenter power back online, our network infrastructure fully restored and with majority of storage back online, remaining recovery is limited to two storage stamps completing the final stages of recovery and data integrity checks. We estimate full service restoration within approximately 3–4 hours. Individual services dependent on these stamps will come back online progressively as validation completes. Customer Guidance: If you have resources in paired or alternate regions, consider failing over traffic away from West US 2 until we confirm full recovery. Single-region workloads will recover automatically as infrastructure is restored — no customer action is required. We recommend pausing new deployments to West US 2 until this incident is resolved; use alternate regions if urgent. Monitor Azure Status (https://azure.status.microsoft/en-us/status) and Service Health in the portal for real-time updates specific to your subscriptions. Next update: We will provide our next status update within the next 60 minutes, or sooner if events warrant.

    • investigating

      Impact Statement: Starting at 04:27 UTC on 29 May 2026, a severe thunderstorm caused widespread utility power loss to our West US 2 datacenter facilities, resulting in a multi-service outage. Impact is currently region-wide, and we have not yet confirmed isolation to specific scale units or availability zones and are treating this as full-region impact until physical inspections confirm otherwise. Customers are experiencing service connectivity failures, timeouts, and elevated error rates across affected services. This includes an inability to deploy new resources or scale existing workloads, intermittent availability where some requests may succeed while others fail depending on which infrastructure nodes have recovered, and both data plane and control plane impact for services not yet restored. Affected Azure services include, but are not limited to: Azure Functions, Azure Database for MySQL Flexible Servers, Azure Database for PostgreSQL Flexible Server, Azure Databricks, Redis, Azure SQL, Azure Managed Grafana, Virtual Machines, Virtual Machine Scale Sets, Azure Kubernetes Service, Storage, Application Insights, Azure Data Factory, Azure Monitor, and Azure Log Analytics Current Status: Severe thunderstorms resulted to a complete utility power loss to multiple datacenter buildings simultaneously. Our backup generators activated but were unable to fully compensate. The generator transfer switchover was only partially successful, with some generator sets failing to synchronize under the sudden full facility load and others experiencing thermal protection shutdowns as ambient temperatures rose due to simultaneous cooling system failures. This cascading combination of power instability and cooling loss exceeded our designed N+1 redundancy for this failure mode. We are still determining the full extent of mechanical vs. electrical failures in the generator systems. HVAC systems are being restarted in sequence; ambient temperatures are returning to safe ranges but have not fully normalized, so we are staged-powering equipment to avoid thermal re-trips. Network devices and storage arrays are being power-cycled and validated in sequence, with storage dependencies as the primary remaining bottleneck due to required manual intervention and data integrity verification. Where possible, traffic is being redirected to healthy nodes, and on-site teams are conducting physical hardware inspections to identify components requiring replacement. The following services have been confirmed restored and are operating normally: Service Bus, App Service (Web Apps), Azure Site Recovery, Backup (MAB), Azure Cosmos DB, Azure Resource Manager, Data Explorer, Azure IoT Hub, Microsoft Defender for Cloud Apps, Azure Container Registry, Azure Policy, Azure NetApp Files, Azure Resource Graph, Azure Synapse Customer Guidance: • If you have resources in paired or alternate regions, consider failing over traffic away from West US 2 until we confirm full recovery. • Single-region workloads will recover automatically as infrastructure is restored — no customer action is required. • We recommend pausing new deployments to West US 2 until this incident is resolved; use alternate regions if urgent. • Monitor Azure Status (https://azure.status.microsoft/en-us/status) and Service Health in the portal for real-time updates specific to your subscriptions. Next update: We will provide our next status update within the next 60 minutes, or sooner, if events warrant.

    • investigating

      Impact Statement: Starting at 04:27 UTC on 29 May 2026, a severe thunderstorm caused widespread utility power loss to our West US 2 datacenter facilities, resulting in a multi-service outage. Impact is currently region-wide, and we have not yet confirmed isolation to specific scale units or availability zones and are treating this as full-region impact until physical inspections confirm otherwise. Customers are experiencing service connectivity failures, timeouts, and elevated error rates across affected services. This includes an inability to deploy new resources or scale existing workloads, intermittent availability where some requests may succeed while others fail depending on which infrastructure nodes have recovered, and both data plane and control plane impact for services not yet restored. Affected Azure services include, but are not limited to: Azure Functions, Azure Database for MySQL Flexible Servers, Azure Database for PostgreSQL Flexible Server, Azure Databricks, Redis, Azure SQL, Azure Managed Grafana, Virtual Machines, Virtual Machine Scale Sets, Azure Kubernetes Service, Storage, Application Insights, Azure Data Factory, Azure Monitor, and Azure Log Analytics Current Status: Severe thunderstorms resulted to a complete utility power loss to multiple datacenter buildings simultaneously. Our backup generators activated but were unable to fully compensate. The generator transfer switchover was only partially successful, with some generator sets failing to synchronize under the sudden full facility load and others experiencing thermal protection shutdowns as ambient temperatures rose due to simultaneous cooling system failures. This cascading combination of power instability and cooling loss exceeded our designed N+1 redundancy for this failure mode. We are still determining the full extent of mechanical vs. electrical failures in the generator systems. HVAC systems are being restarted in sequence; ambient temperatures are returning to safe ranges but have not fully normalized, so we are staged-powering equipment to avoid thermal re-trips. Network devices and storage arrays are being power-cycled and validated in sequence, with storage dependencies as the primary remaining bottleneck due to required manual intervention and data integrity verification. Where possible, traffic is being redirected to healthy nodes, and on-site teams are conducting physical hardware inspections to identify components requiring replacement. The following services have been confirmed restored and are operating normally: Service Bus, App Service (Web Apps), Azure Site Recovery, Backup (MAB), Azure Cosmos DB, Azure Resource Manager, Data Explorer, Azure IoT Hub, Microsoft Defender for Cloud Apps, Azure Container Registry, Azure Policy, Azure NetApp Files, Azure Resource Graph, Azure Synapse Customer Guidance: • If you have resources in paired or alternate regions, consider failing over traffic away from West US 2 until we confirm full recovery. • Single-region workloads will recover automatically as infrastructure is restored — no customer action is required. • We recommend pausing new deployments to West US 2 until this incident is resolved; use alternate regions if urgent. • Monitor Azure Status (status.azure.com) and Service Health in the portal for real-time updates specific to your subscriptions. Next update: We will provide our next status update within 1 hour, or sooner, if events warrant.

  8. Active – Multi Service degradation in West US 2 region.

    Major · 29 May 2026, 05:27 · resolved 2 months ago

    • resolved

      Auto-resolved by the status page: the vendor stopped reporting this incident in their feed.

    • investigating

      Impact Statement: Starting at 04:27 UTC on 29 May 2026, we are investigating an incident which is impacting multiple services in West US 2, due to a power event. This impacts service accessibility region-wide, with customers potentially experiencing increased latency and intermittent connectivity, including timeouts when connecting to resources. Affected Azure services include, but are not limited to: Azure Functions, Azure Database for MySQL flexible servers, Azure Database PostgreSQL Flexible Server, Azure Databricks and, Redis, Azure SQL, Azure Managed Grafana, Virtual Machine, Virtual Machine Scale Set, Azure Kubernetes Service, Storage, Application Insights, Azure Monitor, Azure Data Factory and Azure Log Analytics Current Status: We are actively mitigating service impact in the West US 2 region following severe thunderstorms that caused widespread power outages. Backup generators were unable to fully stabilize power, leading to temperature spikes and instability across datacenter hardware and network devices. Recovery efforts are well underway, including power cycling and targeted reboots of network and storage devices, physical inspections, node remediation, and traffic redirection to healthy infrastructure. Our telemetry indicates significant improvements. Customers might start noticing improvements as these measures advance, though full mitigation is delayed by persistent hardware and network instability, storage dependencies, and cooling normalization. Recovered Azure services: Service Bus, Storage, App Service (Web Apps), Azure Site Recovery, Backup (MAB), Azure Cosmos DB, Application Insights, Azure Resource Manager, Data Explorer, Azure IoT Hub, Microsoft Defender for Cloud Apps, Azure Container Registry, Azure Policy, Azure NetApp Files, Azure Resource Graph, Azure Synapse, and Azure Database for MySQL - Flexible Server Our teams actively working to address the issue, with manual intervention and inspections ongoing to stabilize remaining scale units. The next update will be provided within 2 hours, or as events warrant.

    • investigating

      Impact Statement: Starting at 04:27 UTC on 29 May 2026, we are investigating an incident which is impacting multiple services in West US 2, due to a power event. This impacts service accessibility region-wide, with customers potentially experiencing increased latency and intermittent connectivity, including timeouts when connecting to resources. Affected Azure services include, but are not limited to: Azure Functions, Azure Database for MySQL flexible servers, Azure Database PostgreSQL Flexible Server, Azure Databricks and, Redis, Azure SQL, Azure Managed Grafana, Virtual Machine, Virtual Machine Scale Set, Azure Kubernetes Service, Storage, Application Insights Current Status: We are actively mitigating service impact in the West US 2 region following severe thunderstorms that caused widespread power outages. Backup generators were unable to fully stabilize power, leading to temperature spikes and instability across datacenter hardware and network devices. Recovery efforts are well underway, including power cycling and targeted reboots of network and storage devices, physical inspections, node remediation, and traffic redirection to healthy infrastructure. Our telemetry indicates significant improvements. Customers might start noticing improvements as these measures advance, though full mitigation is delayed by persistent hardware and network instability, storage dependencies, and cooling normalization. Recovered Azure services: Service Bus, Storage, App Service (Web Apps), Azure Site Recovery, Backup (MAB), Azure Cosmos DB, Azure Log Analytics, Application Insights, Azure Monitor, Azure Resource Manager, Data Explorer, Azure IoT Hub, Microsoft Defender for Cloud Apps, Azure Container Registry, Azure Policy, Azure NetApp Files, Azure Resource Graph, Azure Synapse, Azure Database for MySQL - Flexible Server Our teams actively working to address the issue, with manual intervention and inspections ongoing to stabilize remaining scale units and restore full service which is expected to be completed within the next hour.

    • investigating

      Impact Statement: Starting at 04:27 UTC on 29 May 2026, we are investigating an incident which is impacting multiple services in West US 2, due to a power event. This impacts service accessibility region-wide, with customers potentially experiencing increased latency and intermittent connectivity, including timeouts when connecting to resources. Affected Azure services include, but are not limited to: Azure Functions, Azure Database for MySQL flexible servers, Azure Database PostgreSQL Flexible Server, Azure Databricks and, Redis, Azure SQL, Azure Managed Grafana, Virtual Machine, Virtual Machine Scale Set, Azure Kubernetes Service. Current Status: We are actively mitigating service impact in the West US 2 region following severe thunderstorms that caused widespread power outages. Backup generators were unable to fully stabilize power, leading to temperature spikes and instability across datacenter hardware and network devices. Recovery efforts are well underway, including power cycling and targeted reboots of network and storage devices, physical inspections, node remediation, and traffic redirection to healthy infrastructure. Our telemetry indicates significant improvements. Customers might start noticing improvements as these measures advance, though full mitigation is delayed by persistent hardware and network instability, storage dependencies, and cooling normalization. Recovered Azure services: Service Bus, Storage, App Service (Web Apps), Azure Site Recovery, Backup (MAB), Azure Cosmos DB, Azure Log Analytics, Application Insights, Azure Monitor, Azure Resource Manager, Data Explorer, Azure IoT Hub, Microsoft Defender for Cloud Apps, Azure Container Registry, Azure Policy, Azure NetApp Files, Azure Resource Graph, Azure Synapse, Azure Database for MySQL - Flexible Server Our teams actively working to address the issue, with manual intervention and inspections ongoing to stabilize remaining scale units and restore full service which is expected to be completed within the next hour.

    • investigating

      Impact Statement: Starting at 04:27 UTC on 29 May 2026, we are investigating an incident which is impacting multiple services in West US 2, due to a power event. This impacts service accessibility region-wide, with customers potentially experiencing increased latency and intermittent connectivity, including timeouts when connecting to resources. Affected Azure services include, but are not limited to: Azure Functions, Azure Database for MySQL flexible servers, Azure Database PostgreSQL Flexible Server, Azure Databricks and, Redis, Azure SQL, Azure Managed Grafana, Virtual Machine, Virtual Machine Scale Set Current Status: We are actively mitigating service impact in the West US 2 region following severe thunderstorms that caused widespread power outages. Backup generators were unable to fully stabilize power, leading to temperature spikes and instability across datacenter hardware and network devices. Recovery efforts are well underway, including power cycling and targeted reboots of network and storage devices, physical inspections, node remediation, and traffic redirection to healthy infrastructure. Our telemetry indicates significant improvements. Customers might start noticing improvements as these measures advance, though full mitigation is delayed by persistent hardware and network instability, storage dependencies, and cooling normalization. Recovered Azure services: Service Bus, Storage, App Service (Web Apps), Azure Site Recovery, Backup (MAB), Azure Cosmos DB, Azure Log Analytics, Application Insights, Azure Monitor, Azure Resource Manager, Data Explorer, Azure IoT Hub, Microsoft Defender for Cloud Apps, Azure Container Registry, Azure Kubernetes Service, Azure Policy, Azure NetApp Files, Azure Resource Graph, Azure Synapse, Azure Database for MySQL - Flexible Server Our teams actively working to address the issue, with manual intervention and inspections ongoing to stabilize remaining scale units and restore full service which is expected to be completed within the next hour.

    • investigating

      Impact Statement: Starting at 04:27 UTC on 29 May 2026, we are investigating an incident which is impacting multiple services in West US 2, due to a power event. This impacts service accessibility region-wide, with customers potentially experiencing increased latency and intermittent connectivity, including timeouts when connecting to resources. Affected Azure services include, but are not limited to: (yet to recover) Azure Functions, Azure Database for MySQL flexible servers, Azure Database PostgreSQL Flexible Server, Azure Databricks and, Redis, Azure SQL, Azure Managed Grafana Current Status: We identified this issue through our automated monitoring after detecting elevated alerts related to network and infrastructure health in the West US 2 region. The issue was triggered by a power event in the datacenter, which impacted underlying infrastructure and led to increased latency and intermittent connectivity for select resources. We are aware of the impact and are actively investigating. Our telemetry indicates significant improvements; customers might start noticing improvements as these measures advance. Recovered Azure services: Service Bus, Storage, App Service (Web Apps), Azure Site Recovery, Virtual Machine, Virtual Machine scale set, Backup (MAB), Azure Cosmos DB, Azure Log Analytics, Application Insights, Azure Monitor, Azure Resource Manager, Data Explorer, Azure IoT Hub, Microsoft Defender for Cloud Apps, Azure Container Registry, Azure Kubernetes Service, Azure Policy, Azure NetApp Files, Azure Resource Graph, Azure Synapse, Azure Database for MySQL - Flexible Server Mitigation efforts are still underway to restore affected network components across dependent services, including Storage and Compute. The next update will be provided within 2 hours, or sooner if there are significant developments.

    • investigating

      Impact Statement: Starting at 04:27 UTC on 29 May 2026, we are investigating an incident which is impacting multiple services in West US 2, due to a power event. This impacts service accessibility region-wide, with customers potentially experiencing increased latency and intermittent connectivity, including timeouts when connecting to resources. Affected Azure services include, but are not limited to: App Service, Azure Functions, Azure Virtual Machines, Azure Virtual Machine Scale Sets, Azure Backup, Azure Container Registry, Azure Cosmos DB, Azure Database for MySQL flexible servers, Azure Database PostgreSQL Flexible Server, Azure IoT Hub, Azure Kubernetes Service (AKS), Azure Monitor, Application Insights, Log Analytics, Azure NetApp Files, Azure Site Recovery, Azure Synapse Analytics, Microsoft Defender for Cloud, Azure Databricks and Azure Storage, Redis, Azure SQL, Azure Managed Grafana Current Status: We identified this issue through our automated monitoring after detecting elevated alerts related to network and infrastructure health in the West US 2 region. The issue was triggered by a power event in the datacenter, which impacted underlying infrastructure and led to increased latency and intermittent connectivity for select resources. We are aware of the impact and are actively investigating. Mitigation efforts are underway to restore affected network components across dependent services, including Storage and Compute. Telemetry indicates that certain customers might start noticing improvements as these measures advance. We are maintaining ongoing monitoring of the situation to guarantee complete service restoration and to prevent any further recurrences. The next update will be provided within 2 hours, or sooner if there are significant developments.

    • investigating

      Impact Statement: Starting at 04:27 UTC on 29 May 2026, we are investigating an incident which is impacting multiple services in West US 2, due to a power event. This impacts service accessibility region-wide, with customers potentially experiencing increased latency and intermittent connectivity, including timeouts when connecting to resources. Affected Azure services include, but are not limited to: App Service, Azure Functions, Azure Virtual Machines, Azure Virtual Machine Scale Sets, Azure Backup, Azure Container Registry, Azure Cosmos DB, Azure Database for MySQL flexible servers, Azure Database PostgreSQL Flexible Server, Azure IoT Hub, Azure Kubernetes Service (AKS), Azure Monitor, Application Insights, Log Analytics, Azure NetApp Files, Azure Site Recovery, Azure Synapse Analytics, Microsoft Defender for Cloud, Azure Databricks and Azure Storage, Redis Cache, Azure SQL, Azure Managed Grafana Current Status: We identified this issue through our automated monitoring after detecting elevated alerts related to network and infrastructure health in the West US 2 region. The issue was triggered by a power event in the datacenter, which impacted underlying infrastructure and led to increased latency and intermittent connectivity for select resources. We are aware of the impact and are actively investigating. Mitigation efforts are underway to restore affected network components across dependent services, including Storage and Compute. Customers may begin to see signs of recovery as these actions progress. The next update will be provided within 2 hours, or sooner if there are significant developments.

    • investigating

      Impact Statement: Starting at 04:27 UTC on 29 May 2026, we are investigating an incident which is impacting multiple services in West US 2, due to a power event. This impacts service accessibility in the region, with customers potentially experiencing increased latency and intermittent connectivity, including timeouts when connecting to resources. Affected Azure services include, but are not limited to: App Service, Azure Backup, Azure Container Registry, Azure Cosmos DB, Azure Database for MySQL flexible servers, Azure IoT Hub, Azure Kubernetes Service (AKS), Azure Monitor, Application Insights, Log Analytics, Azure NetApp Files, Azure Site Recovery, Azure Synapse Analytics, Microsoft Defender for Cloud, Azure Databricks and Azure Storage. Current Status: We identified this issue through our automated monitoring after detecting elevated alerts related to network and infrastructure health in the West US 2 region. The issue was triggered by a power event in the datacenter, which impacted underlying infrastructure and led to increased latency and intermittent connectivity for select resources. We are aware of the impact and are actively investigating. Mitigation efforts are underway to restore affected network components across dependent services, including Storage and Compute. Customers may begin to see signs of recovery as these actions progress. The next update will be provided within 60 minutes, or sooner if there are significant developments.

    • investigating

      Impact Statement: Starting at 04:27 UTC on 29 May 2026, we are investigating an incident which is impacting multiple services in West US 2, due to a power event. This impacts service accessibility in the region, with customers potentially experiencing increased latency and intermittent connectivity, including timeouts when connecting to resources. Current Status: We identified this issue through our automated monitoring after detecting elevated alerts related to network and infrastructure health in the West US 2 region. The issue was triggered by a power event in the datacenter, which impacted underlying infrastructure and led to increased latency and intermittent connectivity for select resources. We are aware of the impact and are actively investigating. Mitigation efforts are underway to restore affected network components across dependent services, including Storage and Compute. Customers may begin to see signs of recovery as these actions progress. The next update will be provided within 60 minutes, or sooner if there are significant developments.