If I use Tracert in a command window:

speedtester.bt.com resolves to: 217.35.209.142

and speedtest.btcentralplus.com to: 217.32.105.42

and both have identical routing if I do them sequentially. But wait 5 minutes and try again, the routing may change. For example:

Tracing route to speedtester.bt.com [217.35.209.142]
1 ... homeportal
... ...
6 ... 213.120.176.178
7 ... acc1-10GigE-0-1-0-5.l-far.21cn-ipp.bt.net [109.159.249.82]
8 ... core2-te0-15-0-2.ilford.ukcore.bt.net [109.159.249.19]
9 ... core2-pos6-0.manchester.ukcore.bt.net [62.6.204.13]
10 ... vhsaccess1-pos8-0.manchester.fixed.bt.net [62.6.196.202]
11 ... Request timed out.

Tracing route to speedtest.btcentralplus.com [217.32.105.42]
1 ... homeportal
... ...
6 ... 213.120.176.178
7 ... acc1-10GigE-0-1-0-5.l-far.21cn-ipp.bt.net [109.159.249.82]
8 ... core2-te0-15-0-2.ilford.ukcore.bt.net [109.159.249.19]
9 ... core2-pos6-0.manchester.ukcore.bt.net [62.6.204.13]
10 ... vhsaccess1-pos8-0.manchester.fixed.bt.net [62.6.196.202]
11 ... Request timed out.


Then a few minutes later:

Tracing route to speedtester.bt.com [217.35.209.142]
1 ... homeportal
... ...
6 ... 213.120.176.178
7 ... acc1-10GigE-0-1-0-5.l-far.21cn-ipp.bt.net [109.159.249.82]
8 ... core2-te-0-0-0-2.ilford.ukcore.bt.net [109.159.249.31]
9 ... core2-pos9-0.stalbans.ukcore.bt.net [194.74.16.222]
10 ... vhsaccess2-gig1-0.stalbans.fixed.bt.net [217.32.169.148]
11 ... Request timed out.

Tracing route to speedtest.btcentralplus.com [217.32.105.42]
1 ... homeportal
... ...
6 ... 213.120.176.178
7 ... acc1-10GigE-0-1-0-5.l-far.21cn-ipp.bt.net [109.159.249.82]
8 ... core2-te-0-0-0-2.ilford.ukcore.bt.net [109.159.249.31]
9 ... core2-pos9-0.stalbans.ukcore.bt.net [194.74.16.222]
10 ... vhsaccess2-gig1-0.stalbans.fixed.bt.net [217.32.169.148]
11 ... Request timed out.

If I use PingPlotter and enter the IP address of speedtester.bt.com 217.35.209.142 it comes back with the Target Name (URL) of speedtest.btcentralplus.com 217.32.105.42 returns the same.

If I send PingPlotter to speedtester.bt.com it returns an IP of 217.32.105.42 ...

It suggests that there is more than on tester running in the network and each request is pointed to a server with lowest usage and that both URLs ultimately point to the same locations.

Get this too! Ticked the Assured Rate which it offered me and it ran:

1. Assured Rate Test: -provides background information.

Download Speed
15.11 Mbps

0 Kbps 0 Kbps
Max Achievable Speed

Download speed achieved during the test was - 15.11 Mbps
For your connection, the acceptable range of speeds is 0 Kbps-0 Kbps .
Additional Information:
Assured Rate IP profile on your line is - 0 Kbps

We were unable to identify any performance problem with your service at this time.

Don't have Assured Rate service as far as I know.

EDIT: I notice that the main test no longer reports my Sync Speeds.

Edited by XRaySpeX (Tue 14-Feb-12 12:11:35)

In reply to a post by XRaySpeX:

I notice that the main test no longer reports my Sync Speeds.

Well that would be just too helpful to customers who aren't able to find it in their router stats.

It's a wonder they still tell us the IP Profile, not just the acceptable speed range .

Have you noticed it is a much shorter, and therefore possibly less accurate, test? Can't have unhappy useres hogging expensive bandwith to gather evidence of a problem, can we!

C:\Users\Bob>tracert speedtester.bt.com

Tracing route to speedtester.bt.com [217.32.105.42]

5   112 ms    29 ms    15 ms  t2as2-tge4-4.uk-lon1.eu.bt.net [166.49.211.137]
 6    15 ms    14 ms    14 ms  166-49-214-130.eu.bt.net [166.49.214.130]
 7    19 ms    18 ms    19 ms  core1-pos9-0-0.telehouse.ukcore.bt.net [194.74.65.117]
 8    16 ms    15 ms    16 ms  core2-pos9-0.stalbans.ukcore.bt.net [194.74.16.222]
 9    16 ms    15 ms    15 ms  vhsaccess2-gig2-0.stalbans.fixed.bt.net [217.32.169.156]
10     *        *        *     Request timed out.

Hi,

Kelly Comms finally arrived today and swapped FTTC modem out and I was kind of hoping the re-sync may have kicked the BT Speedtester into life as regards my connection - wrong, it still doesn't want to play.

PlusNet say they have some FTTC customers that it's working for and don't (at the moment regard it as a fault!!!!) I am persuing this angle.

I took my laptop to a friend round the corner who is not on FTTC and guess what, the tester works which proves to me at least it's the connection/routing that's the issue.

Guess I'm going to have to follow MHC's advice and get stuck in and have sight of my own info

Pete

Edited by deleted (Tue 14-Feb-12 15:38:22)

I'm with Plusnet & BT Speed test works for me, including the "additional services" test

Hi Bald_Eagle1,

Just to confirm, are you on PlusNet Extra Fibre via FTTC?

I can take my laptop to a friend on normal ADSLx and the tester works fine but a no show on my own connection, i.e. the laptop config is fine.

Interestingly, PN Support cannot do a line speed/profile check either

Pete

As well as Bald_Eagle's reply when it comes, see my sig .

@ Cathotel,

I'm on Plusnet Value Fibre.

Plusnet were unable to run the tests last week & sent me this message related to an ongoing speed issue:-

"With regards to the GEA test failures on your line I simply cannot get the test to run on your circuit. The GEA test shows us the DLM profile and sync rates so it's really useful for this type of issue. If the test continually fails then it is likely that there is planned maintenance on the testing heads for your circuit. As such we will need to wait for this to clear before we can see these details."

The BT speed tester works O.K. for me though.

Paul.

In reply to a post by RobertoS:

Neat!

Upload speed achieved during the test was - 1.03Mbps
Additional Information:
Upstream Rate IP profile on your line is - 832 Kbps

I always understood that the BT tester was the most accurate, and it always has shown speeds a little slower than Speedtest does.
That one however showed higher on both counts: 6.82 & 1.03. Last time I used it I got 6382 and 911.