Erratic pings

anz1066 · Jan 27, 2008, 21:05:21

my service has been pretty bad recently, i think since the maintenence was done, my ping is very erratic. the server i play in is in Holland and i normally have a ping of 50. now it is all over the place and i am lagging. any ideas as to why, and is it going to settle down?

362.9kilobits per second
44.3kilobytes per second
46.141seconds
9:01 PM Sun Jan 27, 2008

56k modem      56
256k DSL      256
512k DSL      512
1Mb DSL/Cable      1024
2Mb DSL/Cable      2048
4Mb DSL/Cable      4096
8Mb DSL/Cable      8192
You      1895
Results   7816 kbits downloaded in 4.125 sec
this is a uk speedtest

Sebby · Jan 27, 2008, 21:08:31

I think maybe you should start a new thread as there must be something wrong. Other than that night where a number of users experienced poor speeds, there are no issues that I know of.

Simon · Jan 27, 2008, 21:42:29

No sooner said, Seb.

Sebby · Jan 27, 2008, 22:37:30

Quote from: Simon on Jan 27, 2008, 21:42:29
No sooner said, Seb.

You're so efficient.

Sebby · Jan 27, 2008, 22:38:07

Quote from: anz1066 on Jan 27, 2008, 21:05:21
my service has been pretty bad recently, i think since the maintenence was done, my ping is very erratic. the server i play in is in Holland and i normally have a ping of 50. now it is all over the place and i am lagging. any ideas as to why, and is it going to settle down?

362.9kilobits per second
44.3kilobytes per second
46.141seconds
9:01 PM Sun Jan 27, 2008

56k modem      56
256k DSL      256
512k DSL      512
1Mb DSL/Cable      1024
2Mb DSL/Cable      2048
4Mb DSL/Cable      4096
8Mb DSL/Cable      8192
You      1895
Results   7816 kbits downloaded in 4.125 sec
this is a uk speedtest

Please can you post your line stats? If you're not sure about that, please post the make and model of the router you're using.

Also, the results of a BT speedtest would be useful (warning: perseverance required - it's often very busy, or just doesn't work!). The results will look something like this (with different values):

Code Select

Test1 comprises of Best Effort Test: -provides background information.
IP profile for your line is - 152 kbps
DSL connection rate: 448 kbps(UP-STREAM) 4000 kbps(DOWN-STREAM)
Actual IP throughput achieved during the test was - 117 kbps

At the moment, your problem could be lots of things (low sync and therefore low profile, stuck profile, high errors, etc). Hopefully we'll be able to narrow it down with some more information.

Lance · Jan 27, 2008, 22:47:14

A couple of tracert results to the server would be good as well.

Simon · Jan 28, 2008, 00:08:58

Quote from: Sebby on Jan 27, 2008, 22:37:30
You're so efficient.

I have to be of some use!

anz1066 · Jan 28, 2008, 01:34:57

bare with me as i noticed it dropped down to it`s usual state, so it might be the server i play on.
thanks for now, i`ll keep you posted.
it might be a good idea to have a sticky with details on how to get the lines stats and profile etc if it`s not allready done.

Thomson Speedtouch ST780
Link Information
Uptime:   0 days, 12:37:40
Modulation:   G.992.1 annex A
Bandwidth (Up/Down) [kbps/kbps]:   448 / 8,128
Data Transferred (Sent/Received) [MB/MB]:   279.57 / 286.23
Output Power (Up/Down) [dBm]:   12.0 / 11.5
Line Attenuation (Up/Down) [dB]:   5.0 / 9.0
SN Margin (Up/Down) [dB]:   22.0 / 11.0
Vendor ID (Local/Remote):   TMMB / TSTC
Loss of Framing (Local/Remote):   0 / 0
Loss of Signal (Local/Remote):   0 / 0
Loss of Power (Local/Remote):   0 / 0
Loss of Link (Remote):   0
Error Seconds (Local/Remote):   0 / 0
FEC Errors (Up/Down):   0 / 0
CRC Errors (Up/Down):   0 / 1
HEC Errors (Up/Down):   0 / 1

Sebby · Jan 28, 2008, 09:26:45

Your stats are good; great, actually. Errors are non-existent so it can't be that. I'd give IDNet a call as there is nothing obvious wrong here.

Rik · Jan 28, 2008, 09:33:50

Quote from: anz1066 on Jan 28, 2008, 01:34:57
it might be a good idea to have a sticky with details on how to get the lines stats and profile etc if it`s not allready done.

It's something I haven't done, as the resource already exists at:

http://www.kitz.co.uk/adsl/frogstats.htm

Simon · Jan 28, 2008, 11:15:08

Might it be worth adding that link to the FAQs, if it's not already, Rik?

Rik · Jan 28, 2008, 11:19:43

It's already there, Simon, in the "Things we need to know" FAQ.

Simon · Jan 28, 2008, 11:27:49

I really must gen up on those. Could everyone stop posting for 24 hours please, so I can catch up?

Rik · Jan 28, 2008, 11:33:11

OK...

anz1066 · Jan 31, 2008, 02:33:53

looks like everything is ok, i think it could be the server i play on being unable to cope with too many players. btw the ping shown here is not accurate lol
appologies to Idnet if blamed them, i`m old and can`t remember

thanks all the help peeps

Rik · Jan 31, 2008, 09:03:57

Maidenhead often seems to be on the other side of the world from its ping times.

Glad you're sorted, thanks for letting us know.

Si · Jan 31, 2008, 09:48:44

Quote from: Rik on Jan 31, 2008, 09:03:57
Maidenhead often seems to be on the other side of the world from its ping times.

I used to live there, I often thought it was on a different planet....

Rik · Jan 31, 2008, 09:54:00

You should visit Milton Keynes.

ducky22 · Jan 31, 2008, 16:33:25

Hmmm unfortunately i'm getting some erratic pings today.

Mostly on IDNet's network it seems.

M:\>tracert bbc.co.uk

Tracing route to bbc.co.uk [212.58.224.131]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 52 ms 35 ms 38 ms telehouse-gw2-msdp.idnet.net [212.69.63.51]
3 30 ms 27 ms 28 ms telehouse-gw3-gi0-1-400.idnet.net [212.69.63.243
]
4 29 ms 30 ms 26 ms rt-lonap-b.thdo.bbc.co.uk [193.203.5.91]
5 26 ms 26 ms 25 ms 212.58.238.133
6 25 ms 24 ms 24 ms rdirwww-vip.thdo.bbc.co.uk [212.58.224.131]

Trace complete.

Any else seeing problems?

Rik · Jan 31, 2008, 16:38:06

Seems OK here, though a different route:

ping www.bbc.co.uk

Pinging www.bbc.net.uk [212.58.253.72] with 32 bytes of data:

Reply from 212.58.253.72: bytes=32 time=25ms TTL=248
Reply from 212.58.253.72: bytes=32 time=23ms TTL=248
Reply from 212.58.253.72: bytes=32 time=24ms TTL=248
Reply from 212.58.253.72: bytes=32 time=28ms TTL=248

Ping statistics for 212.58.253.72:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 23ms, Maximum = 28ms, Average = 25ms

tracert www.bbc.co.uk

Tracing route to www.bbc.net.uk [212.58.253.70]
over a maximum of 30 hops:

1 <1 ms 1 ms <1 ms home [192.168.1.254]
2 25 ms 25 ms 27 ms telehouse-gw2.idnet.net [212.69.63.55]
3 25 ms 25 ms 27 ms telehouse-gw3-gi0-1-400.idnet.net [212.69.63.243
]
4 31 ms 23 ms 23 ms rt-lonap-b.thdo.bbc.co.uk [193.203.5.91]
5 27 ms 25 ms 23 ms 212.58.238.133
6 30 ms 29 ms 23 ms 212.58.239.222
7 26 ms 27 ms 25 ms www1.cwwtf.bbc.co.uk [212.58.253.70]

Trace complete.

ducky22 · Jan 31, 2008, 16:40:25

Oh well.... no recreational counterstrike for me this evening!

Might try rebooting router - see what happens.

AndyG · Jan 31, 2008, 16:53:20

Quote from: ducky22 on Jan 31, 2008, 16:33:25
Hmmm unfortunately i'm getting some erratic pings today.

Mostly on IDNet's network it seems.

M:\>tracert bbc.co.uk

Tracing route to bbc.co.uk [212.58.224.131]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 52 ms 35 ms 38 ms telehouse-gw2-msdp.idnet.net [212.69.63.51]
3 30 ms 27 ms 28 ms telehouse-gw3-gi0-1-400.idnet.net [212.69.63.243
]
4 29 ms 30 ms 26 ms rt-lonap-b.thdo.bbc.co.uk [193.203.5.91]
5 26 ms 26 ms 25 ms 212.58.238.133
6 25 ms 24 ms 24 ms rdirwww-vip.thdo.bbc.co.uk [212.58.224.131]

Trace complete.

Any else seeing problems?

Hi

I'd say those figures are pretty damn good. The important line is the bottom one that says you are getting pings of 25/24/24mS from the destination server. Thats about as good as you could hope for.

Don't worry too much about the figures from intermediate servers.

Andy

ducky22 · Jan 31, 2008, 16:59:38

Quote from: AndyG on Jan 31, 2008, 16:53:20
Hi

I'd say those figures are pretty damn good. The important line is the bottom one that says you are getting pings of 25/24/24mS from the destination server. Thats about as good as you could hope for.

Don't worry too much about the figures from intermediate servers.

Andy

Meh, they're average but I live in Scotland so its not a problem.

When you start seeing high pings on border routers, you know something is up. I'm also seeing intermittant packetloss which is a bugger. :-(.

AndyG · Jan 31, 2008, 17:09:51

Quote from: ducky22 on Jan 31, 2008, 16:59:38
Meh, they're average but I live in Scotland so its not a problem.

When you start seeing high pings on border routers, you know something is up. I'm also seeing intermittant packetloss which is a bugger. :-(.

I'd not worry too much about the figures from the 'border routers'. Routers have lots of important things to do and responding to pings can be pretty low down on their priorities. It could be said that the routers within idnet are responding 'when they get time'. The responses you get from the destination servers have passed through all the routers in the list anyway the overall route is working pretty well based on your tracert above.

Packet loss is a different matter of course.

Andy

RA-1972 · Jan 31, 2008, 18:23:40

Quote from: ducky22 on Jan 31, 2008, 16:40:25
Oh well.... no recreational counterstrike for me this evening!

Might try rebooting router - see what happens.

Off subject.

Ducky what is your counterstike tag m8 ?