mybroadbandspeed - when is it going to be fixed?

[#1]

Quote from: jelv

Quote from: Bob Quote from: Bob What about changing the copy to read as follows then? [quote="Proposed caveat"]Sorry - My Broadband Speed is currently experiencing technical difficulty and may display misleading test results. Thanks for bearing with us while we fix things. This is now live.

It has been spotted that this caveat has been removed. Presumably that means that all of the issues in the following have been resolved:

Arrrrrgh! No they haven't. We recently put some ads on the page to get an idea about potential click-through rates but we were supposed to leave the caveat there. Looks like it got removed
In other news, I've suggested a few tweaks to the Ookla software that /might/ help improve performance a little (should hopefully be rolled over the coming weeks). The main bottleneck will continue to be network capacity to the boxes themselves though.

[#2]

This topic was started in March 2012 and still mybroadbandspeed is borked:
Just run some tests this morning:

[#3]

Yes, it is still not working correctly. There have been, and continue to be, higher priority things to work on. We're re-adding the warning as this shouldn't have been removed.

[#4]

What I am struggling to understand is why Plusnet wouldn't completely disable/remove the speed test while they are fixing it, as they are simply generating extra work for themselves by keeping it working (albeit not exactly) from extra speed enquiries because people didn't pay attention to the message, are new to Plusnet or not sure if they had accurate result or not.
The message "We are currently experiencing issues with our speed tester and results may not be 100% accurate. " is not very helpful, to put it mildly. It implies that you actually might get an accurate result, but unfortunately there is no way of knowing that your particular speed test was accurate, unless you have done 174 speed tests on 7 different sites and know exactly that it's not right and not just a problem on the line.

[#5]

[tt]traceroute to mybroadbandspeed.co.uk (84.92.1.14), 30 hops max, 52 byte packets
1  192.168.0.1 (192.168.0.1)  1.277 ms
2  lo0-central10.ptw-ag04.plus.net (195.166.128.194)  21.306 ms
3  link-a-central10.ptw-gw01.plus.net (212.159.2.156)  21.105 ms
4  xe-7-2-0.ptw-cr01.plus.net (212.159.0.252)  23.722 ms
5  te9-4.ptn-gw01.plus.net (195.166.129.33)  20.831 ms
6  vl55.ptn-lb02.plus.net (212.159.2.125)  20.823 ms
7  84.92.1.14 (84.92.1.14)  22.225 ms[/tt]
For some reason the traceroute to mybroadbandspeed.co.uk appears to go through the same load balancer as the DNS servers, that doesn't seem good. I wouldn't want a load of speedtest traffic clogging up the links to the DNS servers!

[#6]

All the servers in Telehouse are probably behind these load balancers e.g. the CGI platform:

Tracing route to ccgi.plus.net [84.92.1.4]
over a maximum of 30 hops:
  1     4 ms     3 ms     3 ms  home.gateway [192.168.1.254]
  2    16 ms    15 ms    18 ms  lo0-central10.ptn-ag03.plus.net [195.166.128.192]
  3    16 ms    16 ms    15 ms  link-a-central10.ptn-gw01.plus.net [212.159.2.136]
  4    16 ms    15 ms    15 ms  xe-5-3-0.ptw-cr01.plus.net [212.159.0.108]
  5    16 ms    15 ms    17 ms  te9-4.ptn-gw01.plus.net [195.166.129.33]
  6    15 ms    16 ms    15 ms  vl55.ptn-lb02.plus.net [212.159.2.125]
  7    18 ms    26 ms    15 ms  ccgi.plus.net [84.92.1.4]
Trace complete.

Given the modest capacity of the speedtest boxes themselves I very much doubt people running speedtests would affect DNS.