Windows Azure, Microsoft’s cloud platform for developers, has apparently suffered a major meltdown, reports Mary Jo Foley at ZDNet.
“ZDNet UK reported that the initial Azure problems began with an outage in the Windows Azure Management Service technology, which then spread to the Windows Azure Compute and Access Control parts of the platform,” Foley wrote. “Affected areas included North Europe, North Central US and South Central US regions, ZDNet UK said.”
We’ve requested information from Microsoft and update when we get it.
UPDATE 9:30 a.m.: Microsoft sent the following statement:
On February 28th, 2012 at 5:45 PM PST Microsoft became aware of an issue impacting Windows Azure service management in a number of regions. Windows Azure engineering teams developed, validated and deployed a fix that resolved the issue for the majority of our customers. Some customers in 3 sub regions – North Central US, South Central and North Europe – remain affected. Engineering teams are actively working to resolve the issue as soon as possible We will update the Service Dashboard, hourly until this incident is resolved.
UPDATE 3/1/12: Bill Laing, Microsoft corporate VP of Server and Cloud, posted this Wednesday afternoon on the official Windows Azure blog:
Yesterday, February 28th, 2012 at 5:45 PM PST Windows Azure operations became aware of an issue impacting the compute service in a number of regions. The issue was quickly triaged and it was determined to be caused by a software bug. While final root cause analysis is in progress, this issue appears to be due to a time calculation that was incorrect for the leap year. Once we discovered the issue we immediately took steps to protect customer services that were already up and running, and began creating a fix for the issue. The fix was successfully deployed to most of the Windows Azure sub-regions and we restored Windows Azure service availability to the majority of our customers and services by 2:57AM PST, Feb 29th.
UPDATE 3/10/12: The Windows Azure team takes a more detailed look at what happened with a blog post here.