News

Microsoft On Skype Outage: Don't Blame Us

Microsoft's official stance on the recent Skype outage that left millions of users without phone access for two days last week? "Hey, it's not our fault."

The outage, which began last Thursday and continued into Friday, resulted from a bug in Skype's software that wasn't able to handle the flood of system reboots from users following Microsoft's August Patch Tuesday release.

Christopher Budd, part of the Microsoft Security Response Team, stated in a blog entry that the released patches weren't the cause of the outage. "We checked to see if there were any issues introduced by the security updates that could have caused the situation, and we found that there were no issues introduced by the security updates themselves," he stated.

Skype agreed with that assessment. In a blog entry on the failure, Skype spokesperson Villu Arak said "We don't blame anyone but ourselves. The Microsoft Update patches were merely a catalyst -- a trigger -- for a series of events that led to the disruption of Skype, not the root cause of it."

Budd said in the blog that, from Microsoft's end, it was a typical Patch Tuesday. "We confirmed that there is nothing unusual in this month's release that could have contributed to this situation. From a release point of view, this month's release followed our usual format and processes." It was the largest number of patches released for a number of months, but Microsoft has had that large a release, and larger, in the past.

Again, Arak agreed and exonerated Microsoft. "In short -- there was nothing different about this set of Microsoft patches," he wrote.

In addition, it doesn't appear that the patches caused any widespread problems with other vendors' products.

Budd said Microsoft is very careful in determining the possible affects of patches. "We are always watching for any issues that could have an impact on deploying the security updates, and overall, our ongoing monitoring of the last week's release shows that the deployment of updates is going smoothly," he wrote.

But do Skype users have anything to worry about regarding future Microsoft patch releases? Arak said no. "The bug [that caused the outage] has been squashed ...We'd like to reassure our users across the globe that we've done everything we need to do to make sure this doesn't happen again."

About the Author

Keith Ward is the editor in chief of Virtualization & Cloud Review. Follow him on Twitter @VirtReviewKeith.

comments powered by Disqus

Featured

  • Compare New GitHub Copilot Free Plan for Visual Studio/VS Code to Paid Plans

    The free plan restricts the number of completions, chat requests and access to AI models, being suitable for occasional users and small projects.

  • Diving Deep into .NET MAUI

    Ever since someone figured out that fiddling bits results in source code, developers have sought one codebase for all types of apps on all platforms, with Microsoft's latest attempt to further that effort being .NET MAUI.

  • Copilot AI Boosts Abound in New VS Code v1.96

    Microsoft improved on its new "Copilot Edit" functionality in the latest release of Visual Studio Code, v1.96, its open-source based code editor that has become the most popular in the world according to many surveys.

  • AdaBoost Regression Using C#

    Dr. James McCaffrey from Microsoft Research presents a complete end-to-end demonstration of the AdaBoost.R2 algorithm for regression problems (where the goal is to predict a single numeric value). The implementation follows the original source research paper closely, so you can use it as a guide for customization for specific scenarios.

  • Versioning and Documenting ASP.NET Core Services

    Building an API with ASP.NET Core is only half the job. If your API is going to live more than one release cycle, you're going to need to version it. If you have other people building clients for it, you're going to need to document it.

Subscribe on YouTube