Up to date under with new info from Microsoft, saying service has been restored to nearly all of prospects.
Microsoft’s cloud computing platform, Windows Azure, has been experiencing outages in quite a few areas all over the world for a lot of the day, apparently ensuing from a glitch associated to Leap Day, the additional day in February that happens as soon as each 4 years.
“On February twenty eighth, 2012 at 5:45 PM PST Microsoft turned conscious of a difficulty impacting Windows Azure service administration in a variety of areas. Windows Azure engineering groups developed, validated and deployed a repair that resolved the problem for almost all of our prospects. Some prospects in 3 sub areas – North Central US, South Central and North Europe – stay affected. Engineering groups are actively working to resolve the problem as quickly as attainable We are going to replace the Service Dashboard, hourly till this incident is resolved.”
Not like that AWS outage, there don’t seem like studies of main client web sites taking place on account of as we speak’s Azure outage, which may present extra insights into the character of Microsoft’s cloud buyer base.
Replace, 5:10 p.m.: Invoice Laing, the Microsoft company vice chairman in command of Windows Azure engineering, apologizes and offers an update in this blog post, confirming that it seems to have been a intercalary year concern. Right here’s an excerpt …
Yesterday, February twenty eighth, 2012 at 5:45 PM PST Windows Azure operations turned conscious of a difficulty impacting the compute service in a variety of areas. The problem was rapidly triaged and it was decided to be brought on by a software program bug. Whereas closing root trigger evaluation is in progress, this concern seems to be on account of a time calculation that was incorrect for the intercalary year. As soon as we found the problem we instantly took steps to guard buyer providers that had been already up and working, and started making a repair for the problem. The repair was efficiently deployed to many of the Windows Azure sub-regions and we restored Windows Azure service availability to nearly all of our prospects and providers by 2:57AM PST, Feb twenty ninth.
Nevertheless, some sub-regions and prospects are nonetheless experiencing points and on account of these points they could be experiencing a lack of software performance. We’re actively working to deal with these remaining points. Clients ought to consult with the Windows Azure Service Dashboard for up to date standing. Windows Azure Storage was not impacted by this concern.