Understanding Today's Skype Outage: Explaining Supernodes
disruptivetelephony.com
Understanding Today's Skype Outage: Explaining Supernodes
1–10 of 19 posts
Re: Understanding Today's Skype Outage: Explaining Supernodes
#2Re: Understanding Today's Skype Outage: Explaining Supernodes
#3Re: Understanding Today's Skype Outage: Explaining Supernodes
#4I can imagine ipv6 would greatly benefit Skype.
Re: Understanding Today's Skype Outage: Explaining Supernodes
#5Re: Understanding Today's Skype Outage: Explaining Supernodes
#6In other words, supernodes are nodes connected behind a routable IP with a minimum of bandwidth. They are used to provide NAT traversal for unroutable clients. I can imagine ipv6 would greatly benefit Skype.
Re: Understanding Today's Skype Outage: Explaining Supernodes
#7That Skype uses supernodes is interesting, but makes some sense since it was developed by the same people who developed Kazaa (a P2P filesharing service), which as I recall has a similar architecture.
http://blogs.skype.com/en/2009/11/joltid_settlement.html
There were in fact several lawsuits related to licencing this stuff.
Re: Understanding Today's Skype Outage: Explaining Supernodes
#8Re: Understanding Today's Skype Outage: Explaining Supernodes
#9My theory: Tons of supernodes (static ip with no NAT, broadband, constantly on) are in the 20s-30s age group and are on holiday. Plus office and university machines that are normally left on have been turned off. The people I know in universities across Europe normally have skype on at work constantly, or at least during the day, and most have static ips on their uni networks so I imagine they get selected as superno…
[1] Since the last outage was 3 years ago. I can't find a source for that right now -- would be interesting to see if the outage was also around Christmas time.
Re: Understanding Today's Skype Outage: Explaining Supernodes
#10In other words, supernodes are nodes connected behind a routable IP with a minimum of bandwidth. They are used to provide NAT traversal for unroutable clients. I can imagine ipv6 would greatly benefit Skype.
It's not just to solve the NAT problem. There are no servers in the traditional sense, it's a "cloud" of peer-to-peer clients (that are also, strictly speaking, servers), and you need some way of "bootstrapping" yourself into that cloud when you sign in. Supernodes fix this problem easily, but I have to wonder why it was a relatively short list hardcoded into the client... it wouldn't be hard to make it a bit more ad…
In fact, I found I was able to reconnect faster after the outage by deleting the shared.xml file that stores known supernodes - presumably connecting back to Skype-operated bootstrap servers.