murfitUK
20-09-2004, 21:18
Can anyone help? I am on the 600/750 service through a set-top box. On the whole it is not too bad but recently the service has been unacceptable. Yesterday and this evening, it is so bad as to be un-useable. I phoned customer services - they said there was nothing wrong with the system so it must be my computer at fault.
I have pasted a speed test result below, but I don't really know what it all means.
I would be grateful if someone could have a look and let me know what to say to ntl when I phone them again. I think I could get further by telling them exactly what is wrong instead of my usual feeble attempts - eg "Well, its just not working properly"!
I've got XP, connect through ethernet - don't know what else might be useful to you.
Thank you in advance.
Dan Elwell's Broadband Speed Test
Speed Test Report 04/09/20 20:02 - Full test
Test conducted at: 20/09/2004 20:02:29
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)
bbc.co.uk: 113.5 ms
f2s.com: 59 ms
vantage.myby.co.uk: This test failed due to a server timeout or other error.
bbc.co.uk: This test failed due to a server timeout or other error.
This result is much poorer than expected and should be investigated.
Test 2: Ping times to European servers
Ideally, you should get a result of around 50 ms (lower is better)
uvsq.fr: This test failed due to a server timeout or other error.
belnet.be: 363 ms
uni-kl.de: This test failed due to a server timeout or other error.
gmd.de: This test failed due to a server timeout or other error.
This result is much poorer than expected and should be investigated.
Test 3: Ping times to east-coast USA servers
Ideally, you should get a result of around 120 ms (lower is better)
aeneas.mit.edu: This test failed due to a server timeout or other error.
internet2.edu: 328 ms
aeneas.mit.edu: 261.8 ms
dc.aleron.net: 317 ms
This result shows serious problems with your ping times, and should be investigated.
Test 4: Ping times to west-coast USA servers
Ideally, you should get a result of around 160 ms (lower is better)
mirrors.usc.edu: 342.3 ms
cybertrails.com: This test failed due to a server timeout or other error.
berkeley.edu: 284.3 ms
mirrors.tds.net: This test failed due to a server timeout or other error.
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)
apache.linuxforum.net: This test failed due to a server timeout or other error.
apache.cdpa.nsysu.edu.tw: 412 ms
meisei-u.ac.jp: 289 ms
apache.cdpa.nsysu.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.ausgamers.com: 381.5 ms
apache.ausgamers.com: 476 ms
bondinet.com: 500.7 ms
planetmirror.com: 495 ms
Your ping times are slightly poorer than expected.
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: This test failed due to a server timeout or other error.
opensourcecommunity.ph: This test failed due to a server timeout or other error.
apache.fresh.co.il: This test failed due to a server timeout or other error.
apache.rinet.ru: 246 ms
The results of this test indicate no problems.
Test 8: Download speeds from UK servers
Ideally, you should get a result of around 600 Kb/s (higher is better)
apache.mirrors.rossfell.co.uk: This test failed due to a server timeout or other error.
Too many server errors occurred therefore this test is inconclusive.
Test 9: Download speeds from European servers
Ideally, you should get a result of around 600 Kb/s (higher is better)
artfiles.org: This test failed due to a server timeout or other error.
Too many server errors occurred therefore this test is inconclusive.
Test 10: Download speeds from east-coast USA servers
Ideally, you should get a result of around 600 Kb/s (higher is better)
jungle.metalab.unc.edu: This test failed due to a server timeout or other error.
Too many server errors occurred therefore this test is inconclusive.
Test 11: Upload speeds to the Speed Test Server
Ideally, you should get a result of around 128 Kb/s (higher is better)
broadbandspeedtest.net: This test failed due to a server timeout or other error.
Too many server errors occurred therefore this test is inconclusive.
Test 12: Packet loss en route to a UK server
Ideally, you should get a result of around 0 % (lower is better)
meto.gov.uk: 70 %
clara.net: 80 %
An unacceptable level of packet loss has been detected which should be investigated.
Test 13: Packet loss en route to a European server
Ideally, you should get a result of around 0 % (lower is better)
sunsite.cnlab-switch.ch: 62 %
sunet.se: 44 %
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)
aeneas.mit.edu: 86 %
dc.aleron.net: 58 %
An unacceptable level of packet loss has been detected which should be investigated.
End of testing.
This report was collated using Dan Elwell's Broadband Speed Test. For more information or to download, please visit www.broadbandspeedtest.net.
Generated 20/09/2004 20:02:30 using test version 3.0.316 - registered copy
I have pasted a speed test result below, but I don't really know what it all means.
I would be grateful if someone could have a look and let me know what to say to ntl when I phone them again. I think I could get further by telling them exactly what is wrong instead of my usual feeble attempts - eg "Well, its just not working properly"!
I've got XP, connect through ethernet - don't know what else might be useful to you.
Thank you in advance.
Dan Elwell's Broadband Speed Test
Speed Test Report 04/09/20 20:02 - Full test
Test conducted at: 20/09/2004 20:02:29
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)
bbc.co.uk: 113.5 ms
f2s.com: 59 ms
vantage.myby.co.uk: This test failed due to a server timeout or other error.
bbc.co.uk: This test failed due to a server timeout or other error.
This result is much poorer than expected and should be investigated.
Test 2: Ping times to European servers
Ideally, you should get a result of around 50 ms (lower is better)
uvsq.fr: This test failed due to a server timeout or other error.
belnet.be: 363 ms
uni-kl.de: This test failed due to a server timeout or other error.
gmd.de: This test failed due to a server timeout or other error.
This result is much poorer than expected and should be investigated.
Test 3: Ping times to east-coast USA servers
Ideally, you should get a result of around 120 ms (lower is better)
aeneas.mit.edu: This test failed due to a server timeout or other error.
internet2.edu: 328 ms
aeneas.mit.edu: 261.8 ms
dc.aleron.net: 317 ms
This result shows serious problems with your ping times, and should be investigated.
Test 4: Ping times to west-coast USA servers
Ideally, you should get a result of around 160 ms (lower is better)
mirrors.usc.edu: 342.3 ms
cybertrails.com: This test failed due to a server timeout or other error.
berkeley.edu: 284.3 ms
mirrors.tds.net: This test failed due to a server timeout or other error.
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)
apache.linuxforum.net: This test failed due to a server timeout or other error.
apache.cdpa.nsysu.edu.tw: 412 ms
meisei-u.ac.jp: 289 ms
apache.cdpa.nsysu.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.ausgamers.com: 381.5 ms
apache.ausgamers.com: 476 ms
bondinet.com: 500.7 ms
planetmirror.com: 495 ms
Your ping times are slightly poorer than expected.
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: This test failed due to a server timeout or other error.
opensourcecommunity.ph: This test failed due to a server timeout or other error.
apache.fresh.co.il: This test failed due to a server timeout or other error.
apache.rinet.ru: 246 ms
The results of this test indicate no problems.
Test 8: Download speeds from UK servers
Ideally, you should get a result of around 600 Kb/s (higher is better)
apache.mirrors.rossfell.co.uk: This test failed due to a server timeout or other error.
Too many server errors occurred therefore this test is inconclusive.
Test 9: Download speeds from European servers
Ideally, you should get a result of around 600 Kb/s (higher is better)
artfiles.org: This test failed due to a server timeout or other error.
Too many server errors occurred therefore this test is inconclusive.
Test 10: Download speeds from east-coast USA servers
Ideally, you should get a result of around 600 Kb/s (higher is better)
jungle.metalab.unc.edu: This test failed due to a server timeout or other error.
Too many server errors occurred therefore this test is inconclusive.
Test 11: Upload speeds to the Speed Test Server
Ideally, you should get a result of around 128 Kb/s (higher is better)
broadbandspeedtest.net: This test failed due to a server timeout or other error.
Too many server errors occurred therefore this test is inconclusive.
Test 12: Packet loss en route to a UK server
Ideally, you should get a result of around 0 % (lower is better)
meto.gov.uk: 70 %
clara.net: 80 %
An unacceptable level of packet loss has been detected which should be investigated.
Test 13: Packet loss en route to a European server
Ideally, you should get a result of around 0 % (lower is better)
sunsite.cnlab-switch.ch: 62 %
sunet.se: 44 %
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)
aeneas.mit.edu: 86 %
dc.aleron.net: 58 %
An unacceptable level of packet loss has been detected which should be investigated.
End of testing.
This report was collated using Dan Elwell's Broadband Speed Test. For more information or to download, please visit www.broadbandspeedtest.net.
Generated 20/09/2004 20:02:30 using test version 3.0.316 - registered copy