上周四,也就是2007年8月16日,Skype的点对点网络出现了不稳定的情况,且经历了一段较长时间的故障,直到18日Skype网络才逐步回复正常,那么那一天Skype到底发生了什么呢?带着好奇心我们去官方博客看看官方的最新解释!今天官方博客正式发表了关于16日Skype发生情况的说明,大致意思如下:    该故障的起因是全球范围内大量用户的计算机在很短时间内被重启,而重启的原因则是Skype客户端接收到了定期的软件更新. (Tom - Skype)

    The disruption was initiated by a massive restart of our user's computers across the globe within a very short timeframe as they re-booted after receiving a routine software update. (Skype - HeartBeat)

    这种异常数量的重启影响了Skype的网络资源.也就是说,大量的重启动作触发了大量的登录请求,造成了Skype的点对点网络资源告急,进而引发了连锁反应和严重影响. (Tom - Skype)

    The abnormally high number of restarts affected Skype's network resources. This caused a flood of log-in requests, which, combined with the lack of peer-to-peer network resources, prompted a chain reaction that had a critical impact. (Skype - HeartBeat)

    通常情况下,Skype的点对点网络具有内建的自救能力.但此次事故暴露出了一个之前未被发现的存在于网络资源分配算法中的软件漏洞,该漏洞阻止了自救功能的快速响应.而由于此次事故,大多数用户在近两天时间内都无法正常使用Skype,为此我们深表歉意.(Tom - Skype)

    Normally Skype's peer-to-peer network has an inbuilt ability to self-heal, however, this event revealed a previously unseen software bug within the network resource allocation algorithm which prevented the self-healing function from working quickly. Regrettably, as a result of this disruption, Skype was unavailable to the majority of its users for approximately two days.(Skype - HeartBeat)

    此次事故已在Skype内部被清楚地查明.我们可以十分确定的是,此次事故中没有出现任何恶意攻击或行为,广大用户的安全性也没有经历任何风险. (Tom - Skype)

    The issue has now been identified explicitly within Skype. We can confirm categorically that no malicious activities were attributed or that our users' security was not, at any point, at risk.(Skype - HeartBeat)

从这篇解释中我们可以获知如下几点:

    1、并不是人为的恶意攻击导致服务网络瘫痪

    2、用户数据依旧安全并未遭到任何危险

    3、软件设计中存在网络资源分配的漏洞是发生此事故的因由

具体的原因不是我们讨论的重点,不过在宕机事件发生之后,官方采取的公关措施很是值得我们学习与借鉴,不是一味的隐瞒与逃避而是积极的沟通与交流,这些为技术人员处理此事赢得了时间同时也为赢得这场战争的胜利奠定了良好的基础.