Named in 1 record in this register, in 2026.
On 7 February 2026, one data centre within Microsoft's West US cloud region in California, United States, lost power. According to a post incident report that Microsoft published, an electrical failure in an on-site transformer caused the loss of utility...
On 20 October 2023 Microsoft detected instability on the utility grid, in the form of voltage sags and swells, at one of its data centres in the AZ-01 Availability Zone of its West Europe region in the Netherlands. The company decided to transfer the load...
Beginning at 22:19 UTC on 15 March 2017, a main breaker tripped in one of the redundant upstream remote power panels serving a storage scale unit in Microsoft Azure's East US region. As load transferred to the remaining power sources, the transfer caused a...
The record behind each entry: the manufacturer, integrator and operator, root cause, failure mode, downtime, losses and every source. One entry's record is £2.99 on its page.
On Friday 31 March 2017, Microsoft Azure services across Japan were affected for several hours after a failure at the Japan East data centre in Saitama Prefecture, near Tokyo. The facility is managed by a third party. Microsoft's status page said that one...
On 1 January 2014, at about 3pm, the National Park Service data centre in Denver, Colorado, lost utility power and went completely dark. According to a note posted on the agency's website, the outage was caused by an underground cable that had either suffered...
It counts the records in this register that name this company in any role. Being named is not a finding of fault. Most incidents have several contributing causes, and the company named as manufacturer, integrator, operator or contractor is often not the cause of what went wrong.
Counts reflect what public reporting names, so a company with a large installed base, or one operating where reporting is open, will appear more often than a company of the same size elsewhere. Read the counts alongside the note on coverage in the methodology.
If you work for this company and something here is wrong, tell us and we will correct it. Use the corrections page: we acknowledge within 2 working days and decide within 10.