Odd TBB test ?
I meant to reply many hours ago but got a bit tied up sifting through a stack of PN forum emails and forgot!!
Thanks for that scrookes, it clears that bit up regarding the BTw tester 
Any news on the TBB one? As I wouldn't have thought there would be too many surfing at this hour... 
It's just that....
..... 18Mbps at 00:39 - http://www.thinkbroadband.com/speedtest/results.html?id=1487637552777361955
..... 11Mbps at 01:02 - http://www.thinkbroadband.com/speedtest/results.html?id=1487638963664993755
..... 8Mbps at 01:36 - http://www.thinkbroadband.com/speedtest/results.html?id=1487641005753292055
(not a happy bunny)
I'll power the hub down and see if this changes anything.....
edit
Hub light sequence:
green light for a while
green light flashing
blue light for a while
amber light flashing for a long time
amber light for a while
amber light then BB light for a long time
blue
23Mbps at (01:59) - http://www.thinkbroadband.com/speedtest/results.html?id=1487642393889797955
(happier bunny, but....)
So... am I being thick* or are these pointing to 'hiper04.sheff.dial.plus.net' being some (or all) of the reason why the TBB results are showing as they do?
(Not to TBB, but using portal.plus.net as a comparison as I've seen some oddities over the last 2 weeks or so when carrying out traceroutes - these were not to TBB hence not making a big deal of them)
Carried out on 19/02/17 but note hop 3
tracert 212.159.9.2
1 1 ms <1 ms <1 ms dsldevice.lan [172.16.0.1]
2 * * * Request timed out.
3 * 17 ms 17 ms 141.hiper04.sheff.dial.plus.net.uk [195.166.143.141]
4 23 ms 17 ms 18 ms be3-3106.psb-ir02.plus.net [195.166.143.140]
5 16 ms 17 ms 17 ms be1.psb-ir01.plus.net [195.166.129.176]
6 22 ms 22 ms 22 ms 84-93-224-48.plus.net [84.93.224.48]
7 22 ms 23 ms 22 ms reth0.ptp-elbfw.plus.net [84.92.0.109]
8 24 ms 22 ms 22 ms 10.104.128.55
9 30 ms 22 ms 24 ms portal.plus.net [212.159.9.2]
----
Both of the following were carried out today at 03:30 after the manual hub reboot
tracert 80.249.106.133
1 1 ms <1 ms <1 ms dsldevice.lan [172.16.0.1]
2 * * * Request timed out.
3 * * * Request timed out.
4 17 ms 16 ms 17 ms be3-3104.psb-ir01.plus.net [195.166.143.136]
5 17 ms 16 ms 17 ms 195.99.125.134
6 17 ms 16 ms 17 ms 213.121.193.207
7 * * * Request timed out.
8 17 ms 17 ms 17 ms te2-1-9.star10g.bdr-rt3.thdo.ncuk.net [80.249.97.17]
9 30 ms 19 ms 18 ms po4-31.core-rs2.thdo.ncuk.net [80.249.97.85]
10 17 ms 17 ms 17 ms speedtest7.thinkbroadband.com [80.249.106.133]
----
tracert 80.249.99.130
1 1 ms <1 ms <1 ms dsldevice.lan [172.16.0.1]
2 * * * Request timed out.
3 * * * Request timed out.
4 16 ms 16 ms 16 ms be3-3104.psb-ir01.plus.net [195.166.143.136]
5 16 ms 16 ms 17 ms core1-BE1.southbank.ukcore.bt.net [195.99.125.130]
6 17 ms 17 ms 17 ms 62.172.103.23
7 * * * Request timed out.
8 17 ms 17 ms 16 ms te2-1-9.star10g.bdr-rt3.thdo.ncuk.net [80.249.97.17]
9 18 ms 19 ms 18 ms po4-31.core-rs2.thdo.ncuk.net [80.249.97.85]
10 17 ms 17 ms 17 ms www.thinkbroadband.com [80.249.99.130]
----
And carried out at 10:30, nothing has changed at this end, but note hop 3 is back when routing to TBB, which is the first time I've ever seen this when routing to TBB....
>tracert 80.249.106.133
1 1 ms <1 ms <1 ms dsldevice.lan [172.16.0.1]
2 * * * Request timed out.
3 * 16 ms 16 ms 137.hiper04.sheff.dial.plus.net.uk [195.166.143.137]
4 17 ms 16 ms 17 ms be3-3104.psb-ir01.plus.net [195.166.143.136]
5 17 ms 17 ms 16 ms 195.99.125.134
6 17 ms 16 ms 17 ms 213.121.193.207
7 * * * Request timed out.
8 17 ms 17 ms 17 ms te2-1-9.star10g.bdr-rt3.thdo.ncuk.net [80.249.97.17]
9 18 ms 18 ms 19 ms po4-31.core-rs2.thdo.ncuk.net [80.249.97.85]
10 17 ms 17 ms 17 ms speedtest7.thinkbroadband.com [80.249.106.133]
----
tracert 80.249.99.130
1 1 ms <1 ms <1 ms dsldevice.lan [172.16.0.1]
2 * * * Request timed out.
3 * 16 ms 17 ms 137.hiper04.sheff.dial.plus.net.uk [195.166.143.137]
4 16 ms 16 ms 16 ms be3-3104.psb-ir01.plus.net [195.166.143.136]
5 17 ms 16 ms 16 ms core1-BE1.southbank.ukcore.bt.net [195.99.125.130]
6 17 ms 17 ms 17 ms 62.172.103.23
7 * * * Request timed out.
8 17 ms 17 ms 17 ms te2-1-9.star10g.bdr-rt3.thdo.ncuk.net [80.249.97.17]
9 17 ms 19 ms 19 ms po4-31.core-rs2.thdo.ncuk.net [80.249.97.85]
10 18 ms 17 ms 17 ms www.thinkbroadband.com [80.249.99.130]
----
Another test to portal.plus.net just prior to posting
>tracert 212.159.9.2
1 1 ms <1 ms <1 ms dsldevice.lan [172.16.0.1]
2 * * * Request timed out.
3 * 17 ms 17 ms 141.hiper04.sheff.dial.plus.net.uk [195.166.143.141]
4 23 ms 17 ms 18 ms be3-3106.psb-ir02.plus.net [195.166.143.140]
5 16 ms 17 ms 17 ms be1.psb-ir01.plus.net [195.166.129.176]
6 22 ms 22 ms 22 ms 84-93-224-48.plus.net [84.93.224.48]
7 22 ms 23 ms 22 ms reth0.ptp-elbfw.plus.net [84.92.0.109]
8 24 ms 22 ms 22 ms 10.104.128.55
9 30 ms 22 ms 24 ms portal.plus.net [212.159.9.2]
---
I'm not sure on hops 4 and 5 when going to portal.plus.net either, *pickled eyes, 48+hrs of no sleep, being away from this sort of stuff for a few years and the onset of a migraine may be contributing to this - as in, should it jump gateways or have I got this wrong too...?
If it turns out I have, sorry in advance!!
@Kelly All* of mine are poor 
*The only ones that show a good graph are when using TBB's alternative tester - the proof is further up.
re Traceroutes - I'd got it in my head that because 'hiper04.sheff.dial..' was sometimes showing and then repeat traceroutes were not, even though they were going to the same destination, could the erratic TBB results be showing a potential reason why we (as in those on this thread) are seeing this, as other ISP's appear to have sorted theirs....?
I even keep a completely untouched version of IE for these types of issues, to rule out browser config changes at my end.
I did also think what happens if I tried a different DNS
Google DNS - tracert 80.249.99.130
1 <1 ms <1 ms <1 ms PNHUB1 [172.16.0.1]
2 * * * Request timed out.
3 16 ms 16 ms 16 ms 137.hiper04.sheff.dial.plus.net.uk [195.166.143.137]
4 16 ms 17 ms 18 ms be3-3104.psb-ir01.plus.net [195.166.143.136]
5 24 ms 17 ms 16 ms core1-BE1.southbank.ukcore.bt.net [195.99.125.130]
6 17 ms 17 ms 17 ms peer1-et-10-1-0.telehouse.ukcore.bt.net [195.99.127.3]
7 * * * Request timed out.
8 18 ms 25 ms 18 ms po4-31.core-rs2.thdo.ncuk.net [80.249.97.85]
9 18 ms 17 ms 17 ms www.thinkbroadband.com [80.249.99.130]
(just a quick fwiw - you can tell from looking at the above that I'm not using PN DNS from the reference of PNHUB1 on hop 1 - guess all involved may know this, but might be of some use to future readers....?)
PN DNS - tracert 80.249.99.130
1 1 ms <1 ms <1 ms dsldevice.lan [172.16.0.1]
2 * * * Request timed out.
3 * * * Request timed out.
4 16 ms 17 ms 16 ms be3-3104.psb-ir01.plus.net [195.166.143.136]
5 17 ms 17 ms 30 ms core1-BE1.southbank.ukcore.bt.net [195.99.125.130]
6 17 ms 17 ms 17 ms peer1-et-10-1-0.telehouse.ukcore.bt.net [195.99.127.3]
7 * * * Request timed out.
8 28 ms 23 ms 19 ms po4-31.core-rs2.thdo.ncuk.net [80.249.97.85]
9 18 ms 24 ms 17 ms www.thinkbroadband.com [80.249.99.130]
(and again just to point out that the above changes to dsldevice.lan when using PN DNS)
The above is only posted for reference as the testing was not conclusive, but may be something that can be ticked off the list....
Just to show how erratic the results are, here's some from:
22/02 at 19:23 = http://www.thinkbroadband.com/speedtest/results.html?id=1487791386118759755
22/02 at 21:30 - http://www.thinkbroadband.com/speedtest/results.html?id=1487799056444388655
22/02 at 23:37 - http://www.thinkbroadband.com/speedtest/results.html?id=1487806632135290455
-----------------
23/02 at 01:14 - http://www.thinkbroadband.com/speedtest/results.html?id=1487812475104599855
23/02 at 01:40 - http://www.thinkbroadband.com/speedtest/results.html?id=1487814050165132155
If only all the above were all similar - nothing was done differently at this end, so why would they be like this?
However, right now it's this 
Wind or rain perhaps? - It certainly isn't wifi as I've been using ethernet to this laptop to rule that part out for a number of weeks now
we made a change to the way traffic routes over the BT Network on Monday
That might answer something I've been getting recently, or maybe not....
Since joining PN, Youtube videos have been poor when they first play content - I'll get the loading swirl, then any of the content is blurry/out of focus at the beginning, then it's all good and can play fine till the end. - tested over ethernet only.
Since yesterday*, the content does this but also the image will freeze now too but the sound continues.
(I have today - how ironic is the timing - reset FF to default as over a period of time I had tweaked many of the config settings. I was then going to try YT again)
*only tried from then on. The last time YT was used was Friday pm/Saturday am
edit. re message #414, yep got it, I'm just trying to assist and thought it was worth a mention that sometimes I get hiper, then sometimes I didn't. I would have thought it would be all or nothing rather than a now ya see me now ya don't so often - In my medically induced confused state, I'd have expected it to be either one or the other all of the time!!
