Re: Bad connection Nottingham
 

DrAwesome transparent cache will do nothing to the ping times. Pings/trace's are ICMP requests and not get effected by cache servers

Re: Bad connection Nottingham
 

A quick check without typing tracert (what ever) in a dos prompt here 2 sample Unix traceroutes between the Giganews servers and your current location if it helps those that are lazy.

my connection during the day

news-40.giganews.com
1 330.ge-4-2-0.mpr2.iah1.us.above.net (64.125.104.19) 0.857 ms 0.676 ms 0.594 ms
2 pos-0-0.er1.atl4.us.above.net (64.125.29.69) 13.480 ms 13.379 ms 13.409 ms
3 pos12-0.pr1.atl4.us.above.net (64.125.30.234) 13.408 ms 13.243 ms 13.263 ms
4 so-5-3-0.cr1.dca2.us.mfnx.net (208.184.232.49) 24.601 ms 24.587 ms 24.565 ms
5 so-6-0-0.cr1.lhr3.uk.above.net (64.125.31.185) 96.626 ms 96.438 ms 96.424 ms
6 pop-bb-b-so-330-0.inet.ntl.com (208.185.188.42) 96.496 ms 96.378 ms 96.372 ms
7 lee-bb-a-so-700-0.inet.ntl.com (62.253.185.237) 101.947 ms 101.843 ms 101.903 ms
8 midd-t2core-a-pos31.inet.ntl.com (62.253.187.90) 103.400 ms 103.247 ms 103.329 ms
9 cache8-midd.server.ntli.net () 109.268 ms 109.136 ms 109.124 ms

news-60.giganews.com
1 gw1-vlan201.ash.giganews.com (216.196.98.2) 26 ms 38 ms 2 ms
2 g3-2.gw1.ash.giganews.com (64.200.88.101) 0 ms 0 ms 0 ms
3 hrndva1wcx2-pos0-0.wcg.net (64.200.89.49) 79 ms 79 ms 79 ms
4 nycmny2wcx2-oc48.wcg.net (64.200.240.45) 7 ms 7 ms 7 ms
5 lndnuk1lcx1-oc12.wcg.net (64.200.87.150) 78 ms 78 ms 78 ms
6 linx-gw2.router.ntli.net (195.66.226.22) 78 ms 79 ms 79 ms
7 pop-bb-b-so-430-0.inet.ntl.com (62.253.185.81) 78 ms 78 ms 78 ms
8 lee-bb-a-so-700-0.inet.ntl.com (62.253.185.237) 84 ms 83 ms 83 ms
9 midd-t2core-a-pos31.inet.ntl.com (62.253.187.90) 85 ms 85 ms 85 ms
10 cache8-midd.server.ntli.net () 91 ms 91 ms 91 ms

Re: Bad connection Nottingham
 

Does anybody know if this problem is resolved yet? I am actually getting fine pings ingame BUT it is rather shaky, with high pings sometimes, quite unstable.
As with tracerts, 1 second the ping to the t2core thing is like 600 and the next its sub 100.

Was wondering if it was resolved yet as i dunno what to make of it, and i wouldnt want to assume because i know ntl are rather random with their problems =/

Re: Bad connection Nottingham
 

DrAwesome, return path trace routes, ie from someone else to you do not take the same path as ones from you. As you will notice there are only 4 ntl servers there and one of them is the cache server. It wont give a reliable representation of what is happening.

If you wan to use a web based package to test server responce times use Visual Route (http://visualroute.visualware.co.uk/)