Comments on: Global Network: The Proof is in the Traceroute http://blog.softlayer.com/2011/global-network-the-proof-is-in-the-traceroute/ A Behind the Scenes Look at the Best Hosting Provider in the World Fri, 24 May 2013 11:59:58 +0000 hourly 1 http://wordpress.org/?v=3.4.1 By: Kevin Hazard http://blog.softlayer.com/2011/global-network-the-proof-is-in-the-traceroute/comment-page-1/#comment-41076 Kevin Hazard Mon, 23 Jul 2012 19:17:33 +0000 http://blog.softlayer.com/?p=6421#comment-41076 As of right now, there are no immediate plans to open a full data center in Hong Kong or Japan. If you need a direct or peering connection with your SoftLayer infrastructure through one of our points of presence, ask to be connected with the network operations team via a support ticket, and they'll have the best insight about whether your specific use-case is possible. As of right now, there are no immediate plans to open a full data center in Hong Kong or Japan. If you need a direct or peering connection with your SoftLayer infrastructure through one of our points of presence, ask to be connected with the network operations team via a support ticket, and they’ll have the best insight about whether your specific use-case is possible.

]]> By: SL Fan http://blog.softlayer.com/2011/global-network-the-proof-is-in-the-traceroute/comment-page-1/#comment-41073 SL Fan Mon, 23 Jul 2012 11:54:15 +0000 http://blog.softlayer.com/?p=6421#comment-41073 Any plans on opening DC in HK and Japan? Also, who can I talk to if I want our infrastructure in HK to directly connect to SL PoP in HKIX? Any plans on opening DC in HK and Japan?

Also, who can I talk to if I want our infrastructure in HK to directly connect to SL PoP in HKIX?

]]> By: sumeet sharma http://blog.softlayer.com/2011/global-network-the-proof-is-in-the-traceroute/comment-page-1/#comment-40389 sumeet sharma Sun, 24 Jun 2012 11:29:05 +0000 http://blog.softlayer.com/?p=6421#comment-40389 Would it be possible to find location of server and speed using tracert? Would it be possible to find location of server and speed using tracert?

]]> By: Py http://blog.softlayer.com/2011/global-network-the-proof-is-in-the-traceroute/comment-page-1/#comment-38121 Py Mon, 16 Apr 2012 09:56:45 +0000 http://blog.softlayer.com/?p=6421#comment-38121 Hmm. 1. Surely you should be asking why the latency jumped from 188ms to 381+ms between lax and dallas on softlayer's network in the pre-launch traceroutes? 12 te1-6.bbr01.cs01.lax01.networklayer.com (66.109.11.42) 186.482 ms 188.265 ms 187.021 ms 13 ae7.bbr01.cs01.lax01.networklayer.com (173.192.18.166) 188.569 ms 191.100 ms 188.736 ms 14 po5.bbr01.eq01.dal01.networklayer.com (173.192.18.140) 381.645 ms 410.052 ms 420.311 ms 15 ae0.dar01.sr01.dal01.networklayer.com (173.192.18.211) 415.379 ms 415.902 ms 418.339 ms 2. If you practice hot potato routing (ie, hand off the packets to someone in dallas rather than in hong kong), doesn't that actually reduce the advantage you have from building a speedy global network? Eyeball -> content traffic will quickly jump onto your uncongested network, but content -> eyeball traffic will also quickly jump onto somebody else's (possibly congested) network... and most traffic is content -> eyeball. Hmm.

1. Surely you should be asking why the latency jumped from 188ms to 381+ms between lax and dallas on softlayer’s network in the pre-launch traceroutes?

12 te1-6.bbr01.cs01.lax01.networklayer.com (66.109.11.42) 186.482 ms 188.265 ms 187.021 ms
13 ae7.bbr01.cs01.lax01.networklayer.com (173.192.18.166) 188.569 ms 191.100 ms 188.736 ms
14 po5.bbr01.eq01.dal01.networklayer.com (173.192.18.140) 381.645 ms 410.052 ms 420.311 ms
15 ae0.dar01.sr01.dal01.networklayer.com (173.192.18.211) 415.379 ms 415.902 ms 418.339 ms

2. If you practice hot potato routing (ie, hand off the packets to someone in dallas rather than in hong kong), doesn’t that actually reduce the advantage you have from building a speedy global network? Eyeball -> content traffic will quickly jump onto your uncongested network, but content -> eyeball traffic will also quickly jump onto somebody else’s (possibly congested) network… and most traffic is content -> eyeball.

]]> By: addi http://blog.softlayer.com/2011/global-network-the-proof-is-in-the-traceroute/comment-page-1/#comment-37611 addi Fri, 30 Mar 2012 06:59:42 +0000 http://blog.softlayer.com/?p=6421#comment-37611 I think it would be really helpful if softlayer posted traffic/link utilization graphs. this would really boost confidence in your network if you run your links under utilized. Reverse traceroute tools would be great also. Sometimes I get horrid speeds when downloading off softlayer, I assume its because softlayer has congested links I think it would be really helpful if softlayer posted traffic/link utilization graphs. this would really boost confidence in your network if you run your links under utilized.

Reverse traceroute tools would be great also. Sometimes I get horrid speeds when downloading off softlayer, I assume its because softlayer has congested links

]]> By: Kevin Hazard http://blog.softlayer.com/2011/global-network-the-proof-is-in-the-traceroute/comment-page-1/#comment-33270 Kevin Hazard Thu, 08 Dec 2011 16:17:12 +0000 http://blog.softlayer.com/?p=6421#comment-33270 No problem at all, Charles. The return traceroute doesn't show which provider brought the traffic back across the ocean (hop 7). Like I said following your first traceroutes, sub-200ms routes from San Jose, CA, to Hong Kong are pretty quick, considering the fact the data is traveling more than 7,000 miles. If you ever run into spikes in latency, drop a ticket in for our NOC, and the network engineers will see what we can do to optimize the routes. Ianh, our core business is built on a platform that's significantly different from many providers in the industry, so we're not in a hurry to focus on colocation services until we can find a way to innovate in that area of the market. Many of SoftLayer's benefits are made possible by our pod-concept data center design and consistent hardware throughout, so we couldn't guarantee the same kind of performance and functionality for different hardware and configurations. What's most appealing to you about colo? No problem at all, Charles. The return traceroute doesn’t show which provider brought the traffic back across the ocean (hop 7). Like I said following your first traceroutes, sub-200ms routes from San Jose, CA, to Hong Kong are pretty quick, considering the fact the data is traveling more than 7,000 miles. If you ever run into spikes in latency, drop a ticket in for our NOC, and the network engineers will see what we can do to optimize the routes.

Ianh, our core business is built on a platform that’s significantly different from many providers in the industry, so we’re not in a hurry to focus on colocation services until we can find a way to innovate in that area of the market. Many of SoftLayer’s benefits are made possible by our pod-concept data center design and consistent hardware throughout, so we couldn’t guarantee the same kind of performance and functionality for different hardware and configurations. What’s most appealing to you about colo?

]]> By: lanh http://blog.softlayer.com/2011/global-network-the-proof-is-in-the-traceroute/comment-page-1/#comment-33216 lanh Thu, 08 Dec 2011 02:55:16 +0000 http://blog.softlayer.com/?p=6421#comment-33216 This is great, I love your network but I prefer to colo, are you planning to provide collocation services in the near future? This is great, I love your network but I prefer to colo, are you planning to provide collocation services in the near future?

]]> By: Charles http://blog.softlayer.com/2011/global-network-the-proof-is-in-the-traceroute/comment-page-1/#comment-33198 Charles Wed, 07 Dec 2011 22:24:21 +0000 http://blog.softlayer.com/?p=6421#comment-33198 Kevin, thanks for your explanation. It would be nicer to pass through the HKIX from server to Softlayer to the users in Hong Kong, since some of the ISP in Hong Kong do not have sufficient oversea bandwidth. Kevin, thanks for your explanation.
It would be nicer to pass through the HKIX from server to Softlayer to the users in Hong Kong, since some of the ISP in Hong Kong do not have sufficient oversea bandwidth.

]]> By: Kevin Hazard http://blog.softlayer.com/2011/global-network-the-proof-is-in-the-traceroute/comment-page-1/#comment-33072 Kevin Hazard Tue, 06 Dec 2011 17:18:16 +0000 http://blog.softlayer.com/?p=6421#comment-33072 Thanks for the follow-up Charles. I got a little more detail from someone on our networking team about why you're seeing the different routes. We use "<a href="http://en.wikipedia.org/wiki/Hot-potato_and_cold-potato_routing" rel="nofollow">hot-potato routing</a>" to best determine the path to a given IP address. If you're going to a SoftLayer server, other ISPs are more likely to give us the "hot potato" quickly because we can get it to our destination quickly (and we will incur the costs in doing so). When you're on the SoftLayer network and you're going to an external IP address, we'll pass the "hot potato" to an ISP that may claim a better route to that destination IP address. If you ran the traceroute from your server in SJC to our SNG test IP (216.12.196.114) you'd see the traffic stay on our network because the destination is on our network. Also, if you noticed any significant problems with the return route traveling over our peer's network across the Pacific Ocean, our NOC could adjust the routes to ensure consistent performance. Thanks for the follow-up Charles. I got a little more detail from someone on our networking team about why you’re seeing the different routes. We use “hot-potato routing” to best determine the path to a given IP address. If you’re going to a SoftLayer server, other ISPs are more likely to give us the “hot potato” quickly because we can get it to our destination quickly (and we will incur the costs in doing so). When you’re on the SoftLayer network and you’re going to an external IP address, we’ll pass the “hot potato” to an ISP that may claim a better route to that destination IP address.

If you ran the traceroute from your server in SJC to our SNG test IP (216.12.196.114) you’d see the traffic stay on our network because the destination is on our network. Also, if you noticed any significant problems with the return route traveling over our peer’s network across the Pacific Ocean, our NOC could adjust the routes to ensure consistent performance.

]]> By: Charles http://blog.softlayer.com/2011/global-network-the-proof-is-in-the-traceroute/comment-page-1/#comment-32832 Charles Sun, 04 Dec 2011 01:45:29 +0000 http://blog.softlayer.com/?p=6421#comment-32832 Kevin, I thought the route should be connect to HKIX, as I see Softlayer has a POP in Hong Kong and having a 10G peer with HKIX. There is a traceroute from another isp in Hong Kong (hkbn.net). 1 5 ms 3 ms 6 ms 014198216001.ctinets.com [14.198.216.1] 2 10 ms 10 ms 15 ms 061093016209.ctinets.com [61.93.16.209] 3 6 ms 11 ms 11 ms 014199254073.ctinets.com [14.199.254.73] 4 5 ms 3 ms 3 ms 014136129106.ctinets.com [14.136.129.106] 5 6 ms 6 ms 6 ms softlayer-10G.hkix.net [202.40.161.241] 6 50 ms 57 ms 50 ms ae0.bbr02.eq01.tok01.networklayer.com [50.97.18. 166] 7 101 ms 50 ms 54 ms ae7.bbr01.eq01.tok01.networklayer.com [50.97.18. 162] 8 167 ms 166 ms 183 ms ae2.bbr02.eq01.sjc02.networklayer.com [50.97.18. 160] 9 166 ms 166 ms 166 ms ae5.dar02.sr01.sjc01.networklayer.com [173.192.1 8.251] 10 169 ms 168 ms 166 ms po2.fcr01.sr01.sjc01.networklayer.com [50.23.118 .133] 11 166 ms 166 ms 166 ms speedtest.sjc01.softlayer.com [50.23.64.58] However, the traceroute from my SJC server to hkbn still using Any2, not the Softlayer transit. traceroute to 14.198.222.223 (14.198.222.223), 30 hops max, 40 byte packets 1 50.23.*.*-static.reverse.softlayer.com (50.23.*.*) 0.427 ms 0.539 ms 0.642 ms 2 ae0.dar01.sr01.sjc01.networklayer.com (50.23.118.130) 0.494 ms 0.488 ms 0.478 ms 3 ae8.bbr01.eq01.sjc02.networklayer.com (173.192.18.248) 0.910 ms 0.908 ms 0.890 ms 4 ae7.bbr02.eq01.sjc02.networklayer.com (173.192.18.165) 15.390 ms 15.389 ms 15.372 ms 5 ae0.bbr02.cs01.lax01.networklayer.com (173.192.18.151) 8.584 ms 8.580 ms 8.862 ms 6 ae7.bbr01.cs01.lax01.networklayer.com (173.192.18.166) 8.683 ms 8.679 ms 8.564 ms 7 * * * 8 014136129013.ctinets.com (14.136.129.13) 172.211 ms 172.312 ms 172.304 ms 9 014199254078.ctinets.com (14.199.254.78) 170.538 ms 175.652 ms 175.538 ms 10 061093016210.ctinets.com (61.93.16.210) 175.458 ms 175.768 ms 175.216 ms 11 * * * 12 * * * Kevin, I thought the route should be connect to HKIX, as I see Softlayer has a POP in Hong Kong and having a 10G peer with HKIX.

There is a traceroute from another isp in Hong Kong (hkbn.net).

1 5 ms 3 ms 6 ms 014198216001.ctinets.com [14.198.216.1]
2 10 ms 10 ms 15 ms 061093016209.ctinets.com [61.93.16.209]
3 6 ms 11 ms 11 ms 014199254073.ctinets.com [14.199.254.73]
4 5 ms 3 ms 3 ms 014136129106.ctinets.com [14.136.129.106]
5 6 ms 6 ms 6 ms softlayer-10G.hkix.net [202.40.161.241]
6 50 ms 57 ms 50 ms ae0.bbr02.eq01.tok01.networklayer.com [50.97.18.
166]
7 101 ms 50 ms 54 ms ae7.bbr01.eq01.tok01.networklayer.com [50.97.18.
162]
8 167 ms 166 ms 183 ms ae2.bbr02.eq01.sjc02.networklayer.com [50.97.18.
160]
9 166 ms 166 ms 166 ms ae5.dar02.sr01.sjc01.networklayer.com [173.192.1
8.251]
10 169 ms 168 ms 166 ms po2.fcr01.sr01.sjc01.networklayer.com [50.23.118
.133]
11 166 ms 166 ms 166 ms speedtest.sjc01.softlayer.com [50.23.64.58]

However, the traceroute from my SJC server to hkbn still using Any2, not the Softlayer transit.

traceroute to 14.198.222.223 (14.198.222.223), 30 hops max, 40 byte packets
1 50.23.*.*-static.reverse.softlayer.com (50.23.*.*) 0.427 ms 0.539 ms 0.642 ms
2 ae0.dar01.sr01.sjc01.networklayer.com (50.23.118.130) 0.494 ms 0.488 ms 0.478 ms
3 ae8.bbr01.eq01.sjc02.networklayer.com (173.192.18.248) 0.910 ms 0.908 ms 0.890 ms
4 ae7.bbr02.eq01.sjc02.networklayer.com (173.192.18.165) 15.390 ms 15.389 ms 15.372 ms
5 ae0.bbr02.cs01.lax01.networklayer.com (173.192.18.151) 8.584 ms 8.580 ms 8.862 ms
6 ae7.bbr01.cs01.lax01.networklayer.com (173.192.18.166) 8.683 ms 8.679 ms 8.564 ms
7 * * *
8 014136129013.ctinets.com (14.136.129.13) 172.211 ms 172.312 ms 172.304 ms
9 014199254078.ctinets.com (14.199.254.78) 170.538 ms 175.652 ms 175.538 ms
10 061093016210.ctinets.com (61.93.16.210) 175.458 ms 175.768 ms 175.216 ms
11 * * *
12 * * *

]]>