Linked by David Adams on Thu 1st Mar 2012 22:53 UTC, submitted by judgen
Microsoft The outage on Microsoft's Windows Azure cloud computing platform that caused the government's G-Cloud service to go offline was the result of a calculation error caused by the extra day in February due to the leap year. Writing on the Azure blog the firm's corporate vice president for service and cloud, Bill Laing, said while the firm had still to fully determine the cause of the issue, the extra date in the month appeared the most likely cause.
Permalink for comment 509262
To read all comments associated with this story, please click here.
RE: Wtf? Really?
by B. Janssen on Fri 2nd Mar 2012 09:58 UTC in reply to "Wtf? Really?"
B. Janssen
Member since:
2006-10-11

The reason is that they didn't think about leap years? In 2012, this is the error they made? It's not like it's some unexpected even we didn't see coming.
You know, I would have found this acceptable in someone's pet OSS project but not in a global service from MS that you probably pay an arm and a leg for.

Agreed, that's just embarrassing. But...

If I was the guy who was responsible for this in "the government" I would have been having a serious talk with my account rep already and it would not have been easy for them convince me to continue using their product.

...you would only complain and try to get some monetary recognition out of it, but you wouldn't quit using the service. And you know why. This is not just picking up your ball and going, it's picking up the goal posts, the fences, the benches, the lawn and the parking lot, too. I don't claim to know how large the gov's data is on Azure, but I'm sure it is somewhere in the region where you don't move on a whim.

And on top of that 1 day in 366 is probably well within agreed outage levels (I'd guess they have 99.9%, so they would be covered.)

Reply Parent Score: 2