It should be impossible to get an upload speed greater than the upstream IP Profile.

It's working perfectly here, I just accepted the java cert and continued.

Download speedachieved during the test was - 37.48 Mbps
For your connection, the acceptable range of speedsis 12 Mbps-38.72 Mbps .
Additional Information:
IP Profile for your line is - 38.72 Mbps

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

I did wonder! - Didn't know enough to be 100% sure

I'll try it again tomorrow and see if it tells a truer story.

The BT tester has been erratic for me this past hour - busy, timed out, unable to complete...eventually, on the fifth try I got a result:
Down 6.68 up (max achievable 7.15)
Up .973 (max achievable 832)

So it's still showing that oddness on the up speed.

I did a Speedtest right after and got an identical result on both speeds ...think BT are using Speedtest!

I think a new thread somewhere is indicated Trishah. This one is mainly targeted at Fibre tests and how accurate the tester is with those. You're on ADSL2+ and from previous discussion I'm not happy about your speeds. Could be a lengthy discussion .

So sorry - I'd initially forgotten I was reading the fibre section

I had thought we decided nothing much could be done about my speeds ...I'll post my router stats etc in the other thread!

Now working for me, since I was put on the 80/20 trial today.

In reply to a post by billford:

Some reports of problems with the speedtester and Java 7, any help?
http://www.idnetters.co.uk/forums/index.php/topic,28...

This is a red herring to some extent. I have had Java 7 since release in July last year. Since running the test today, a Java Applet was downloaded and have not been able to run the tester since. I have screen shots from January when Java7b2 was installed, java7b3 has just been released. It does not seem to be a Java 7 issue as such.

DrT

Edited by deleted (Mon 27-Feb-12 20:29:21)

You are right - it is NOT a Java issue.

I had the problem - as mentioned below and now it has gone ... with NO change to my Java set up to cause it or cure it!

Did you notice if an amended/updated applet was downloaded at all?

DrT