PDA

View Full Version : Poor d/l's in Luton


MisterPie
20-10-2004, 22:49
I'm seeing some really strange behaviour on my NTL 750kbs BB in the MK45 area.

Downloads speed along fine for between 1-5 secs then stop for 30-60 before bursting along again for another few secs.
This happens on HTTP, FTP and newsgroups.
I've read on here that some US sites are unavailable due to a pipe fault, but this has been going on for a week or so now.
Web pages are not found, or connections are refused, but a few dozen refreshes and a cuppa normally sorts that out.... as in the pages eventually load :-(

Anybody else seen similar behaviour?

Here's some pings and trace routes to www.bbc.co.uk

Pinging www.bbc.net.uk [212.58.224.121] with 32 bytes of data:

Reply from 212.58.224.121: bytes=32 time=36ms TTL=245
Reply from 212.58.224.121: bytes=32 time=13ms TTL=245
Reply from 212.58.224.121: bytes=32 time=13ms TTL=245
Reply from 212.58.224.121: bytes=32 time=12ms TTL=245

Tracing route to www.bbc.net.uk [212.58.224.121]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 11 ms 8 ms 7 ms 10.139.xxx.xxx
3 8 ms 10 ms 13 ms lutn-t2cam1-a-v113.inet.ntl.com [80.4.118.17]
4 12 ms 11 ms 10 ms lutn-t2core-a-ge-wan64.inet.ntl.com [213.107.47.89]
5 10 ms 12 ms 10 ms pop-bb-a-so-300-0.inet.ntl.com [62.253.188.185]

6 53 ms 36 ms 77 ms tele-ic-2-so-000-0.inet.ntl.com [62.253.185.86]

7 14 ms 14 ms 14 ms 212.58.239.217
8 12 ms 12 ms 12 ms 212.58.238.153
9 14 ms 12 ms 11 ms www21.thdo.bbc.co.uk [212.58.224.121]

Trace complete.

Heres a speed test from Robin Walkers site which shows the problem quite nicely:-

Wed, 20 Oct 2004 20:39:37 GMT
1st 128K took 1469 ms = 89225 Bytes/sec = approx 742 kbits/sec
2nd 128K took 68922 ms = 1902 Bytes/sec = approx 16 kbits/sec
3rd 128K took 33437 ms = 3920 Bytes/sec = approx 33 kbits/sec
4th 128K took 1453 ms = 90208 Bytes/sec = approx 751 kbits/sec

I've tried all the usual things such as reboot the modem and router, disabled Norton firewall, I've even connected the modem (Terayon TJ210) via USB incase my router was hosed or been haxored (Linksys WRT54G)

Any ideas, suggestions or help is greatly appreciated.

Thanks.

bontrager
20-10-2004, 23:23
yeah im on the luton-hatfield UBR and im also having problems at the moment. happened since the upgrade, i guess its just saturated them all. Give the support folk a ring so it can be noted etc. :( not much else you can do really..

paulyoung666
21-10-2004, 00:09
hi and :welcome: to the site MisterPie , have you tried specifying a proxy to see if that helps , try here (http://www.cableforum.co.uk/kb/84/list-of-ntl-proxy-servers-new-format) port 8080 for any of them :)

Ignition
21-10-2004, 00:27
I'm seeing some really strange behaviour on my NTL 750kbs BB in the MK45 area.

Downloads speed along fine for between 1-5 secs then stop for 30-60 before bursting along again for another few secs.
This happens on HTTP, FTP and newsgroups.

Yip, give me your IP address will see what I can do.

MisterPie
21-10-2004, 10:47
Yip, give me your IP address will see what I can do.
PM sent, thanks.

I've ran Dan Elwells Broadband Speed Test (http://www.broadbandspeedtest.net/) a few times.
The results vary, but I think thatâ₠¬Ã¢â€žÂ¢s a function of the bursty d/ls...
Results seem to indicate horrendous packet loss....?

Test 1: Ping times to UK servers
Ideally, you should get a result of around 30 ms (lower is better)
mirror.ac.uk: This test failed due to a server timeout or other error.
broadbandspeedtest.co.uk: 15.3 ms
zeniiia.linux.org.uk: 18.5 ms
0800dial.com: 27.5 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)
uni-kl.de: 45 ms
fi.udc.es: This test failed due to a server timeout or other error.
fi.udc.es: This test failed due to a server timeout or other error.
fi.udc.es: This test failed due to a server timeout or other error.

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)
the-city.seas.upenn.edu: 87.8 ms
club.cc.cmu.edu: 95.5 ms
mirror.cc.vt.edu: 115.8 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)
mirror.chpc.utah.edu: 142 ms
ucsb.edu: 159 ms
limestone.uoregon.edu: 163 ms
cybertrails.com: 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)
meisei-u.ac.jp: 280.3 ms
meisei-u.ac.jp: 283 ms
meisei-u.ac.jp: 278.5 ms
apache-kr.org: 305.8 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)
mirror.pacific.net.au: 423 ms
ains.net.au: 341.7 ms
apache.planetmirror.com.au: 382.5 ms
apache.inspire.net.nz: 306.3 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: 372.5 ms
apache.oss.eznetsols.org: 369 ms
apache.fresh.co.il: 375.7 ms
opensourcecommunity.ph: 368 ms

Your ping times are slightly poorer than expected.

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)
mozilla.sk: 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)
64.12.168.21: 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)
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)
london.gov.uk: 44 %
cardiff.ac.uk: 40 %
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)
univie.ac.at: 2 %
tux.cprm.net: 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)
cs.columbia.edu: 26 %
club.cc.cmu.edu: 14 %
An unacceptable level of packet loss has been detected which should be investigated.

End of testing.

MisterPie
21-10-2004, 10:49
have you tried specifying a proxy to see if that helps , try here (http://www.cableforum.co.uk/kb/84/list-of-ntl-proxy-servers-new-format) port 8080 for any of them :)

I haven't yet, but I'll give it a go when I get home tonight. cheers

MisterPie
29-10-2004, 11:23
Well despite the planned maintenance - re-segmentation, ubr load balancing etc I'm still having problems.
Specifying a new proxy was funny... Firefox pops up saying the specified Proxy cannot be found, rather than page not found. lol :mad: