[172584] in North American Network Operators' Group
RE: Help with route latency between TATA and Comcast
daemon@ATHENA.MIT.EDU (Edward Arthurs)
Tue Jun 24 14:57:43 2014
X-Original-To: nanog@nanog.org
From: "Edward Arthurs" <earthurs@legacyinmate.com>
To: <nanog@nanog.org>
In-Reply-To: <web-163783@mail.ropeguru.com>
Date: Tue, 24 Jun 2014 11:48:36 -0700
Errors-To: nanog-bounces@nanog.org
Here is what I get from a trace route, I am in Los Angeles.
Tracing route to 128.199.162.241 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms 172.25.0.137
2 14 ms 16 ms 14 ms 208.179.145.213
3 7 ms 5 ms 6 ms cr01.lax1.tierzero.net [216.31.153.48]
4 7 ms 6 ms 6 ms ge-0-1-2.br02.lax3.tierzero.net =
[216.31.128.73]
5 7 ms 7 ms 45 ms xe-7-1-2.edge6.LosAngeles1.Level3.net =
[4.59.57.157]
6 6 ms 6 ms 6 ms ae-1-60.edge3.LosAngeles1.Level3.net =
[4.69.144.9]
7 8 ms 7 ms 8 ms =
xe-0-3-0-5.r04.lsanca03.us.bb.gin.ntt.net [129.250.9.229]
8 8 ms 8 ms 8 ms ae-8.r20.lsanca03.us.bb.gin.ntt.net =
[129.250.5.1]
9 116 ms 123 ms 117 ms ae-6.r20.osakjp02.jp.bb.gin.ntt.net =
[129.250.4.39]
10 117 ms 117 ms 117 ms ae-4.r22.osakjp02.jp.bb.gin.ntt.net =
[129.250.6.188]
11 204 ms 223 ms 208 ms ae-8.r20.sngpsi05.sg.bb.gin.ntt.net =
[129.250.3.110]
12 200 ms 192 ms 191 ms ae-2.r00.sngpsi02.sg.bb.gin.ntt.net =
[129.250.3.147]
13 181 ms 184 ms 182 ms 116.51.27.190 APNIC
14 179 ms 180 ms 179 ms 103.253.144.242 APNIC
15 * * * Request timed out.
16 188 ms 188 ms 194 ms 128.199.162.241 digitalocean.com
Trace complete.
Thank You
-----Original Message-----
From: NANOG [mailto:nanog-bounces@nanog.org] On Behalf Of =
rwebb@ropeguru.com
Sent: Tuesday, June 24, 2014 11:26 AM
To: Matthew Petach
Cc: nanog@nanog.org
Subject: Re: Help with route latency between TATA and Comcast
Now that I look at it again, I believe you are correct. This is my first =
overseas server so I was not really sure what to expect in latency.
It has been one of those days that doing a reverse had not occurred to =
me to try as suggested by another reply. I am seeing about the same on =
the reverse so I am good to go.
Robert
On Tue, 24 Jun 2014 11:18:09 -0700
Matthew Petach <mpetach@netflight.com> wrote:
> 260ms from VA to SG is about right. I'd suspect the DNS is wrong in=20
> this case, as otherwise they somehow went from LAX to SG in less than=20
> 10ms--and if they found a way to do that, I suspect they'd have a=20
> *lot* more customers beating down their doors to get onto that=20
> pathway. :P
>=20
> Matt
>=20
>=20
>=20
> On Tue, Jun 24, 2014 at 10:49 AM, rwebb@ropeguru.com=20
><rwebb@ropeguru.com>
> wrote:
>=20
>> I am doing some testing between my Comcast Business connection and a =
>>Singapore server that I have just setup. I am seeing high latency to=20
>>the server but it appears it is the Comcast to TATA link and not the=20
>>link between the U.S. and Singapore. At least that is what I can=20
>>gather from the reverse lookup in the traceroute.
>>
>> Can someone please enlighten me as to if I am correct or not?
>>
>> Tracing route to 128.199.162.241 over a maximum of 30 hops
>>
>> 1 <1 ms <1 ms <1 ms 192.168.1.254
>> 2 1 ms <1 ms <1 ms 23-25-112-190-static.hfc.
>> comcastbusiness.net [23.25.xxx.xxx]
>> 3 27 ms 22 ms 19 ms 96.178.10.1
>> 4 10 ms 9 ms 10 ms te-1-3-ur01.shadygrove.va.
>> richmond.comcast.net [68.86.124.241]
>> 5 17 ms 17 ms 17 ms xe-12-0-1-0-ar02.charlvilleco.
>> va.richmond.comcast.net [68.86.172.17]
>> 6 24 ms 24 ms 25 ms pos-1-2-0-0-cr01.ashburn.va.
>> ibone.comcast.net [68.86.91.53]
>> 7 24 ms 23 ms 23 ms pos-0-3-0-0-pe01.ashburn.va.
>> ibone.comcast.net [68.86.86.142]
>> 8 20 ms 20 ms 20 ms 66.208.233.38
>> 9 268 ms 264 ms 265 ms=20
>>if-6-8.tcore2.lvw-los-angeles.as6453.net
>> [216.6.87.114]
>> 10 * * * Request timed out.
>> 11 270 ms 255 ms 256 ms=20
>>if-2-2.tcore1.svw-singapore.as6453.net
>> [180.87.12.1]
>> 12 270 ms 271 ms 275 ms=20
>>if-11-2.thar1.svq-singapore.as6453.net
>> [180.87.98.37]
>> 13 260 ms 258 ms 260 ms 180.87.98.6
>> 14 256 ms 256 ms 258 ms 103.253.144.242
>> 15 262 ms 258 ms 259 ms 128.199.162.241
>>
>> Trace complete.?
>>
>>
