"A wide variety of services were affected, including the Azure Kubernetes Service, Azure Confidential Compute and, ironically, Azure Site Recovery. Microsoft blamed the stoppage on "an unexpected interruption to utility power at one of our West US datacenters," which, "resulted in a loss of power to parts of the facility." Backup power systems were activated, but it took until 0423 UTC on February 8 before Microsoft declared the issue mitigated."
"At 1634 UTC on February 7, Microsoft admitted that the datacenter power outage had also impacted "customers' ability to complete operations in the Microsoft Store and Windows Update." "As a result, some users may experience failures or timeouts when installing or updating Microsoft Store apps, or when downloading Windows updates." Affected administrators received almost a three-hour reprieve from the company's update flow while Microsoft's engineers worked on the problem. By 1930 UTC on February 7, the company confirmed that the services had been restored."
A utility power interruption at a West US Azure datacenter caused intermittent unavailability, timeouts, and increased latency across multiple Azure services between 0800 UTC on February 7 and 0423 UTC on February 8. A wide range of services were affected, including Azure Kubernetes Service, Azure Confidential Compute, and Azure Site Recovery. Backup power systems activated and mitigation was declared at 0423 UTC on February 8. The outage also impacted Microsoft Store and Windows Update, producing failures or timeouts for some users and a near three-hour pause in update flow for administrators while engineers worked on restoration. Services were confirmed restored by 1930 UTC on February 7, though some IT administrators continued to see residual latency affecting Windows Server update operations and the Windows Server sync API, which was being addressed separately. Microsoft has experienced multiple recent incidents and outages.
Read at Theregister
Unable to calculate read time
Collection
[
|
...
]