Ping Problems
 

I am using Ntl 600k to play xbox live and ps2 online i connect through a wireless router till saturday i have bene having no problems with my pings being at 110 on ps2 online in a eupean server this is normal for connection through a wireless router but on saturday my pings have got as high as 250 and havent been below 180 i thought this could be a router problem so i tried connecting directly to ps2 online with ntl but with the same problem high pings. Is this a problem at the ntl end and should i contact them or is it a problem my end?

Anyhelp would be appreciated

Thanks

Re: Ping Problems
 

hiya

can you provide us with a traceroute report to the server you are connecting to?

Re: Ping Problems
 

i have a even worser problem for my PC online gaming
i play UT2k3 and my ping shoots straight up thru the roof
if i look at my ping status (via in-game) its says its 1000+ sometimes over 30k
im seeing that my out-going have bad packet lost and in-coming seems fine
this started to happen a week ago
i want to phone customer support but server status page says:

"Our Internet support centres will have no access to their systems during this period, normal service will be restored on the morning of 3rd December"

so i think ill have to wait till wednesday

also may i ask how do i copy a text report of traceroute??
i dont know many commands in command prompt

Re: Ping Problems
 

I had the same problems for ages, then suddenly after the dns
server problem which happend last week was sorted everything is
fine now.

My counter strike pings used to jump up to 2000+

Re: Ping Problems
 

does any1 know what NTL r doing to thier system??
http://www.ntl-isp.ntl.com/lookup/de...ovember&y=2003

does this have anything to do with my ping spikes??

Re: Ping Problems
 

in a windows session select the relevant text & choose 'copy' 'paste'?

in a dos session do summat like "tracert 'path' > C:\trace.txt"

Re: Ping Problems
 

In a dos session click on the c:\ logo in the top right of the window and select edit-mark. Highlight the text then press enter. The text is now in your clipboard, paste into the forum post and there you go :)


They are migrating their billing and customer management systems to a newer version of harmony/sabs. It gives the techs on the phones a better system to be able to handle your calls. Honestly its does i've seen the system its way easier.

Re: Ping Problems
 

thanks for the quick answers guys

this is a traceroute to a gameservers.net server

Tracing route to 62-212-74-82.gameservers.net [62.212.74.82]
over a maximum of 30 hops:

1 * * * Request timed out.
2 11 ms 30 ms 23 ms pool-t2cam1-b-ge92.inet.ntl.com [80.5.168.129]
3 13 ms 59 ms 164 ms sot3-t2core-b-pos71.inet.ntl.com [80.4.225.137]

4 35 ms 41 ms 14 ms gfd-bb-b-so-330-0.inet.ntl.com [62.253.185.53]
5 13 ms 17 ms 12 ms gfd-bb-a-ae0-0.inet.ntl.com [213.105.172.5]
6 11 ms 27 ms 18 ms pop-bb-b-so-000-0.inet.ntl.com [213.105.172.138]

7 31 ms 10 ms 15 ms pop-bb-a-ae0-0.inet.ntl.com [213.105.172.78]
8 19 ms 21 ms 22 ms amst-ic-1-so-000-0.inet.ntl.com [62.253.188.94]

9 35 ms 28 ms 46 ms ams-ix.leaseweb.nl [195.69.144.215]
10 140 ms 42 ms 63 ms 62-212-74-82.gameservers.net [62.212.74.82]

Trace complete.

C:\>tracert 62.212.74.82

Tracing route to 62-212-74-82.gameservers.net [62.212.74.82]
over a maximum of 30 hops:

1 * * * Request timed out.
2 130 ms 139 ms 129 ms pool-t2cam1-b-ge92.inet.ntl.com [80.5.168.129]
3 11 ms 52 ms 13 ms sot3-t2core-b-pos71.inet.ntl.com [80.4.225.137]

4 72 ms 15 ms 88 ms gfd-bb-b-so-330-0.inet.ntl.com [62.253.185.53]
5 14 ms 20 ms 9 ms gfd-bb-a-ae0-0.inet.ntl.com [213.105.172.5]
6 87 ms 11 ms 16 ms pop-bb-b-so-000-0.inet.ntl.com [213.105.172.138]

7 19 ms 10 ms 9 ms pop-bb-a-ae0-0.inet.ntl.com [213.105.172.78]
8 47 ms 71 ms 26 ms amst-ic-1-so-000-0.inet.ntl.com [62.253.188.94]

9 65 ms 40 ms 42 ms ams-ix.leaseweb.nl [195.69.144.215]
10 34 ms 28 ms 74 ms 62-212-74-82.gameservers.net [62.212.74.82]

Trace complete.

C:\>tracert 62.212.74.82

Tracing route to 62-212-74-82.gameservers.net [62.212.74.82]
over a maximum of 30 hops:

1 * * * Request timed out.
2 232 ms 124 ms 17 ms pool-t2cam1-b-ge92.inet.ntl.com [80.5.168.129]
3 16 ms 18 ms 9 ms sot3-t2core-b-pos71.inet.ntl.com [80.4.225.137]

4 11 ms 18 ms 14 ms gfd-bb-b-so-330-0.inet.ntl.com [62.253.185.53]
5 78 ms 121 ms 163 ms gfd-bb-a-ae0-0.inet.ntl.com [213.105.172.5]
6 153 ms 203 ms 79 ms pop-bb-b-so-000-0.inet.ntl.com [213.105.172.138]

7 235 ms 182 ms 201 ms pop-bb-a-ae0-0.inet.ntl.com [213.105.172.78]
8 273 ms 243 ms 283 ms amst-ic-1-so-000-0.inet.ntl.com [62.253.188.94]

9 25 ms 74 ms 117 ms ams-ix.leaseweb.nl [195.69.144.215]
10 147 ms 83 ms 81 ms 62-212-74-82.gameservers.net [62.212.74.82]

did it 3 times
this looks like a NTL problem right???

Re: Ping Problems
 

Here are my traceroute test results

Section 1: General Ping Results
A Ping test is the time taken for a server to reply to a request

ntl:World Server:
31ms - Normal - it's about right!

UK Server 1 (www.demon.net):
0ms - *** PING timed out ***
Tracert to specified location:

Tracing route to 194.159.254.213 over a maximum of 20 hops
1 24 ms 26 ms 45 ms 10.153.55.254
2 59 ms 28 ms 18 ms 80.4.46.73
3 13 ms 23 ms 15 ms 80.1.79.57
4 17 ms 22 ms * 62.253.185.33
5 23 ms 19 ms 20 ms 62.253.185.238
6 24 ms 46 ms 29 ms 62.253.185.82
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
Trace complete.


UK Server 2 (www.bbc.co.uk):
36ms - Normal - it's about right!

UK Server 3 (www.ic24.net):
32ms - Normal - it's about right!

USA East Coast Server (www.yahoo.com):
0ms - *** PING timed out ***
Tracert to specified location:

Tracing route to 64.58.76.176 over a maximum of 20 hops
1 7 ms 14 ms 17 ms 10.153.55.254
2 32 ms 17 ms 10 ms 80.4.46.205
3 16 ms 25 ms 51 ms 80.1.79.185
4 20 ms 13 ms 26 ms 62.253.188.37
5 15 ms 13 ms 13 ms 62.253.185.106
6 30 ms 57 ms 31 ms 62.253.185.134
7 31 ms 51 ms 16 ms 62.253.187.177
8 62 ms 22 ms 26 ms 208.175.252.89
9 38 ms 22 ms 21 ms 166.63.209.201
10 102 ms 101 ms 102 ms 206.24.226.99
11 206.24.238.38 reports: Destination host unreachable.
Trace complete.


USA West Coast Server (www.lycos.com):
102ms - Fast - very fast response

European Server (www.marcopoly.com):
45ms - Better than average - very quick response

Blueyonder Counter-Strike 1:
0ms - *** PING timed out ***
Tracert to specified location:

Tracing route to 194.117.138.249 over a maximum of 20 hops
1 15 ms 23 ms 25 ms 10.153.55.254
2 36 ms 22 ms 24 ms 80.4.46.73
3 12 ms 25 ms 27 ms 80.1.79.57
4 19 ms 17 ms 16 ms 62.253.185.33
5 22 ms 22 ms 19 ms 62.253.185.238
6 21 ms 56 ms 37 ms 62.253.185.82
7 194.117.147.69 reports: Destination host unreachable.
Trace complete.


Blueyonder Team-Fortress Leage 1:
0ms - *** PING timed out ***
Tracert to specified location:

Tracing route to 194.117.138.225 over a maximum of 20 hops
1 26 ms 14 ms 53 ms 10.153.55.254
2 55 ms 28 ms 16 ms 80.4.46.73
3 64 ms 59 ms 13 ms 80.1.79.61
4 61 ms 21 ms 29 ms 62.253.188.33
5 18 ms 40 ms 38 ms 62.253.185.238
6 23 ms 22 ms 23 ms 62.253.185.82
7 194.117.147.69 reports: Destination host unreachable.
Trace complete.


BarrysWorld Master Server (all games):
0ms - *** PING timed out ***
Tracert to specified location:

Tracing route to 213.221.174.165 over a maximum of 20 hops
1 45 ms 9 ms 11 ms 10.153.55.254
2 49 ms 64 ms * 80.4.46.205
3 54 ms 25 ms 13 ms 80.1.79.89
4 11 ms 9 ms 19 ms 62.253.188.37
5 14 ms 16 ms 13 ms 62.253.185.117
6 35 ms 15 ms 13 ms 62.253.185.98
7 83 ms 43 ms 36 ms 213.105.172.5
8 21 ms 20 ms 21 ms 62.253.185.78
9 20 ms 30 ms 39 ms 212.250.14.14
10 19 ms 20 ms 21 ms 213.221.179.115
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
Trace complete.


Japanese Ping Server (VERY long distance!):
0ms - *** PING timed out ***
Tracert to specified location:

Tracing route to 211.13.208.202 over a maximum of 20 hops
1 9 ms 32 ms 9 ms 10.153.55.254
2 25 ms 20 ms 64 ms 80.4.46.205
3 10 ms 11 ms 65 ms 80.1.79.89
4 92 ms 14 ms 48 ms 62.253.188.37
5 62 ms 11 ms 62 ms 62.253.185.117
6 19 ms 16 ms 15 ms 62.253.185.98
7 38 ms 53 ms 19 ms 213.105.172.5
8 77 ms 19 ms 19 ms 62.253.185.78
9 25 ms 23 ms 21 ms 195.66.224.105
10 170 ms 186 ms 178 ms 64.200.87.61
11 165 ms 233 ms 161 ms 64.200.240.46
12 165 ms 173 ms 195 ms 64.200.240.29
13 163 ms 201 ms 166 ms 64.200.210.122
14 182 ms 174 ms 219 ms 64.200.150.90
15 264 ms 214 ms 194 ms 203.181.104.81
16 281 ms 304 ms 286 ms 203.181.100.1
17 284 ms 282 ms 299 ms 203.181.96.118
18 289 ms 287 ms 294 ms 202.239.171.142
19 312 ms 262 ms 261 ms 210.155.132.82
20 * * * Request timed out.
Trace complete.

Could any one please tell me if thye are normal or bad etc

Re: Ping Problems
 

That's a lot of traces so I only scanned them quickly - unless someone can see something I missed then apart from the Japan one, none look particularly bad.