Help with route latency between TATA and Comcast

Tue Jun 24 18:18:09 UTC 2014

260ms from VA to SG is about right.  I'd suspect
the DNS is wrong in this case, as otherwise
they somehow went from LAX to SG in less
than 10ms--and if they found a way to do that,
I suspect they'd have a *lot* more customers
beating down their doors to get onto that pathway.  :P

Matt

On Tue, Jun 24, 2014 at 10:49 AM, rwebb at ropeguru.com <rwebb at ropeguru.com>
wrote:

> 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 the
> server but it appears it is the Comcast to TATA link and not the link
> between the U.S. and Singapore. At least that is what I can 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 if-6-8.tcore2.lvw-los-angeles.as6453.net
> [216.6.87.114]
>  10     *        *        *     Request timed out.
>  11   270 ms   255 ms   256 ms if-2-2.tcore1.svw-singapore.as6453.net
> [180.87.12.1]
>  12   270 ms   271 ms   275 ms 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.?
>
>