 themanPremium join:2000-08-02 Dallas, TX | reply to WhosTheBosch
Re: Telus Peering.said by WhosTheBosch:Here's mine, I'm in Vancouver on Telus as well. Looks like I'm one less hop than you though which causes 20ms more time.
Tracing route to 50.22.184.114-static.reverse.softlayer.com [50.22.184.114] over a maximum of 30 hops:
3 30 ms 30 ms 30 ms 204.225.244.101 4 30 ms 30 ms 30 ms eqix-ix.softlayer.com [198.32.176.207] 5 33 ms 32 ms 31 ms ae3.bbr01.eq01.sjc02.networklayer.com [173.192.1 8.240] 6 49 ms 49 ms 49 ms ae0.bbr02.wb01.sea02.networklayer.com [173.192.1 8.146] 7 48 ms 48 ms 48 ms ae1.dar01.sr01.sea01.networklayer.com [173.192.1 8.143] 8 50 ms 49 ms 48 ms po1.fcr02.sr03.sea01.networklayer.com [67.228.11 8.225] 9 50 ms 50 ms 49 ms 50.22.184.114-static.reverse.softlayer.com [50.2 2.184.114]
Trace complete.
What's really messed up is that for some reason it's routed to Toronto on 204.225.244.101 (»www.geobytes.com/IpLocator.htm?G···.244.101) and then New York on 198.32.176.207 (»www.geobytes.com/IpLocator.htm?G···.176.207) and then goes from there to San Jose. The reason it goes to NY from TO is the right thing for SL to do though as that's probably the closest node to TO. I have no idea why Telus decides to send West Coast traffic through Toronto, it's mind boggling.
After reviewing it, the main reason for an extra 20ms appears to be this part where it's hitting different nodes for some reason:
Shaw 7 35 ms 35 ms 34 ms te1-7.bbr01.eq01.sjc01.networklayer.com [206.223 .116.176] 8 34 ms 35 ms 35 ms ae0.bbr02.wb01.sea02.networklayer.com [173.192.1 8.146]
Telus 5 33 ms 32 ms 31 ms ae3.bbr01.eq01.sjc02.networklayer.com [173.192.1 8.240] 6 49 ms 49 ms 49 ms ae0.bbr02.wb01.sea02.networklayer.com [173.192.1 8.146]
I still think if Telus came around and manned up to joining SIX in Seattle, they could really improve their West Coast routing:
»www.seattleix.net/participants.htm Small update to this issue, it looks like Telus has joined the SIX and we're currently peering with them there. The new path looks to be around 16ms instead of 70ms.
traceroute to 142.179.56.1 (142.179.56.1), 64 hops max, 72 byte packets
3 slr01.sea01.softlayer.com (67.228.118.97) 0.623 ms 3.146 ms 0.425 ms
4 ae4.dar02.sr01.sea01.networklayer.com (67.228.118.210) 0.365 ms 0.349 ms 0.279 ms
5 ae9.bbr01.wb01.sea02.networklayer.com (173.192.18.158) 0.600 ms 0.601 ms 0.522 ms
6 six.telus.com (206.81.80.227) 0.729 ms 0.694 ms 0.622 ms
7 75.154.215.192 (75.154.215.192) 4.953 ms 5.791 ms 4.668 ms
8 d142-179-56-1.bchsia.telus.net (142.179.56.1) 15.589 ms 15.897 ms 15.659 ms
-- Director of Engineering -- SoftLayer Technologies, Inc. |
|
 parrelium join:2005-07-31 Abbotsford, BC kudos:1 Reviews:
·TELUS
2 edits | reply to WhosTheBosch  1 1 ms 1 ms 1 ms 192.168.1.254 2 6 ms 6 ms 6 ms 10.31.206.1 3 11 ms 10 ms 10 ms 75.154.217.103 4 46 ms 11 ms 10 ms te1-5.bbr01.wb01.sea01.networklayer.com [206.81.1.140] 5 11 ms 11 ms 11 ms ae0.dar01.sr01.sea01.networklayer.com [173.192.1.199] 6 11 ms 13 ms 12 ms po1.fcr02.sr03.sea01.networklayer.com [67.228.11.225] 7 11 ms 11 ms 11 ms 50.22.184.114tatic.reverse.softlayer.com [50.2.184.114] Trace Complete
My tracert is 11 ms to that address And on another note, my pings in general are better to seattle than ever before. |
|
 pfakPremium join:2002-12-29 Vancouver, BC | reply to theman
said by theman:Small update to this issue, it looks like Telus has joined the SIX and we're currently peering with them there. The new path looks to be around 16ms instead of 70ms.
traceroute to 142.179.56.1 (142.179.56.1), 64 hops max, 72 byte packets
3 slr01.sea01.softlayer.com (67.228.118.97) 0.623 ms 3.146 ms 0.425 ms
4 ae4.dar02.sr01.sea01.networklayer.com (67.228.118.210) 0.365 ms 0.349 ms 0.279 ms
5 ae9.bbr01.wb01.sea02.networklayer.com (173.192.18.158) 0.600 ms 0.601 ms 0.522 ms
6 six.telus.com (206.81.80.227) 0.729 ms 0.694 ms 0.622 ms
7 75.154.215.192 (75.154.215.192) 4.953 ms 5.791 ms 4.668 ms
8 d142-179-56-1.bchsia.telus.net (142.179.56.1) 15.589 ms 15.897 ms 15.659 ms
.. And satan skates to work. Guess I need to bother my ISP.
traceroute to 75.157.x.x (75.157.x.x), 30 hops max, 60 byte packets
1 10.242.7.21 (10.242.7.21) 0.498 ms 0.383 ms 0.456 ms
2 204.14.120.65 (204.14.120.65) 0.937 ms 1.004 ms 1.059 ms
3 216.18.227.9 (216.18.227.9) 0.914 ms 0.909 ms 0.966 ms
4 border2.te13-2.farreachnet-2.sea.pnap.net (206.253.223.189) 1.305 ms 1.354 ms 1.427 ms
5 core1.t6-1-bbnet1.sea.pnap.net (63.251.160.16) 1.262 ms 1.264 ms 1.304 ms
6 xe-0-3-0-5.r05.sttlwa01.us.bb.gin.ntt.net (198.104.202.45) 1.127 ms 0.747 ms 0.891 ms
7 xe-0-1-0-2.r05.sttlwa01.us.ce.gin.ntt.net (198.104.202.206) 1.519 ms 1.821 ms 1.812 ms
8 d75-157-x-x.bchsia.telus.net (75.157.x.x) 7.909 ms 7.902 ms 7.879 ms
/sigh. -- The more I C, the less I see. |
|
 jtl999Classified CEO join:2012-11-24 Reviews:
·Shaw
| reply to theman Yup.  |
|
 | I wonder if this has to do with the Netflix announcement and they have their caches at SIX? Or are they stored directly on Telus' network? |
|
 | Whatever the reason, this is a pretty nice move on their part. Most of the horrible latency to the West Coast problems should be fixed. |
|
|
|