High pings on cable but not on ADSL?

Toilet-Duck · 21-05-2006, 19:19

Im getting some really high pings on some of the Battlefield 1942 servers that I use to play on ADSL heres a tracert of one of them:

C:\>tracert 213.186.35.63

Tracing route to nateos.com [213.186.35.63]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.2.1
2 9 ms 7 ms 8 ms 10.157.164.1
3 9 ms 8 ms 9 ms midd-t2cam1-b-v110.inet.ntl.com [213.106.238.185
]
4 34 ms 36 ms 7 ms midd-t2core-b-ge-wan63.inet.ntl.com [213.106.237
.169]
5 13 ms 14 ms 13 ms ren-bb-b-so-220-0.inet.ntl.com [62.253.187.93]
6 14 ms 13 ms 12 ms ren-bb-a-ae0-0.inet.ntl.com [62.253.185.185]
7 25 ms 28 ms 24 ms bre-bb-b-so-110-0.inet.ntl.com [62.253.185.166]

8 24 ms 24 ms 23 ms bre-bb-a-ge-000-0.inet.ntl.com [213.105.174.225]

9 20 ms 21 ms 21 ms gfd-bb-b-so-700-0.inet.ntl.com [213.105.172.150]

10 25 ms 25 ms 23 ms redb-ic-1-as0-0.inet.ntl.com [213.105.174.138]
11 183 ms 360 ms 239 ms sw1.tc.lon [195.66.224.220]
12 177 ms 163 ms 162 ms p19-5-m1.routers.ovh.net [213.251.130.160]
13 * nateos.com [213.186.35.63] reports: Destination protocol unreacha
ble.

Trace complete.

Its all fine until it gets to point 11 any ideas on what is causing these high pings? Its still fine on my old ADSL which is getting deactivated soon:

C:\Documents and Settings\Administrator>tracert
213.186.35.63

Tracing route to nateos.com [213.186.35.63]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.0.1
2 45 ms 46 ms 45 ms
lo1-lon3-adsl20.nildram.net [195.112.5.29]
3 71 ms 46 ms 46 ms
ge-0-0-1.cr2.gs1.bb.pipex.net [84.12.224.21]
4 47 ms 45 ms 45 ms lon1-9.nildram.net
[84.12.224.14]
5 46 ms 45 ms 45 ms
g3-18.cr05.tn5.bb.pipex.net [62.72.141.37]
6 49 ms 46 ms 47 ms
v3952.cr05.hx2.bb.pipex.net [62.72.137.10]
7 47 ms 45 ms 46 ms linx2.teleglobe.net
[195.66.226.51]
8 56 ms 56 ms 55 ms
if-1-0.core2.LHX-London.Teleglobe.net [195.219.9
6.122]
9 56 ms 57 ms 57 ms
if-1-1.mcore3.LHX-London.teleglobe.net [195.219.
196.5]
10 55 ms 57 ms 55 ms
if-3-0.core1.PG1-Paris.teleglobe.net [80.231.72.
41]
11 56 ms 55 ms 54 ms
if-10-1.har1.PG1-Paris.teleglobe.net [80.231.72.
46]
12 54 ms 55 ms 55 ms 195.219.198.58
13 56 ms 54 ms 56 ms
th1-1-6k.routers.ovh.net [213.186.32.146]
14 55 ms 55 ms 54 ms
p19-5-m2.routers.ovh.net [213.251.130.161]
15 nateos.com [213.186.35.63] reports: Destination
protocol unreachable.

Trace complete.Any ideas please?

Efour · 21-05-2006, 21:28

well its a totaly different route to the destination so some companys switch is buggered on whatever route u have trouble with. will probably be fixed by 9am tommorow when somone can be bothered.

Toilet-Duck · 22-05-2006, 13:39

Quote:

Originally Posted by Efour

well its a totaly different route to the destination so some companys switch is buggered on whatever route u have trouble with. will probably be fixed by 9am tommorow when somone can be bothered.

Ah your right thanks its working now

Toilet-Duck · 24-05-2006, 22:56

Nope it still happening at around 10pm uk time my pings go insane, everyone elses pings on the server are normal and on my adsl connection still but huge pings on NTL...

Any ideas?

Heres another tracert:

C:\>tracert 213.186.35.63

Tracing route to nateos.com [213.186.35.63]
over a maximum of 30 hops:

1 2 ms <1 ms <1 ms 192.168.2.1
2 11 ms 27 ms 6 ms 10.157.164.1
3 8 ms 8 ms 8 ms midd-t2cam1-b-v110.inet.ntl.com [213.106.238.185
]
4 9 ms 8 ms 8 ms midd-t2core-b-ge-wan63.inet.ntl.com [213.106.237
.169]
5 15 ms 13 ms 12 ms ren-bb-b-so-220-0.inet.ntl.com [62.253.187.93]
6 16 ms 15 ms 15 ms ren-bb-a-ae0-0.inet.ntl.com [62.253.185.185]
7 23 ms 23 ms 24 ms bre-bb-b-so-110-0.inet.ntl.com [62.253.185.166]

8 26 ms 23 ms 24 ms bre-bb-a-ge-000-0.inet.ntl.com [213.105.174.225]

9 22 ms 20 ms 20 ms gfd-bb-b-so-700-0.inet.ntl.com [213.105.172.150]

10 22 ms 23 ms 23 ms redb-ic-1-as0-0.inet.ntl.com [213.105.174.138]
11 239 ms 208 ms * sw1.tc.lon [195.66.224.220]
12 149 ms 191 ms 171 ms p19-5-m1.routers.ovh.net [213.251.130.160]
13 nateos.com [213.186.35.63] reports: Destination protocol unreachable.

Trace complete.