Tracing to the IP you gave me earlier this week, FROM our server, I get:
9 so-2-1-0.bbr2.Washington1.Level3.net (209.244.11.13) 30.609 ms 30.586 ms so-2-1-0.bbr1.Washington1.Level3.net (209.244.11.9) 30.607 ms
10 as-0-0.bbr2.London1.Level3.net (4.68.128.105) 102.056 ms 147.613 ms 102.861 ms
11 ae-0-56.gar2.London1.Level3.net (4.68.116.172) 102.447 ms ae-0-54.gar2.London1.Level3.net (4.68.116.108) 102.060 ms ae-0-56.gar2.London1.Level3.net (4.68.116.172) 103.239 ms
12 195.50.91.70 (195.50.91.70) 102.448 ms 104.802 ms 111.524 ms
13 win-bb-b-so-500-0.inet.ntl.com (62.253.185.202) 105.225 ms 105.532 ms 120.706 ms
14 swan-t2core-b-pos31.inet.ntl.com (62.253.187.242) 174.965 ms 114.930 ms 108.957 ms
15 swan-t2cam1-b-ge-wan31.inet.ntl.com (213.105.225.146) 108.453 ms 108.936 ms 109.456 ms
16 swan-sket-ubr-1-ge20.inet.ntl.com (80.0.254.150) 110.471 ms 121.421 ms 109.318 ms
17 * * *
18 * * *
19 *
You should probably check with your provider and give them that tracerout - that's where it dies. If there's a bottleneck, its around hop 16/17
Joe
9 so-2-1-0.bbr2.Washington1.Level3.net (209.244.11.13) 30.609 ms 30.586 ms so-2-1-0.bbr1.Washington1.Level3.net (209.244.11.9) 30.607 ms
10 as-0-0.bbr2.London1.Level3.net (4.68.128.105) 102.056 ms 147.613 ms 102.861 ms
11 ae-0-56.gar2.London1.Level3.net (4.68.116.172) 102.447 ms ae-0-54.gar2.London1.Level3.net (4.68.116.108) 102.060 ms ae-0-56.gar2.London1.Level3.net (4.68.116.172) 103.239 ms
12 195.50.91.70 (195.50.91.70) 102.448 ms 104.802 ms 111.524 ms
13 win-bb-b-so-500-0.inet.ntl.com (62.253.185.202) 105.225 ms 105.532 ms 120.706 ms
14 swan-t2core-b-pos31.inet.ntl.com (62.253.187.242) 174.965 ms 114.930 ms 108.957 ms
15 swan-t2cam1-b-ge-wan31.inet.ntl.com (213.105.225.146) 108.453 ms 108.936 ms 109.456 ms
16 swan-sket-ubr-1-ge20.inet.ntl.com (80.0.254.150) 110.471 ms 121.421 ms 109.318 ms
17 * * *
18 * * *
19 *
You should probably check with your provider and give them that tracerout - that's where it dies. If there's a bottleneck, its around hop 16/17
Joe