Re: www.google.com latency/packet loss/very slow thru savvis

[Richard A Steenbergen <ras () e-gerbil net>]

On Tue, Dec 13, 2005 at 03:46:43PM -0600, Erik Sundberg wrote:
> hey is any one seeing a slow google to day... packet loss 22 hops...
>
> visual traceroute show that it goes from chicago to los angeles to singapore
> to italy to amsterdam and then finally to google in sunnyvale ca.
...yadayadayada...
>  8  singapore-telecommunications-ltd.LosAngelesEquinix.savvis.net
> (208.174.196.6)  64.209 ms  62.281 ms  62.374 ms
>  9  laxeq-cr1.ge-3-0-0.ix.singtel.com (203.208.182.45)  62.767 ms
> ge-0-3-0.laxeq-cr1.ix.singtel.com (203.208.168.221)  62.958 ms  62.604 ms
>      MPLS Label=126512 CoS=0 TTL=1 S=1
> 10  so-3-3-2.sngc3-cr1.ix.singtel.com (203.208.154.25)  227.841 ms  225.874
> ms  226.254 ms
>      MPLS Label=100288 CoS=0 TTL=1 S=1
> 11  ge-1-0-0.sngc3-ar2.ix.singtel.com (203.208.172.158)  232.373 ms
> ge-0-0-0.sngc3-ar2.ix.singtel.com (203.208.172.166)  232.503 ms  239.240 ms
> 12  203.208.147.238 (203.208.147.238)  424.056 ms *  429.784 ms
> 13  pal6-pakistan-telecom-1-pk.pal.seabone.net (195.22.197.193)  477.452 ms
> 478.886 ms *
> 14  amsix-ams2-racc1.ams.seabone.net (195.22.213.221)  483.282 ms  491.266
> ms  480.559 ms
> 15  core1.ams.net.google.com (195.69.144.247)  448.393 ms  442.054 ms
> 435.464 ms

You'd be better off with an AS-PATH, but just follow the chain... Savvis 
-> Singtel -> Pakistan Telecom -> Seabone -> Google. Where I'm from, we 
call that a routing leak. Doesn't take too much work to guess where 
either. :)

-- 
Richard A Steenbergen <ras () e-gerbil net>       http://www.e-gerbil.net/ras
GPG Key ID: 0xF8B12CBC (7535 7F59 8204 ED1F CC1C 53AF 4C41 5ECA F8B1 2CBC)