On Tue, Jun 19, 2012 at 06:42:33PM -0400, Drew Weaver wrote:
> I have also noticed that traffic sourced in NYC destined for Qatar across NTT
> seems to now go from NYC -> SJC -> SNG and ends up being about 180+ms longer
> than just going over the atlantic.
I've seen some people in the middle east/africa purchase services
in Asia based on their business needs. In the case of NTT, this
is likely the case as they are a decent sized player in Asia.
> I've seen this a few times (only with NTT routes).
See below for some further insight....
> Thanks,
> -Drew
>
> -----Original Message-----
> From: Anurag Bhatia [mailto:[email protected]]
> Sent: Tuesday, June 19, 2012 4:15 PM
> To: NANOG Mailing List
> Subject: NTT handing packets to Reliance (Flag Telecom) in California for
> BSNL block
>
> Hello everyone,
>
>
> I was trying to understand reason for high latency between my BSNL (AS9829)
> connection and a specific Germany based server on M-Online.
>
>
> I can see forward path is correct but reverse path is:
>
>
> traceroute to 117.200.57.47 (117.200.57.X), 30 hops max, 60 byte packets
> ...
> 13 xe-0-1-0-10.r04.lsanca03.us.ce.gin.ntt.net (198.172.90.222) [AS2914]
> 183.765 ms 183.748 ms 185.719 ms
.CE.GIN.NTT.NET is customer equipment. It appears they are
preferring their customer route.
> I can see from Reliance's Looking glass that there direct path from EU to
> India on their network. I wonder why exactly NTT handling off packets to
> Reliance in California? The problem seems only for BSNL block -
> 117.200.48.0/20.
It is going to their customer.
> If destination is not BSNL and say Reliance itself...say for Monster.co.inweb
> server which is in Reliance datacenter:
>
>
>
> *Query Results:*
> *Router: *Amsterdam - NL
> *Command:* traceroute 220.226.205.30
>
> *Disclaimer: Traceroute is a useful tool for determining the route a packet
> takes, but it should not be used as an accurate measure of network
> performance. For more information please view the Traceroute
> Disclaimer<https://ssp.pme.gin.ntt.net/lg/trDisclaimer.html>
> .*
>
>
> traceroute to 220.226.205.30 (220.226.205.30), 30 hops max, 40 byte packets
> 1 as-0.r22.amstnl02.nl.bb.gin.ntt.net (129.250.2.118) 15.806 ms
> 0.746 ms 0.718 ms
> MPLS Label=499040 CoS=0 TTL=1 S=0
> MPLS Label=304400 CoS=0 TTL=1 S=1
> 2 ae-5.r23.londen03.uk.bb.gin.ntt.net (129.250.5.197) 8.180 ms
> 7.740 ms 8.770 ms
> MPLS Label=304400 CoS=0 TTL=1 S=1
> 3 ae-2.r02.londen03.uk.bb.gin.ntt.net (129.250.5.41) 16.229 ms
> 15.829 ms 16.326 ms
> 4 flagtelecom-0.r02.londen03.uk.bb.gin.ntt.net (83.231.235.238)
> 15.059 ms 16.032 ms 7.014 ms
> 5 62.216.128.106 (62.216.128.106) 8.332 ms 62.216.128.122
> (62.216.128.122) 32.306 ms ge-0-0-3.0.cjr02.ldn004.flagtel.com
> (62.216.128.138) 9.051 ms
> MPLS Label=412816 CoS=0 TTL=1 S=1
> 6 so-1-0-0.0.pjr02.ldn001.flagtel.com (85.95.25.9) 8.616 ms
> so-1-0-0.0.pjr01.ldn001.flagtel.com (85.95.25.13) 19.806 ms
> ge-0-1-0.0.pjr01.ldn001.flagtel.com (62.216.129.137) 8.059 ms
> MPLS Label=300480 CoS=0 TTL=1 S=1
> 7 so-4-0-0.0.pjr01.mmb004.flagtel.com (85.95.25.113) 280.327 ms
> so-1-0-0.0.pjr02.mmb004.flagtel.com (85.95.25.138) 281.659 ms
> so-3-1-0.0-pjr02.mmb004-flagtel.com (85.95.26.158) 282.889 ms
> 8 62.216.147.138 (62.216.147.138) 285.101 ms 695.643 ms
> 62.216.147.46 (62.216.147.46) 278.537 ms
>
>
>
> Pretty much direct.
>
>
> I wonder what exactly is different/wrong in case of BSNL block
> 117.200.48.0/20? Is BSNL selectively announcing it only from Reliance's
> California based router and not any other router in Europe?
>
> Can somehow one can test & confirm the above guess of selective announcement?
>
>
>
> (*Apologize if I missed some fundamental glitch error. I am new to it.*)
I've seen cases where the packet goes around the world based
on the networks involved. You can usually tell due to increased
latency or looking at ping -R output.
- Jared
--
Jared Mauch | pgp key available via finger from [email protected]
clue++; | http://puck.nether.net/~jared/ My statements are only mine.
