Cliff Saran’s Enterprise blog

Aug 20 2007   2:13PM GMT

Who’s to blame for Skype’s downtime

Cliff Saran Profile: Cliff Saran

Tags:
Downtime
Microsoft
Skype
Software Quality

Skype is now back online. But why did it fail? Villu Arak, writing on heatbeat.skype.com site stated:

The Skype peer-to-peer network became unstable and suffered a critical disruption. The disruption was triggered by a massive restart of our users’ computers across the globe within a very short timeframe as they re-booted after receiving a routine set of patches through Windows Update.

It looks like Microsoft’s August 14th patch update may be the root cause for Skype spectacular crash. Skype user who downloaded the monthly MS patch had their PCs reboot as part of the update, causing them to restart and login to Skype. This led to a flood of log-in requests. According to Arak, combined with the lack of peer-to-peer network resources, this prompted a chain reaction that had a critical impact – in effect, it was a massive denial of service attack caused by Skype users all trying to login at the same time.

The key question is who is responsible. Should Microsoft be held accountable. Perhaps Windows Update could be reengineered to stagger updates? Maybe the users are at fault as they all tried logging in at the same time. Or Skype should have foreseen these circumstances and worked around such am occurrence.

What Skype’s downtime does show is the fragility of modern IT systems to external factors.

1  Comment on this Post

 
There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when other members comment.
  • Jan w
    Skype IT must use a product of PatchLinke for the Patch Management .

    They wood not have had the problem.

    Regards,

    jan w

    0 pointsBadges:
    report

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

Share this item with your network: