latency

just did a speed test & my latency was in the region of 166, it was 68 last night, seems high to me... was wondering if this is 'normal'?

No - not normal. In fact 68 can be considered high too although that will depend on where you are and if you are wired or wireless.

Repeat the test a few times and see what happens. Also try using a PING command from a command window <ping bbc.co.uk> and see what the result is. Follow that with <tracert bbc.co.uk> then copy and paste the results here.

thanks, going to be a few hours before I have time to try & understand & do what you suggest ~ later

sorry about the delay in replying to your help ~ life got in the way....
I couldn't get copy to work in command line window so typed out the results ~ interesting, the lowest latency I've had on the last 2 thinkbb speedtests was 55ms....

pinging bbc.co.uk [212.58.244.20] with 32 bytes of data:
reply from 212.58.244.20: bytes=32 time=33ms TTL=54
reply from 212.58.244.20: bytes=32 time=32ms TTL=54
reply from 212.58.244.20: bytes=32 time=31ms TTL=54
reply from 212.58.244.20: bytes=32 time=32ms TTL=54

Ping statistics for 212.58.244.20:
Packets: Sent = 4, Received = 4, lost = 0 <0% loss>,
Approximate round trip times in milli-seconds:
Minimum = 31ms, Maximum = 33ms, Average = 32ms

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

1 73ms 98ms 98ms dsldevice.lan [192.168.1.254]
2 33ms 34ms 33ms 1o0.11.central11.pc1-bng02.plus.net [195.166.130.152]
3 36ms 34ms 34ms irb.11.PCL-CR01.plus.net [84.93.249.97]
4 35ms 35ms 33ms ae1.pyw-cr01.plus.net [195.166.129.0]
5 35ms 35ms 34ms Kingston-gw.thdo.bbc.co.uk [212.58.239.6]
6 * * * Request timed out.
7 * * * Request timed out.
8 35ms 34ms 33ms ae0.er01.te1hc.bbc.co.uk [132.185.254.109]
9 35ms 35ms 34ms 132.185.255.149
10 34ms 34ms 33ms fmt-vip71.te1hc.bbc.co.uk [212.58.244.20]

Trace complete.

To copy from the CLI there are two options.

For both, right click in the CLI window. "Select all" will do that, turning it black on white instead of white on black. Hit Return. It reverts to white on black but all is in your clipboard.

If you select "Mark" you can place the cursor wherever you want and drag out a rectangle. Again, Return completes the copy of the contents of your rectangle. If you get it wrong you probably have to start again at the right click.

Edited by RobertoS (Fri 31-Jul-15 22:40:56)

It is te first two hops that may be causing the problems - once you hit the PlusNet network, all appears fine.

Are these wired or wireless? what devices are on the network? Have you tried it with all AV temporarily turned off/disabled.

thanks Roberto for the info, lot easier

MHC, I did the cli from my main wired pc, I also have a netbook in my homegroup but that was sleeping at the time.

my partner has a fire hd tablet which he was using at the time via wireless. (reading a book I think)

we have no tv or other devices ~ not sure what you mean by "AV disabled or turned off"

thanks so much for your time, it's appreciated.

Edited by deleted (Sat 01-Aug-15 21:52:15)

AV - Anti-virus of what ever type.


The wired connection - was that direct into the Router/Hub?

yep, direct ethernet to router about 1 metre away.
only windows defender active at the time.

At this time, no real ideas ... The bottle neck is at te very beginning, once you get past the DSLAM everything looks OK.

Go through the obvious, power off the router and modem (if separate). Disconnect from line. Wait 30 minutes and then power back up, wait 5 minutes and then reconnect phone line.