Is Microsoft Azure down?

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.

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.

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

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.

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.