[Womble]

Here are the results from Mr Elwells' tester.....

Dan Elwell's Broadband Speed Test (unregistered)
Speed Test Report 04/12/15 22:17 - Full test

Test conducted at: 15/12/2004 22:17:06
Test sequence: Full test

Please note that these results are a snapshot of this particular moment. Run the test a few times to ensure maximum accuracy. Although the test has been constructed to be highly accurate, no guarantees can be made to the level of accuracy experienced in everyday use.

Test 1: Ping times to UK servers

Ideally, you should get a result of around 30 ms (lower is better)

linx.co.uk: 29.3 ms
gnu.teleglobe.net: 84.5 ms
gold.ac.uk: 12.8 ms
cardiff.ac.uk: 18.5 ms

Your ping times are slightly poorer than expected.

Test 2: Ping times to European servers

Ideally, you should get a result of around 50 ms (lower is better)

uni-kl.de: 40.8 ms
tu-berlin.de: 39.5 ms
uvsq.fr: 16.3 ms
free.fr: 18 ms

The results of this test indicate no problems.

Test 3: Ping times to east-coast USA servers

Ideally, you should get a result of around 120 ms (lower is better)

dulug.duke.edu: 106.5 ms
the-city.seas.upenn.edu: 99.5 ms
unet.brandeis.edu: 97.5 ms
aeneas.mit.edu: 90.3 ms

The results of this test indicate no problems.

Test 4: Ping times to west-coast USA servers

Ideally, you should get a result of around 160 ms (lower is better)

oregonstate.edu: 165.8 ms
ucsb.edu: 158.8 ms
mirror.chpc.utah.edu: This test failed due to a server timeout or other error.
mirrors.kernel.org: 157.8 ms

The results of this test indicate no problems.

Test 5: Ping times to east Asia servers

Ideally, you should get a result of around 300 ms (lower is better)

zentek-international.com: 337.8 ms
meisei-u.ac.jp: 268.5 ms
stu.edu.tw: This test failed due to a server timeout or other error.
stu.edu.tw: This test failed due to a server timeout or other error.

The results of this test indicate no problems.

Test 6: Ping times to Australian servers

Ideally, you should get a result of around 350 ms (lower is better)

apache.inspire.net.nz: 313.5 ms
apache.ausgamers.com: 362 ms
apache.ausgamers.com: 359.7 ms
apache.inspire.net.nz: 315.7 ms

The results of this test indicate no problems.

Test 7: Ping times to central Asian servers

Ideally, you should get a result of around 300 ms (lower is better)

apache.fresh.co.il: 97.8 ms
oynasana.com: 95.5 ms
apache.fresh.co.il: 97 ms
sai.msu.su: 75.5 ms

The results of this test indicate no problems.

Test 8: Download speeds from UK servers

Ideally, you should get a result of around 1536 Kb/s (higher is better)

apache.mirror.positive-internet.com: 1445 Kb/s

The results of this test indicate no problems.

Test 9: Download speeds from European servers

Ideally, you should get a result of around 1536 Kb/s (higher is better)

heanet.ie: 1425 Kb/s

The results of this test indicate no problems.

Test 10: Download speeds from east-coast USA servers

Ideally, you should get a result of around 1536 Kb/s (higher is better)

apache.247available.com: 1434 Kb/s

The results of this test indicate no problems.

Test 11: Upload speeds to the Speed Test Server

Ideally, you should get a result of around 256 Kb/s (higher is better)

Not conducted: You must register this software in order to perform this test.

Please click 'What's This?' for information on registering this software to enable this test.

Test 12: Packet loss en route to a UK server

Ideally, you should get a result of around 0 % (lower is better)

vantage.myby.co.uk: 0 %
gnu.teleglobe.net: 0 %

The results of this test indicate no problems.

Test 13: Packet loss en route to a European server

Ideally, you should get a result of around 0 % (lower is better)

fi.udc.es: 16 %
uni-kl.de: 2 %

An unacceptable level of packet loss has been detected which should be investigated.

Test 14: Packet loss en route to an east-coast USA server

Ideally, you should get a result of around 0 % (lower is better)

rutgers.edu: 0 %
dc.aleron.net: 4 %

A small amount of packet loss has been detected. This should be investigated.

End of testing.

It does show packet loss, but not consistantly. I have run the test a few times.

Is there any test I can do to see if its "noise" on the HFC network ar a problem with ntl's routers etc??