I get that low latency on my gaming PC after replacing a faulty gigabit network card. It is a decent piece of kit. Other old machines here show a latency of around 13ms. test server exactly the same, so I think I have very low latency, which seems to show on a machine fast enough to keep up with it - I expect there are many ready to prove me wrong, but all I know, is that things are down to where they used to be in the days of ASDL2+ that would hold a 1db snr for months, so hair-splitting apart, I am a fairly happy bunny, or at least will be until this time next week, when we will be 400 miles north suffering EE at our other property for a few days.

@professor973
Odd that your tracert test to bbc is just a tad worse than mine from Plusnet (13 ms against mine typically 10 or 11ms), but that your my speedtest tests show much lower (almost miraculous) latency of just 1 or 2 ms against my 14ms. Thinkbroadband test shows latency of 15ms for me, what does your show?

For my use I am not concerned as long as the latency remains below 20ms or so (Infinity just managed that at 18ms)

In reply to a post by professor973:

I get that low latency on my gaming PC after replacing a faulty gigabit network card. It is a decent piece of kit. Other old machines here show a latency of around 13ms. test server exactly the same, so I think I have very low latency, which seems to show on a machine fast enough to keep up with it - I expect there are many ready to prove me wrong,

I'm "sure" the old machines are reporting correctly, your line is incapable of reporting 1ms pings... and that's before its even reached the exchange maybe...

13ms is about correct, ping the BBC using "cmd" will reply with around 9-13ms too.

Same here - happy if usable. just done a test with PingPlotterPro, Different site and software and you will see first hop around 3 or 4 ms, depending where you stop it. last TBB test was around 13 ish if I remember, but all sites are different with routing via god knows where. Different servers on speedtest.net shows that, with XILO Maidenhead much lower than others.
http://postimg.org/image/ps1ra8frz/

rolling check with something better shows continual 3, 4, 5 ms on the first hop. After that a lottery.
http://postimg.org/image/ps1ra8frz/

Edited by professor973 (Sat 18-Jul-15 11:08:19)

So as I said 1ms to Maidenhead is impossible for you then, your first hop to TalkTalk was 4-5ms and total to google was 13ms as predicted already.

I believe the 1ms bug to be a glitch with speedtest.net and maybe something to do with browsers, firewall or any other combination of numbers and rubbish.

This is my tracert to Google, bare in mind I'm using WiFi so pings vary a bit.

Tracing route to google-public-dns-a.google.com [8.8.8.8]
over a maximum of 30 hops:

1 5 ms 1 ms 1 ms router.asus.com [192.168.1.1]
2 16 ms 12 ms 11 ms lo0.13.central13.pcl-bng02.plus.net [195.166.130
.154]
3 15 ms 15 ms 11 ms irb.13.pcl-cr02.plus.net [84.93.249.130]
4 16 ms 11 ms 11 ms ae1.ptw-cr02.plus.net [195.166.129.2]
5 14 ms 14 ms 11 ms ae2.ptw-cr01.plus.net [195.166.129.4]
6 14 ms 11 ms 11 ms 72.14.222.97
7 48 ms 13 ms 13 ms 216.239.47.23
8 17 ms 12 ms 14 ms 66.249.95.39
9 16 ms 13 ms 11 ms google-public-dns-a.google.com [8.8.8.8]

Trace complete.

Also looks like you've got some packet loss and jitter issues.... not good

Edited by mlmclaren (Sat 18-Jul-15 11:19:20)

As this is TBB, we might as well use their BQM ping plot. As the TBB speedtest shows much higher latency than a ping to BBC or whatever, a little artistic licence is allowed. I would say no packet loss whatsoever shows a connection not running at maximum. My packet loss no worse and much better than many. A little this morning as I suffer a little peak-time congestion here, but nothing that makes it unusable. Anyway, they say there is no such thing as bad advertising
http://www.thinkbroadband.com/ping/share/d23a03e87ea...

Edited by professor973 (Sat 18-Jul-15 11:50:40)

here is sky to google dns and also to opendns.

Tracing route to google-public-dns-a.google.com [8.8.8.8]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms home.gateway [192.168.1.253]
2 * * * Request timed out.
3 10 ms 10 ms 10 ms 02780842.bb.sky.com [2.120.8.66]
4 10 ms 10 ms 10 ms 72.14.203.204
5 10 ms 10 ms 10 ms 209.85.255.107
6 11 ms 10 ms 11 ms 209.85.250.77
7 11 ms 10 ms 10 ms google-public-dns-a.google.com [8.8.8.8]

Trace complete.

C:\Windows\system32>tracert 208.67.222.222

Tracing route to resolver1.opendns.com [208.67.222.222]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms home.gateway [192.168.1.253]
2 * * * Request timed out.
3 10 ms 10 ms 10 ms 02780842.bb.sky.com [2.120.8.66]
4 10 ms 10 ms 10 ms gi0-0p226.rtr1.lon.opendns.com [195.66.237.70]
5 10 ms 10 ms 10 ms resolver1.opendns.com [208.67.222.222]

Edited by Chrysalis (Sat 18-Jul-15 11:51:03)

In reply to a post by professor973:

As this is TBB, we might as well use their BQM ping plot.
http://www.thinkbroadband.com/ping/share/d23a03e87ea...

OK,

TBB: http://www.thinkbroadband.com/ping/share-large/8572c...
F8lure (Rapidswitch Maidenhead) : http://f8luresig.mouselike.org/sig.png?/55612.png
F8lure (Andrews & Arnold) : https://f8lure.mouselike.org/proxyfirebrick.asp?ID=5...

I did a resync at around 11:15am so thats the reason for the packet loss...

10 ms is good, but not seen an ISP with hops that are not unreachable. The cause and effect of that is what we should be getting to the bottom of.