TENET peering at LINX

More interesting traceroute data [target www.yahoo.com]:

8 v2750-tiger-brie.uni.net.za (155.232.145.226) 2.732 ms
9 unknown.uni.net.za (196.32.209.25) 152.780 ms
10 ge-1-1-0.pat1.the.yahoo.com (195.66.224.129) 154.808 ms
11 so-0-1-0.msr1.ird.yahoo.com (66.196.65.33) 163.932 ms
12 gi-1-1.bas-b1.ird.yahoo.com (87.248.101.1) 164.020 ms
13 f1.us.www.vip.ird.yahoo.com (87.248.113.14) [open] 165.543 ms


The TENET router in London (196.32.209.25) connects to the Yahoo! AS, and the 195.66.224.0/19 router address is a giveaway that it's through LINX.

Testing other networks [target www.facebook.com] yields more data:

9 unknown.uni.net.za (196.32.209.25) 153.603 ms
10 linx.br01.lon1.tfbnw.net (195.66.225.69) 153.336 ms
11 xe-x-x-x.br01.ash1.tfbnw.net (204.15.22.245) 229.906 ms
12 te-13-0.csw06a.ash1.tfbnw.net (204.15.23.55) 233.942 ms
13 www.11.06.ash1.facebook.com (69.63.186.12) [open] 262.342 ms

where hop 10's hostname confirms the LINX connection, and also shows we're still connecting to the Virginia servers.

The LINX looking glass also shows the routing to TENET through AS1299 (Telia) and AS2914 (NTT) and directly.

Traffic graphs confirm significant traffic through LINX


Several other autonomous systems are reachable via LINX peering sessions, including hosting providers Hurricane Electric and LeaseWeb and CDN Limelight Networks [ex YouTube providers, and 2009 Presidential inauguration streamers].

Clearly this is in preparation for the new SEACOM pipe, although TENET is saving on transit requirements.

Don't care about nanowires? That's good.

[via DailyTech]

So UPenn researchers have discovered a good way of storing ternary digits.

Great news for Cisco, Juniper, et al. You may wonder why, and the answer is quite simple: TCAMs. Basically this could help speed up address mangling, e.g. for routing tables.

Gro'in' pains

Enough 80's references, let's skip to the meat of this post (so to speak). This is from a recent traceroute; DataHop might want to rename one of their nodes to accomodate some expansion in their traffic:

11 196.32.209.25 (196.32.209.25) 165.620 ms 160.809 ms
12 ge2-20-0-cr0.tch.uk.as6908.net (78.41.155.161) 236.578 ms 198.183 ms
13 te-4-2.r00.londen05.uk.bb.gin.ntt.net (83.231.146.69) 151.840 ms 153.098 ms