Microsoft services outage blamed on routine maintenance

Earlier this morning, there was a service outage that affected many of Microsoft’s online products including Office 365, Outlook.com and some users reported issues accessing SkyDrive.

Well, if you think you are having a bad day, the outage, according to Microsoft, was based on routine maintenance that went awry. Microsoft has provided Neowin a comment on the issue:

“Some Microsoft services experienced a short-term issue as a result of a networking adjustment. We worked quickly to roll back the adjustments made and all services are now restored to normal.”

While we have seen cloud services go down in the past, seeing that this issue appears to be the result of human error and not a catastrophic failure of equipment center deep in a datacenter, is somewhat relieving. Because of this, it allowed for the quick recovery of the systems needed to get the services up and running again.

Report a problem with article
Previous Story

Microsoft exec slams low Google+ interaction rate

Next Story

Chinese firm labeled bloatware as Microsoft security update

13 Comments

Commenting is disabled on this article.

So much for "Cloud" security. If I had been working on a long report, being stored in the "Cloud" and it went "poof," I'd be pis_____. Who is going to redo the work and explain that to the boss? Thank you, Microsoft, I'll keep my applications and files on my computer.

Can any one tell, any one of the service which gave 100% up time? It happens sometimes (can be human error or some hardware failure)

nitins60 said,
Can any one tell, any one of the service which gave 100% up time? It happens sometimes (can be human error or some hardware failure)

This. What is more important then the downtime, is the time it takes to get it back up.
If its a few hours, there is nothing to complain. Even power goes down for a few hours every so often.

Shadowzz said,

This. What is more important then the downtime, is the time it takes to get it back up.
If its a few hours, there is nothing to complain. Even power goes down for a few hours every so often.

This isn't your typical free hotmail account.

Enterprises such as the one I work for were affected by this. Hundreds of users unable to get their job done because OWA (outlook web) was completly offline without notice, for hours. A service health page that gets an update 2 hours after the fact.

That's a paid service and cloud based products NEED to be reliable with very minimal downtime. Companies RELY on them to get the job done. This has happened at least 3 times in the last 3 months. And we're not talking about 5 minutes downtime. We're talking about HOURS without an update on the situation.

Saying it's not big deal because **** happens is crazy to say the least.

xplatinum said,

This isn't your typical free hotmail account.

Enterprises such as the one I work for were affected by this. Hundreds of users unable to get their job done because OWA (outlook web) was completly offline without notice, for hours. A service health page that gets an update 2 hours after the fact.

That's a paid service and cloud based products NEED to be reliable with very minimal downtime. Companies RELY on them to get the job done. This has happened at least 3 times in the last 3 months. And we're not talking about 5 minutes downtime. We're talking about HOURS without an update on the situation.

Saying it's not big deal because **** happens is crazy to say the least.

One of the reasons the owner of the conpany i work for WONT go cloud and i respect it. I would rather manager a lot of servers in our own server rooms with off site mirrors/backups in a data center heavily relying on the cloud is something I'm not comfortable with either

Sikh said,

One of the reasons the owner of the conpany i work for WONT go cloud and i respect it. I would rather manager a lot of servers in our own server rooms with off site mirrors/backups in a data center heavily relying on the cloud is something I'm not comfortable with either


I am not either. I would have stayed with Exchange 2010 with regular clients any day.

So those of us who didn't face the issue should brace for same implementation when the same maintenance schedule hits our region also ???

I hope you are not trolling, but do you really have to ask that question?

If something like this happens, especially for a company like Microsoft, it is already under investigation. Yes, they have figured out what caused the error, however, now, they are looking into how the error happened, and until they get to bottom of it, the maintenance procedure will not occur until it is corrected. Further testing may be needed in a smaller scale before they start implementing it to other servers.

They do this, so the same type of error will not occur in the future.

I guess they fixed every thing in their test environment before rolling it out to live servers yet the thing happened and happened while on schedule work phase, hence asked as may be this some thing which requires service to reboot or such which for sure is going to effect concerned users !!!