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

  • Get Started Using .NET Aspire with SQL Server & Azure SQL Database

    Microsoft experts are making the rounds educating developers about the company's new, opinionated, cloud-ready stack for building observable, production ready, distributed, cloud-native applications with .NET.

  • Microsoft Revamps Fledgling AutoGen Framework for Agentic AI

    Only at v0.4, Microsoft's AutoGen framework for agentic AI -- the hottest new trend in AI development -- has already undergone a complete revamp, going to an asynchronous, event-driven architecture.

  • IDE Irony: Coding Errors Cause 'Critical' Vulnerability in Visual Studio

    In a larger-than-normal Patch Tuesday, Microsoft warned of a "critical" vulnerability in Visual Studio that should be fixed immediately if automatic patching isn't enabled, ironically caused by coding errors.

  • Building Blazor Applications

    A trio of Blazor experts will conduct a full-day workshop for devs to learn everything about the tech a a March developer conference in Las Vegas keynoted by Microsoft execs and featuring many Microsoft devs.

  • Gradient Boosting Regression Using C#

    Dr. James McCaffrey from Microsoft Research presents a complete end-to-end demonstration of the gradient boosting regression technique, where the goal is to predict a single numeric value. Compared to existing library implementations of gradient boosting regression, a from-scratch implementation allows much easier customization and integration with other .NET systems.

Subscribe on YouTube