Mcshane123
12-05-2007, 01:56
Hi, i've had the problem now of high pings to all Counter-strike gaming servers during peak/busy times for a few months, I've called Virgin/NTL customer services numerous times, and had a new modem fitted aswell as doing a fresh system format none of this has solved the problem.
I'd appreciate any help/advice at all anyone could give me.
This is the tracert i took @ 14:01 on 10th May
Tracing route to dustworld.net [193.238.84.189]
over a maximum of 30 hops:
1 5 ms 10 ms 20 ms 10.235.116.1
2 6 ms 11 ms 7 ms bagu-t2cam1-a-v123.inet.ntl.com [80.5.162.93]
3 8 ms 7 ms 7 ms bagu-t2core-a-ge-wan61.inet.ntl.com [195.182.175
.1]
4 7 ms 27 ms 18 ms man-bb-a-so-710-0.inet.ntl.com [213.105.174.69]
5 27 ms 8 ms 11 ms lee-bb-b-so-100-0.inet.ntl.com [62.253.185.194]
6 45 ms 41 ms 13 ms nth-bb-a-so-600-0.inet.ntl.com [213.105.175.133]
7 18 ms 18 ms 16 ms nth-bb-b-so-200-0.inet.ntl.com [213.105.172.194]
8 33 ms 36 ms 15 ms tele-ic-1-as0-0.inet.ntl.com [62.253.184.2]
9 16 ms 16 ms 15 ms 212.250.14.98
10 15 ms 23 ms 16 ms webserver1.dustworld.net [193.238.84.189]
Trace complete.
This is a tracert i took @ 20:52 on 10th May
Tracing route to dustworld.net [193.238.84.189]
over a maximum of 30 hops:
1 82 ms 42 ms 59 ms 10.235.116.1
2 39 ms 94 ms 40 ms bagu-t2cam1-a-v123.inet.ntl.com [80.5.162.93]
3 58 ms 59 ms 60 ms bagu-t2core-a-ge-wan61.inet.ntl.com [195.182.175
.1]
4 67 ms 61 ms * man-bb-a-so-710-0.inet.ntl.com [213.105.174.69]
5 * 39 ms 41 ms lee-bb-b-so-100-0.inet.ntl.com [62.253.185.194]
6 66 ms 74 ms 60 ms nth-bb-a-so-600-0.inet.ntl.com [213.105.175.133]
7 51 ms 46 ms 90 ms nth-bb-b-so-200-0.inet.ntl.com [213.105.172.194]
8 90 ms 75 ms 91 ms tele-ic-1-as0-0.inet.ntl.com [62.253.184.2]
9 85 ms 80 ms 58 ms 212.250.14.98
10 56 ms 85 ms 74 ms webserver1.dustworld.net [193.238.84.189]
As you can see the one i took earlier gave alot lower response times and is acceptable, where as the one took in peak time, is very unstable and quite high
Trace complete.
Thanks. Sean
I'd appreciate any help/advice at all anyone could give me.
This is the tracert i took @ 14:01 on 10th May
Tracing route to dustworld.net [193.238.84.189]
over a maximum of 30 hops:
1 5 ms 10 ms 20 ms 10.235.116.1
2 6 ms 11 ms 7 ms bagu-t2cam1-a-v123.inet.ntl.com [80.5.162.93]
3 8 ms 7 ms 7 ms bagu-t2core-a-ge-wan61.inet.ntl.com [195.182.175
.1]
4 7 ms 27 ms 18 ms man-bb-a-so-710-0.inet.ntl.com [213.105.174.69]
5 27 ms 8 ms 11 ms lee-bb-b-so-100-0.inet.ntl.com [62.253.185.194]
6 45 ms 41 ms 13 ms nth-bb-a-so-600-0.inet.ntl.com [213.105.175.133]
7 18 ms 18 ms 16 ms nth-bb-b-so-200-0.inet.ntl.com [213.105.172.194]
8 33 ms 36 ms 15 ms tele-ic-1-as0-0.inet.ntl.com [62.253.184.2]
9 16 ms 16 ms 15 ms 212.250.14.98
10 15 ms 23 ms 16 ms webserver1.dustworld.net [193.238.84.189]
Trace complete.
This is a tracert i took @ 20:52 on 10th May
Tracing route to dustworld.net [193.238.84.189]
over a maximum of 30 hops:
1 82 ms 42 ms 59 ms 10.235.116.1
2 39 ms 94 ms 40 ms bagu-t2cam1-a-v123.inet.ntl.com [80.5.162.93]
3 58 ms 59 ms 60 ms bagu-t2core-a-ge-wan61.inet.ntl.com [195.182.175
.1]
4 67 ms 61 ms * man-bb-a-so-710-0.inet.ntl.com [213.105.174.69]
5 * 39 ms 41 ms lee-bb-b-so-100-0.inet.ntl.com [62.253.185.194]
6 66 ms 74 ms 60 ms nth-bb-a-so-600-0.inet.ntl.com [213.105.175.133]
7 51 ms 46 ms 90 ms nth-bb-b-so-200-0.inet.ntl.com [213.105.172.194]
8 90 ms 75 ms 91 ms tele-ic-1-as0-0.inet.ntl.com [62.253.184.2]
9 85 ms 80 ms 58 ms 212.250.14.98
10 56 ms 85 ms 74 ms webserver1.dustworld.net [193.238.84.189]
As you can see the one i took earlier gave alot lower response times and is acceptable, where as the one took in peak time, is very unstable and quite high
Trace complete.
Thanks. Sean