racingbrett
15-11-2007, 23:08
Iv had it and virgin have had enough chances now. for 8 months iv had nothing but problems and an unusable connection, im on the 8mb package upgraded (as they put it) to the 2mb package, moved house and got put back on the 8 mb package after being assured there was a note on my acc to say i was to be kept on the 2mb package and no matter what they give or where i go the connection is appalling and unusable, im planning on talking to trading standards and then im going for a small claims court case, i want my money back and no doubt about it, they sold me an 8mb ADSL package and they are providing the equivalent to dial up and ISDN at the best of times.
Test conducted at: 15/11/2007 20:23:27
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: 203.3 ms
mirror.public-internet.co.uk: This test failed due to a server timeout or other error.
bris.ac.uk: 204.5 ms
mirrors.dedipower.com: This test failed due to a server timeout or other error.
This result shows serious problems with your ping times, and should be investigated.
Test 2: Ping times to European servers
Ideally, you should get a result of around 50 ms (lower is better)
mir2.ovh.net: This test failed due to a server timeout or other error.
apache.belnet.be: This test failed due to a server timeout or other error.
apache.easy-webs.de: This test failed due to a server timeout or other error.
uni-erlangen.de: 221.7 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)
eng.lsu.edu: This test failed due to a server timeout or other error.
apache.mirrors.hoobly.com: 303 ms
apache.edgescape.com: This test failed due to a server timeout or other error.
less.cogeco.net: This test failed due to a server timeout or other error.
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)
apache.cs.utah.edu: 342 ms
download.nextag.com: 372.5 ms
mirror.stanford.edu: This test failed due to a server timeout or other error.
uci.edu: 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)
riken.jp: 448 ms
apache.cbn.net.id: This test failed due to a server timeout or other error.
apache.hkmirror.org: This test failed due to a server timeout or other error.
download.stmc.edu.hk: 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)
public.planetmirror.com.au: This test failed due to a server timeout or other error.
mirror.optus.net: This test failed due to a server timeout or other error.
public.planetmirror.com.au: This test failed due to a server timeout or other error.
public.planetmirror.com.au: This test failed due to a server timeout or other error.
Too many server errors occurred therefore this test is inconclusive.
Test 7: Ping times to central Asian servers
Ideally, you should get a result of around 300 ms (lower is better)
mirror.tw: 493 ms
apache.cdpa.nsysu.edu.tw: 489.7 ms
mirror.tw: 491.5 ms
apache.oss.eznetsols.org: This test failed due to a server timeout or other error.
Your ping times are slightly poorer than expected.
Test 8: Download speeds from UK servers
Ideally, you should get a result of around 8000 Kb/s (higher is better)
hensa.ac.uk: 52 Kb/s
This result shows serious problems with your downloads, and should be investigated.
Test 9: Download speeds from European servers
Ideally, you should get a result of around 8000 Kb/s (higher is better)
apache.crihan.fr: 55 Kb/s
This result shows serious problems with your downloads, and should be investigated.
Test 10: Download speeds from east-coast USA servers
Ideally, you should get a result of around 8000 Kb/s (higher is better)
apache.mirror99.com: 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 512 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)
mirrorservice.org: This test failed due to a server timeout or other error.
zeniiia.linux.org.uk: 18 %
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)
apache.miroir-francais.fr: 10 %
apache.belnet.be: 20 %
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)
apache.mirrors.northco.net: This test failed due to a server timeout or other error.
apache.mirrors.northco.net: This test failed due to a server timeout or other error.
Too many server errors occurred therefore this test is inconclusive.
End of testing.
and this is one of there better results. un-usable , why do we all put up with there poor service and connections, im sick and tired of it all.
Test 1: 1024K took 34437 ms = 29.7 KB/sec, approx 245 Kbps, 0.24 Mbps
Test 2: 1024K took 41703 ms = 24.6 KB/sec, approx 203 Kbps, 0.2 Mbps
Test 3: 1024K took 45172 ms = 22.7 KB/sec, approx 187 Kbps, 0.18 Mbps
Test 4: 2048K took 78219 ms = 26.2 KB/sec, approx 216 Kbps, 0.21 Mbps
Test conducted at: 15/11/2007 20:23:27
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: 203.3 ms
mirror.public-internet.co.uk: This test failed due to a server timeout or other error.
bris.ac.uk: 204.5 ms
mirrors.dedipower.com: This test failed due to a server timeout or other error.
This result shows serious problems with your ping times, and should be investigated.
Test 2: Ping times to European servers
Ideally, you should get a result of around 50 ms (lower is better)
mir2.ovh.net: This test failed due to a server timeout or other error.
apache.belnet.be: This test failed due to a server timeout or other error.
apache.easy-webs.de: This test failed due to a server timeout or other error.
uni-erlangen.de: 221.7 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)
eng.lsu.edu: This test failed due to a server timeout or other error.
apache.mirrors.hoobly.com: 303 ms
apache.edgescape.com: This test failed due to a server timeout or other error.
less.cogeco.net: This test failed due to a server timeout or other error.
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)
apache.cs.utah.edu: 342 ms
download.nextag.com: 372.5 ms
mirror.stanford.edu: This test failed due to a server timeout or other error.
uci.edu: 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)
riken.jp: 448 ms
apache.cbn.net.id: This test failed due to a server timeout or other error.
apache.hkmirror.org: This test failed due to a server timeout or other error.
download.stmc.edu.hk: 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)
public.planetmirror.com.au: This test failed due to a server timeout or other error.
mirror.optus.net: This test failed due to a server timeout or other error.
public.planetmirror.com.au: This test failed due to a server timeout or other error.
public.planetmirror.com.au: This test failed due to a server timeout or other error.
Too many server errors occurred therefore this test is inconclusive.
Test 7: Ping times to central Asian servers
Ideally, you should get a result of around 300 ms (lower is better)
mirror.tw: 493 ms
apache.cdpa.nsysu.edu.tw: 489.7 ms
mirror.tw: 491.5 ms
apache.oss.eznetsols.org: This test failed due to a server timeout or other error.
Your ping times are slightly poorer than expected.
Test 8: Download speeds from UK servers
Ideally, you should get a result of around 8000 Kb/s (higher is better)
hensa.ac.uk: 52 Kb/s
This result shows serious problems with your downloads, and should be investigated.
Test 9: Download speeds from European servers
Ideally, you should get a result of around 8000 Kb/s (higher is better)
apache.crihan.fr: 55 Kb/s
This result shows serious problems with your downloads, and should be investigated.
Test 10: Download speeds from east-coast USA servers
Ideally, you should get a result of around 8000 Kb/s (higher is better)
apache.mirror99.com: 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 512 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)
mirrorservice.org: This test failed due to a server timeout or other error.
zeniiia.linux.org.uk: 18 %
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)
apache.miroir-francais.fr: 10 %
apache.belnet.be: 20 %
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)
apache.mirrors.northco.net: This test failed due to a server timeout or other error.
apache.mirrors.northco.net: This test failed due to a server timeout or other error.
Too many server errors occurred therefore this test is inconclusive.
End of testing.
and this is one of there better results. un-usable , why do we all put up with there poor service and connections, im sick and tired of it all.
Test 1: 1024K took 34437 ms = 29.7 KB/sec, approx 245 Kbps, 0.24 Mbps
Test 2: 1024K took 41703 ms = 24.6 KB/sec, approx 203 Kbps, 0.2 Mbps
Test 3: 1024K took 45172 ms = 22.7 KB/sec, approx 187 Kbps, 0.18 Mbps
Test 4: 2048K took 78219 ms = 26.2 KB/sec, approx 216 Kbps, 0.21 Mbps