Yeah its kinda annoying, but am sure the engineers will sort it soon ( hope so )
Test 1: Ping times to UK servers
Ideally, you should get a result of around 30 ms (lower is better)
bbc.co.uk: 26.8 ms
london.gov.uk: This test failed due to a server timeout or other error.
gnu.teleglobe.net: 124.5 ms
vantage.myby.co.uk: 18.8 ms
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)
free.fr: 35.3 ms
free.fr: 37.3 ms
lycos.es: 54.5 ms
rediris.es: 66.8 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)
ibiblio.org: 132.8 ms
mirrors.ptd.net: 98.3 ms
mirror.nocservices.com: 157.5 ms
the-city.seas.upenn.edu: 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)
stanford.edu: This test failed due to a server timeout or other error.
mirrors.usc.edu: 154 ms
cybertrails.com: 156.5 ms
mirror.ats.ucla.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)
apache.netsolutions.com.hk: 296 ms
apache-kr.org: 348 ms
apache.oss.eznetsols.org: 341 ms
meisei-u.ac.jp: 261 ms
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)
froggy.com.au: 398.3 ms
froggy.com.au: 398.3 ms
bondinet.com: 317 ms
bondinet.com: 330 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.officepark.ru: This test failed due to a server timeout or other error.
apache.fresh.co.il: 109.8 ms
apache.rinet.ru: 77.8 ms
apache.dnepr.net: 80.3 ms
The results of this test indicate no problems.
Test 8: Download speeds from UK servers
Ideally, you should get a result of around 3072 Kb/s (higher is better)
mirrorservice.org: 4955 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 3072 Kb/s (higher is better)
fr2.rpmfind.net: 6256 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 3072 Kb/s (higher is better)
reverse.net: 7019 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 300 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)
plig.net: 0 %
bristol.ac.uk: 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)
sunsite.cnlab-switch.ch: 2 %
sunsite.cnlab-switch.ch: 0 %
A small amount of packet loss has been detected. This 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)
the-city.seas.upenn.edu: This test failed due to a server timeout or other error.
mirror.cc.vt.edu: 30 %
An unacceptable level of packet loss has been detected which should be investigated.
---------- Post added at 19:54 ---------- Previous post was at 19:52 ----------
sorry for the massive post - seems this time my packet loss was quite low in comparison.
@grubbymitts: thanks for the heads up .. testing it now
