3 Bars | 3 Questions: Singapore

October 28, 2011

It's been a few months since the last 3 Bars 3 Questions with "The Mitch," and between then and now, a lot has changed in the SoftLayer world. The biggest difference: Our technicians have traveled around the world to build out data centers in Singapore and Amsterdam. I joined SoftLayer as general manager of the Asia-Pacific (APAC) region, and when I took a trip to Dallas to meet the rest of the team, Kevin was able to convince me to answer a few questions on video about what's been going on in Singapore:

Asia is the largest growth market for SoftLayer right now, and the flood of orders we've had to keep up with in our Singapore branch is a testament to the customer demand in that region. With our ambitious growth plans and early successes in SNG, you'll be seeing a lot of SoftLayermobiles delivering servers around the world pretty soon. Maybe we need a SoftLayerOceanTanker?

When I made trip to Dallas, I met Jonathan Wisler, another newly hired SLayer responsible for the Amsterdam data center and our future Europe, Middle East and Africa (EMEA) expansion. Because I didn't want him to feel left out, I selected him as my successor in the next 3 Bars 3 Questions interview.

If you have any questions about SoftLayer in Asia, our Singapore data center or Singapore in general, just let me know.

-Michael

Comments

November 15th, 2011 at 11:00am

I am from Malaysia and I have two servers in Softlayer'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

November 15th, 2011 at 2:43pm

Thanks for the comment, Paul. As we've started expanding our private network internationally, we'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't as easy as it seems.

In some cases, the advertised routes will go "out of their way" 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'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'll see if we're able to make any progress with the providers involved in your network path to make your route more efficient: khazard@softlayer.com

Leave a Reply

Filtered HTML

  • Web page addresses and e-mail addresses turn into links automatically.
  • You can enable syntax highlighting of source code with the following tags: <pre>, <blockcode>, <bash>, <c>, <cpp>, <drupal5>, <drupal6>, <java>, <javascript>, <php>, <python>, <ruby>. The supported tag styles are: <foo>, [foo].
  • Allowed HTML tags: <a> <em> <strong> <cite> <blockquote> <code> <ul> <ol> <li> <dl> <dt> <dd>
  • Lines and paragraphs break automatically.

Plain text

  • No HTML tags allowed.
  • Web page addresses and e-mail addresses turn into links automatically.
  • Lines and paragraphs break automatically.

Comments

November 15th, 2011 at 11:00am

I am from Malaysia and I have two servers in Softlayer'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

November 15th, 2011 at 2:43pm

Thanks for the comment, Paul. As we've started expanding our private network internationally, we'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't as easy as it seems.

In some cases, the advertised routes will go "out of their way" 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'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'll see if we're able to make any progress with the providers involved in your network path to make your route more efficient: khazard@softlayer.com

Leave a Reply

Filtered HTML

  • Web page addresses and e-mail addresses turn into links automatically.
  • You can enable syntax highlighting of source code with the following tags: <pre>, <blockcode>, <bash>, <c>, <cpp>, <drupal5>, <drupal6>, <java>, <javascript>, <php>, <python>, <ruby>. The supported tag styles are: <foo>, [foo].
  • Allowed HTML tags: <a> <em> <strong> <cite> <blockquote> <code> <ul> <ol> <li> <dl> <dt> <dd>
  • Lines and paragraphs break automatically.

Plain text

  • No HTML tags allowed.
  • Web page addresses and e-mail addresses turn into links automatically.
  • Lines and paragraphs break automatically.