Here's my tracert to one of our LT servers (goes a bit weird inside the savvis dc, suspect some firewalls are blocking pings or have them on low priority).
I generally manage about 200-400KB/s per thread from LT.
C:\WINDOWS>tracert lt.mrgigabit.com
Tracing route to lt.mrgigabit.com [72.232.60.213]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms router2 [10.0.0.252]
2 34 ms 7 ms 10 ms nott-grim-ubr-1-ge20.inet.ntl.com [10.189.223.254]
3 15 ms 8 ms 11 ms nott-t2cam1-b-v128.inet.ntl.com [80.4.47.225]
4 14 ms 10 ms 17 ms nott-t2core-b-ge-wan74.inet.ntl.com [80.1.79.201]
5 13 ms 12 ms 12 ms nth-bb-b-so-300-0.inet.ntl.com [62.253.188.37]
6 20 ms 12 ms 11 ms nth-bb-a-ae0-0.inet.ntl.com [62.253.185.117]
7 39 ms 33 ms 21 ms so-0-3-2-0.loncr4.london.opentransit.net [193.251.254.141]
8 16 ms 25 ms 18 ms po3-0.loncr3.london.opentransit.net [193.251.242.217]
9 41 ms 17 ms 29 ms so-6-0-0-0.loncr1.london.opentransit.net [193.251.242.170]
10 16 ms 17 ms 16 ms bcr2-so-4-0-0.londonlnx.savvis.net [206.24.169.157]
11 18 ms 15 ms 17 ms bcs1-so-2-1-0.londonlnx.savvis.net [204.70.193.118]
12 90 ms 19 ms 88 ms bcs2-so-0-0-0.newyork.savvis.net [204.70.192.121]
13 90 ms 87 ms 92 ms bcs2-so-4-0-0.washington.savvis.net [204.70.192.1]
14 101 ms 114 ms 122 ms dcr2-so-7-2-0.atlanta.savvis.net [204.70.192.57]
15 113 ms 128 ms 105 ms dcr2-so-7-2-0.atlanta.savvis.net [204.70.192.57]
16 128 ms 125 ms 146 ms bcs2-so-2-0-0.dallas.savvis.net [204.70.192.70]
17 138 ms 126 ms 125 ms bcs1-so-6-0-0.dallas.savvis.net [204.70.192.49]
18 127 ms 128 ms 128 ms ohr1-pos-4-0.fortworthda1.savvis.net [208.172.131.82]
19 138 ms 435 ms 131 ms 216.39.81.34
20 126 ms 125 ms * 216.39.81.34
21 * * * Request timed out.
22 * * * Request timed out.
and back:
Tracing route to "my house in grimsby
" over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 209.60.232.72.reverse.layeredtech.com [72.232.60.209]
2 <1 ms <1 ms <1 ms 10.1.6.29
3 <1 ms <1 ms <1 ms 216.39.66.29
4 <1 ms <1 ms <1 ms 216.39.64.9
5 1 ms 1 ms 1 ms bcs2-so-3-2-0.Dallas.savvis.net [208.172.131.85]
6 41 ms 26 ms 21 ms dcr2-so-6-0-0.Atlanta.savvis.net [204.70.192.69]
7 35 ms 35 ms 35 ms bcs2-so-1-2-0.Washington.savvis.net [204.70.192.62]
8 39 ms 39 ms 39 ms bcs2-so-2-0-0.NewYork.savvis.net [204.70.192.2]
9 38 ms 39 ms 39 ms P5-0.NYKCR2.New-york.opentransit.net [206.24.207.30]
10 39 ms 40 ms 39 ms po10-0.nykcr3.NewYork.opentransit.net [193.251.241.114]
11 110 ms 110 ms 110 ms po4-0.loncr3.London.opentransit.net [193.251.243.22]
12 113 ms 113 ms 113 ms po0-0.brsbb1.Bristol.opentransit.net [193.251.243.38]
13 115 ms 115 ms 115 ms ntl.GW.opentransit.net [193.251.254.146]
14 113 ms 113 ms 113 ms pop-bb-a-so-010-0.inet.ntl.com [62.253.185.201]
15 115 ms 115 ms 115 ms nth-bb-b-so-400-0.inet.ntl.com [213.105.172.13]
16 117 ms 117 ms 117 ms nott-t2core-b-pos31.inet.ntl.com [62.253.185.38]
17 233 ms 133 ms 117 ms nott-t2cam1-b-ge-wan41.inet.ntl.com [80.1.79.166]
18 120 ms 119 ms 127 ms nott-grim-ubr-1-ge20.inet.ntl.com [80.4.47.226]
19 129 ms 134 ms 178 ms my house [hidden]
But in NTLs defense, they have great peering into some of the German datacenters. Can pull 10mbit on a single thread! Guess that's because they have part of their network in germany too
Feel free to run remote tracerts from any of our servers from
www.mrgigabit.com/network.php