Cat Routing To Singapore Via Japan

[mattcodes]

CAT routing to singapore now goes through Japan (&lt;deleted&gt;?), used to sub <125ms. How do I complain? I would like (dream) to talk to someone who knows what a route is. This is Amazon EC2 data center in Singapore, other providers in SG show similar routes.

3 61.7.148.37 (61.7.148.37) 45.958 ms 47.951 ms 49.527 ms

4 202.47.247.193 (202.47.247.193) 51.982 ms 53.344 ms 54.655 ms

5 202.47.247.98 (202.47.247.98) 242.435 ms 242.624 ms 242.938 ms

6 61.19.15.193 (61.19.15.193) 72.370 ms 59.622 ms 64.923 ms

7 61.19.9.33 (61.19.9.33) 89.473 ms 89.847 ms 101.032 ms

8 61.19.9.30 (61.19.9.30) 106.087 ms 107.259 ms 108.208 ms

9 202.47.253.254 (202.47.253.254) 258.947 ms 259.519 ms 261.114 ms

10 203.131.245.25 (203.131.245.25) 212.806 ms 213.716 ms 215.701 ms

11 * * *

12 xe-1-0-0.r21.newthk02.hk.bb.gin.ntt.net (129.250.17.8) 290.453 ms xe-0-3-0.r21.newthk02.hk.bb.gin.ntt.net (129.250.17.10) 246.564 ms 206.104 ms

13 as-4.r20.tokyjp01.jp.bb.gin.ntt.net (129.250.3.194) 239.221 ms 240.177 ms 240.875 ms

14 ae-0.r22.tokyjp01.jp.bb.gin.ntt.net (129.250.5.149) 199.391 ms 201.284 ms 202.730 ms

15 as-1.r02.sngpsi02.sg.bb.gin.ntt.net (129.250.5.21) 280.907 ms 281.621 ms 282.724 ms

16 xe-0.amazon.sngpsi02.sg.bb.gin.ntt.net (129.250.11.210) 377.645 ms 382.536 ms 374.428 ms

17 203.83.223.2 (203.83.223.2) 425.336 ms 433.159 ms 420.956 ms

I think this a CAT or (their immediate routing providers) problem, as a reverse traceroute (http://tools.ix.singtel.com/traceroute) shows more sensible routes - although still a little high vs 6 months ago.

[mattcodes]

Just want to say that this issue is in the progress of being resolved. Presented with the right amount of information (traceroutes, AS details) CAT has acted extremely fast and professionally, and rectified the issue as much as I they can, I am impressed. Now I await for Amazon Singapore NOC to respond for the reverse route issues that remain.

[kudroz]

Thanks for acting on it. We've also moved our deployment to EC2 in Singapore and routing through Japan with a latency of 400ms is totally not the dream. I'm happy to report that with our leased line with kirz.com and our ADSL 3BB it routes directly to Singapore.

 1  192.168.1.254 (192.168.1.254)  0.000 ms  0.000 ms  0.000 ms
2  202.173.219.97 (202.173.219.97)  0.000 ms  0.000 ms  0.000 ms
3  202.173.219.253 (202.173.219.253)  20.000 ms  20.000 ms  20.000 ms
4  202.173.222.129 (202.173.222.129)  20.000 ms  50.000 ms  30.000 ms
5  202.173.222.249 (202.173.222.249)  20.000 ms  20.000 ms  20.000 ms
6  202.173.208.249 (202.173.208.249)  20.000 ms  20.000 ms  20.000 ms
7  TIG-Net28-189.trueinternetgateway.com (122.144.28.189)  20.000 ms  110.000 ms  20.000 ms
8  TH-ICR-TT1-26-129.trueinternetgateway.com (122.144.26.129)  60.000 ms  50.000 ms  80.000 ms
9  SG-ICR-ANC1-26-206.trueinternetgateway.com (122.144.26.206)  60.000 ms  60.000 ms  60.000 ms
10  if-0-0-5.core1.S9R-Singapore.as6453.net (209.58.82.133)  50.000 ms  50.000 ms  60.000 ms
11  if-10-0-0.core2.S9R-Singapore.as6453.net (209.58.82.46)  70.000 ms  60.000 ms  50.000 ms
12  Vlan1860.icore1.SVW-Singapore.as6453.net (209.58.96.14)  60.000 ms  50.000 ms  50.000 ms
13  Vlan43.icore1.S9U-Singapore.as6453.net (116.0.83.5)  60.000 ms  50.000 ms  50.000 ms
14  ix-6-3.icore1.S9U-Singapore.as6453.net (116.0.83.74)  60.000 ms ix-12-3.icore1.S9U-Singapore.as6453.net (116.0.83.70)  70.000 ms ix-6-3.icore1.S9U-Singapore.as6453.net (116.0.83.74)  60.000 ms
15  203.83.223.62 (203.83.223.62)  70.000 ms 203.83.223.60 (203.83.223.60)  70.000 ms  70.000 ms
16  203.83.223.2 (203.83.223.2)  60.000 ms  60.000 ms  60.000 ms

traceroute to 203.83.223.2 (203.83.223.2), 30 hops max, 40 byte packets
1  10.121.XXX.XXX (10.121.XXX.XXX)  20.000 ms  30.000 ms  30.000 ms
2  * * *
3  mx-ll-58.147.0-41.static.tttmaxnet.com (58.147.0.41)  30.000 ms  40.000 ms  40.000 ms
4  * * *
5  mx-ll-58.147.0-69.static.tttmaxnet.com (58.147.0.69)  30.000 ms  40.000 ms  40.000 ms
6  mx-ll-58.147.0-129.static.tttmaxnet.com (58.147.0.129)  70.000 ms  70.000 ms  70.000 ms
7  ge-2-1-5.r02.sngpsi02.sg.bb.gin.ntt.net (129.250.10.173)  70.000 ms  70.000 ms  70.000 ms
8  xe-0.amazon.sngpsi02.sg.bb.gin.ntt.net (129.250.11.210)  70.000 ms  70.000 ms  70.000 ms
9  203.83.223.2 (203.83.223.2)  70.000 ms  70.000 ms  70.000 ms

[mattcodes]

Yes,3BB/TT&T do seem to have better routes through Asia. CAT Hinet despite its hype does suffer some congestion even those the routes are now pretty much direct (reverse from Amazon goes through HK but better than JP, USA) - pings are volatile but not sure if they doing QoS and prioritising ICMP as low.

Initially impressions of EC2 are good, but not sure about embracing it yet. But at < $5 a month to park a Windows 2008 instance its bloody cheap.

[Upcountry]

kudroz,

I noticed that you saw a timeout between 10.121.... and mx-11.

Here's my traceroute to www.google.co.th. Notice the long timeouts between 10.121.65.210 and mx-ll-58.147.1-205.static.tttmaxnet.com.

I counted about 30 seconds as I watched it go, several times. I wonder if you and others have seen something similar. I did this test just after 3BB came down my street with new cable to upgrade speed capability. Theoretically, 2mb is now 3mb for the default Premier package, not that we see anything close to that.

1 <1 ms <1 ms <1 ms 192.168.1.1

2 27 ms 26 ms 414 ms 10.121.165.202

3 28 ms 27 ms 27 ms 10.121.65.210

4 * * * Request timed out.

5 * * * Request timed out.

6 34 ms 33 ms 34 ms mx-ll-58.147.1-205.static.tttmaxnet.com [58.147.1.205]

7 * * * Request timed out.

8 33 ms 33 ms 33 ms mx-ll-58.147.0-90.static.tttmaxnet.com [58.147.0.90]

9 33 ms 33 ms 33 ms mx-ll-58.147.0-66.static.tttmaxnet.com [58.147.0.66]

0 33 ms 33 ms 33 ms 218.100.47.246

1 33 ms 33 ms 33 ms 218.100.47.22

2 56 ms 64 ms 56 ms 72.14.217.193

3 57 ms 58 ms 58 ms 209.85.242.238

4 57 ms 58 ms 57 ms 209.85.242.236

5 133 ms 64 ms 80 ms 209.85.242.242

6 133 ms 134 ms 132 ms 209.85.254.155

7 219 ms 219 ms 217 ms 209.85.249.36

8 226 ms 224 ms 223 ms 216.239.43.228

9 227 ms 222 ms 226 ms 64.233.174.99

0 243 ms 220 ms 230 ms 216.239.46.6

1 221 ms 222 ms 222 ms pz-in-f147.1e100.net [74.125.127.147]

[kudroz]

Here's my traceroute to www.google.co.th. Notice the long timeouts between 10.121.65.210 and mx-ll-58.147.1-205.static.tttmaxnet.com. I counted about 30 seconds as I watched it go, several times. I wonder if you and others have seen something similar.

This generally means that those routers block certain or all UDP ports and ICMP echo request packets. UDP and ICMP are IP protocols used for traceroute. They block this for security reasons - to hide their network topology. This is very common.

I did this test just after 3BB came down my street with new cable to upgrade speed capability. Theoretically, 2mb is now 3mb for the default Premier package, not that we see anything close to that.

You should get your 3Mbps download for sites hosted in Thailand, Malaysia, Singapore, Hong Kong, and Taiwan because Thai ISPs have peering agreements with most SE Asian ISPs. If the sites are hosted in the US or Europe, it is expected that you will see about half-speed of what you pay in average. It depends of the international bandwidth contention ratio of the ISP. A typical Thai ISP may purchase 1Mbps of international bandwidth for each 100Mbps of ADSL they sell (1/100 contention ratio). 3BB Premier could have an international bandwidth contention rate of 1/50 versus 1/100 for 3BB indy packages (just speculating).

Edited May 23, 2010 by kudroz