[Zodd]

Hi all,

I'm also in the ST5 area and too wondering whats happening to this service !!

Getting lots of dropped packets and very poor http performance. Have changed proxy, DNS and everthing else I could think of that may help to no avail. Seems to be getting worse though.

Heres my Dan Elwell's Broadband Speed Test results:

Test conducted at: 06/12/2005 00:02:20
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.net: 20 ms
vantage.myby.co.uk: 19.5 ms
broadbandspeedtest.co.uk: 17 ms
clara.net: 18 ms

The results of this test indicate no problems.

Test 2: Ping times to European servers

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

belnet.be: 39.7 ms
uvsq.fr: 36.7 ms
sunsite.cnlab-switch.ch: 46.5 ms
tu-berlin.de: 47.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: 100.5 ms
dulug.duke.edu: 96.5 ms
rutgers.edu: 109.8 ms
dulug.duke.edu: 98 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)

mirrors.usc.edu: 153 ms
stanford.edu: 160.5 ms
oregonstate.edu: 129.5 ms
uconn.edu: 95 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)

apache-kr.org: 311.7 ms
apache-kr.org: 315.5 ms
zentek-international.com: 319 ms
apache-kr.org: 313.5 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)

planetmirror.com: 332 ms
froggy.com.au: 391.5 ms
apache.inspire.net.nz: 476 ms
apache.inspire.net.nz: 496 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.dnepr.net: 79 ms
apache.rinet.ru: 73.5 ms
apache.dnepr.net: 76.3 ms
apache.fresh.co.il: 153.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 2000 Kb/s (higher is better)

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

Your download speeds are slightly poorer than expected.

Test 9: Download speeds from European servers

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

oleane.net: 1088 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 2000 Kb/s (higher is better)

mirrors.ccs.neu.edu: 1316 Kb/s

This result is much poorer than expected and should be investigated.

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)

f2s.com: 26 %
bristol.ac.uk: 14 %

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)

gmd.de: 12 %
gmd.de: 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)

rutgers.edu: 10 %
ibiblio.org: 24 %

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

End of testing.


Very very poor.

Hope NTL get their finger out and sort this ASAP.