<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: 3 Bars &#124; 3 Questions: Singapore</title>
	<atom:link href="http://blog.softlayer.com/2011/3-bars-3-questions-singapore/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.softlayer.com/2011/3-bars-3-questions-singapore/</link>
	<description>A Behind the Scenes Look at the Best Hosting Provider in the World</description>
	<lastBuildDate>Tue, 21 May 2013 00:08:33 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.4.1</generator>
	<item>
		<title>By: Kevin Hazard</title>
		<link>http://blog.softlayer.com/2011/3-bars-3-questions-singapore/comment-page-1/#comment-31249</link>
		<dc:creator>Kevin Hazard</dc:creator>
		<pubDate>Tue, 15 Nov 2011 20:43:48 +0000</pubDate>
		<guid isPermaLink="false">http://blog.softlayer.com/?p=5837#comment-31249</guid>
		<description>Thanks for the comment, Paul. As we&#039;ve started expanding our private network internationally, we&#039;ve run into a few situations like this one. Our network engineers are always trying to dial in more efficient routes and connect with more peering providers to provide the most optimal routes from any point in the world to a server in our data center, and that process isn&#039;t as easy as it seems.

In some cases, the advertised routes will go &quot;out of their way&quot; to a point of presence geographically farther away to provide faster or more reliable connectivity to users. That may be the result of peering relationships being unavailable across the geographically shorter distance or it might be the result of ISPs in a certain area forcing traffic through a sub-optimal route for one reason or another (whether it be capacity, usage, maintenance, etc.). We try to keep an open dialog with ISPs around the world to help ensure the most optimal routes between facilities, and the information you shared here is helpful as we continue those discussions.

While we can&#039;t guarantee that the route will change immediately, our team is going to do our best to streamline that network path, given whatever limitations are present. Keep an eye on whether the route changes at all in the next few weeks, and send me an update every now and then, and I&#039;ll see if we&#039;re able to make any progress with the providers involved in your network path to make your route more efficient: khazard@softlayer.com</description>
		<content:encoded><![CDATA[<p>Thanks for the comment, Paul. As we&#8217;ve started expanding our private network internationally, we&#8217;ve run into a few situations like this one. Our network engineers are always trying to dial in more efficient routes and connect with more peering providers to provide the most optimal routes from any point in the world to a server in our data center, and that process isn&#8217;t as easy as it seems.</p>
<p>In some cases, the advertised routes will go &#8220;out of their way&#8221; to a point of presence geographically farther away to provide faster or more reliable connectivity to users. That may be the result of peering relationships being unavailable across the geographically shorter distance or it might be the result of ISPs in a certain area forcing traffic through a sub-optimal route for one reason or another (whether it be capacity, usage, maintenance, etc.). We try to keep an open dialog with ISPs around the world to help ensure the most optimal routes between facilities, and the information you shared here is helpful as we continue those discussions.</p>
<p>While we can&#8217;t guarantee that the route will change immediately, our team is going to do our best to streamline that network path, given whatever limitations are present. Keep an eye on whether the route changes at all in the next few weeks, and send me an update every now and then, and I&#8217;ll see if we&#8217;re able to make any progress with the providers involved in your network path to make your route more efficient: <a href="mailto:khazard@softlayer.com">khazard@softlayer.com</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Paul Tan</title>
		<link>http://blog.softlayer.com/2011/3-bars-3-questions-singapore/comment-page-1/#comment-31241</link>
		<dc:creator>Paul Tan</dc:creator>
		<pubDate>Tue, 15 Nov 2011 17:00:39 +0000</pubDate>
		<guid isPermaLink="false">http://blog.softlayer.com/?p=5837#comment-31241</guid>
		<description>I am from Malaysia and I have two servers in Softlayer&#039;s SG datacenter. Just wish there was a direct route between Malaysia and the SG datacenter... the route SEEMS to go through Hongkong now.

Tracing ...........*.T
TTL LFT trace to 216.185.109.243:80/tcp
 1  [AS?] [NULL] 192.168.1.1 1.5ms
 2  [4788] [XDSLSTREAMYX] 60.53.175.50 5.6ms
 3  [4788] [XDSLSTREAMYX] 60.53.175.49 6.1ms
 4  [AS?] [NULL] 10.55.208.80 40.0ms
 5  [17888] [HKIX-HK] softlayer-10g.hkix.net (202.40.161.241) 47.0ms
 6  [36351] [IANA-NETBLOCK-50] ae7.bbr01.pn01.hkg01.networklayer.com (50.97.18.175) 46.5ms
 7  [36351] [IANA-NETBLOCK-50] ae0.bbr02.eq01.sng02.networklayer.com (50.97.18.172) 42.0ms
 8  [36351] [IANA-NETBLOCK-50] ae7.bbr01.eq01.sng02.networklayer.com (50.97.18.170) 40.2ms
 9  [36351] [IANA-NETBLOCK-50] ae5.dar01.sr03.sng01.networklayer.com (50.97.18.197) 53.9ms
10  [36351] [NETBLK-THEPLANET-BLK-15] po1.fcr01.sr03.sng01.networklayer.com (174.133.118.131) 47.3ms
11  [21844] [NETBLK-THEPLANET-BLK-3] [target closed] xxxxxxxxxxx 43.1ms</description>
		<content:encoded><![CDATA[<p>I am from Malaysia and I have two servers in Softlayer&#8217;s SG datacenter. Just wish there was a direct route between Malaysia and the SG datacenter&#8230; the route SEEMS to go through Hongkong now.</p>
<p>Tracing &#8230;&#8230;&#8230;..*.T<br />
TTL LFT trace to 216.185.109.243:80/tcp<br />
 1  [AS?] [NULL] 192.168.1.1 1.5ms<br />
 2  [4788] [XDSLSTREAMYX] 60.53.175.50 5.6ms<br />
 3  [4788] [XDSLSTREAMYX] 60.53.175.49 6.1ms<br />
 4  [AS?] [NULL] 10.55.208.80 40.0ms<br />
 5  [17888] [HKIX-HK] softlayer-10g.hkix.net (202.40.161.241) 47.0ms<br />
 6  [36351] [IANA-NETBLOCK-50] ae7.bbr01.pn01.hkg01.networklayer.com (50.97.18.175) 46.5ms<br />
 7  [36351] [IANA-NETBLOCK-50] ae0.bbr02.eq01.sng02.networklayer.com (50.97.18.172) 42.0ms<br />
 8  [36351] [IANA-NETBLOCK-50] ae7.bbr01.eq01.sng02.networklayer.com (50.97.18.170) 40.2ms<br />
 9  [36351] [IANA-NETBLOCK-50] ae5.dar01.sr03.sng01.networklayer.com (50.97.18.197) 53.9ms<br />
10  [36351] [NETBLK-THEPLANET-BLK-15] po1.fcr01.sr03.sng01.networklayer.com (174.133.118.131) 47.3ms<br />
11  [21844] [NETBLK-THEPLANET-BLK-3] [target closed] xxxxxxxxxxx 43.1ms</p>
]]></content:encoded>
	</item>
</channel>
</rss>
