Lots and lots of timeout errors
 

Not actually sure if this is down to NTL or something else but i've recently been getting loads of timeout errors. I seem to get them constantly when using ebay and on a fairly regular basis whilst just browsing. It's been happening for about a week now and shows no signs of stopping.

I never got any similar types of problems when i was with virgin BB before NTL or BT before that.

Anyone got any suggestions on where I should start looking?

Re: Lots and lots of timeout errors
 

I am getting similar problems in the ST5 area.

intermittant although in general not good.

averaging from 10% to 40% packet loss, obviously when it gets towards the high scale my internet becomes unuable for anything but a very flakey messenger service. ( icq msn or yahoo )

Re: Lots and lots of timeout errors
 

Have either of you tried changing the proxy you are using? Could be that the proxys you are using currently are having problems.
Also you could try a trace route to check your connection to sites. When it gets really bad though I would suggest calling Tech Support so they can check your levels etc.

Re: Lots and lots of timeout errors
 

I have had two engineer visits in 2 days, my levels are fine.

I have tried changing my proxy and it gets no better; in fact when its bad it actually seems to get worse.

Had a modem swap too.

Running Daniel Elwells speedtest thingy now and will post reults.

Re: Lots and lots of timeout errors
 

We had a similar problem last week, turned out to be local fault which took 2 days to fix. What operating system are you running? If possible, next time it goes bad, try running a tracert/ trace route to a site like www.bbc.co.uk or www.google.co.uk and post the results.
Easiest way in Windows XP is to open start menu and select run and then type
cmd
then in the dos box that opens type
tracert www.bbc.co.uk>c:/trace.txt
this will run a trace to www.bbc.co.uk and then output the result to a file in your C drive called trace. You can either attach that here or copy and paste the results into a post.

Re: Lots and lots of timeout errors
 

Got that here in ST5 area too. Using the Ashford proxy asfd-cache-1.server.ntli.net seems to get it working faster. Baguley proxy, which we're on, has been crap for a while now.

Re: Lots and lots of timeout errors
 

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 :)

Re: Lots and lots of timeout errors
 

Getting worse again .... so here we go


tracert www.google.com

Tracing route to www.l.google.com [66.102.9.104]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms 192.168.2.1
2 7 ms 7 ms 15 ms 10.49.160.1
3 9 ms 13 ms 25 ms bagu-t2cam1-b-ge-wan44-115.inet.ntl.com [80.5.16
2.189]
4 11 ms 37 ms * bagu-t2core-b-ge-wan61.inet.ntl.com [80.5.161.12
9]
5 19 ms 9 ms 30 ms lee-bb-b-so-300-0.inet.ntl.com [62.253.188.29]
6 * * 20 ms lee-bb-a-ae0-0.inet.ntl.com [62.253.187.185]
7 14 ms * * nth-bb-b-so-000-0.inet.ntl.com [62.253.185.101]

8 * 24 ms 16 ms tele-ic-1-so-700-0.inet.ntl.com [62.253.184.2]
9 16 ms 15 ms 24 ms 212.250.14.66
10 28 ms * 20 ms 72.14.238.240
11 * 63 ms 38 ms 216.239.49.254
12 52 ms 37 ms 36 ms 64.233.174.42
13 30 ms 38 ms * 64.233.174.14
14 52 ms * 75 ms 66.102.9.104

Trace complete.

two words - Bloody rediculous !

NTL can ram this cr4p up their a$$

Although webpages now work intermittently - the times when they do work it takes at least a minute to open pages. Pathetic - Broaband ? i think not.

/me goes off to connect by GPRS and will have better speeds than this supposed 10mb

Re: Lots and lots of timeout errors
 

my brother-in-law who lives in the next street to me in the ST5 area is having an awful time of it - his modem has been down for three days.

Re: Lots and lots of timeout errors
 

Same here, happend since I changed my router over.
My old Linskys WRT54G gave up and died, so replaced it with another WRT54G (newer version thats all).

Was convinced was the router, but kept settings the same.
Skysports page ok but select team page never loads.
eBay, no chance at all times out.

This is what I get:

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

1 1 ms <1 ms <1 ms www26.thdo.bbc.co.uk [212.58.224.126]
2 21 ms 8 ms 11 ms 10.145.231.254
3 103 ms 23 ms 25 ms nott-t2cam1-a-v122.inet.ntl.com [80.4.46.69]
4 10 ms 9 ms 11 ms nott-t2core-a-ge-wan73.inet.ntl.com [80.1.79.77]
5 14 ms 29 ms 14 ms nott-t2core-b-ge-wan91.inet.ntl.com [80.1.79.2]
6 13 ms 11 ms 12 ms nth-bb-b-so-200-0.inet.ntl.com [62.253.185.37]
7 34 ms 11 ms 27 ms nth-bb-a-ae0-0.inet.ntl.com [62.253.185.117]
8 15 ms 16 ms 16 ms gfd-bb-b-so-400-0.inet.ntl.com [62.253.185.98]
9 18 ms 15 ms 16 ms redb-ic-1-as0-0.inet.ntl.com [213.105.174.138]
10 98 ms 112 ms 18 ms 212.58.238.189
11 18 ms 15 ms 15 ms 212.58.238.133
12 20 ms 18 ms 17 ms www26.thdo.bbc.co.uk [212.58.224.126]

Trace complete.

www.ebay.co.uk:
Tracing route to hp-intl-uk.ebay.com [66.135.192.78]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms hp-intl-uk.ebay.com [66.135.192.78]
2 9 ms 10 ms 12 ms 10.145.231.254
3 108 ms 38 ms 24 ms nott-t2cam1-b-v122.inet.ntl.com [80.4.46.201]
4 10 ms 13 ms 9 ms nott-t2core-b-ge-wan72.inet.ntl.com [80.1.79.189]
5 12 ms 18 ms 12 ms nth-bb-b-so-300-0.inet.ntl.com [62.253.188.37]
6 13 ms 15 ms 76 ms pop-bb-a-so-100-0.inet.ntl.com [213.105.172.14]
7 15 ms 14 ms 15 ms 195.50.91.69
8 15 ms 14 ms 12 ms ae-0-54.bbr2.London1.Level3.net [212.187.131.146]
9 156 ms 155 ms 183 ms as-0-0.bbr1.SanJose1.Level3.net [64.159.1.133]
10 155 ms 154 ms 156 ms ge-10-2.ipcolo2.SanJose1.Level3.net [4.68.123.138]
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.

So this means? :dunce:

Also downloading from EasyNews is a no no, never goes above 50-80k (on 10Mbit ntl:250
) used to be fine but again around the same time (4 weeks) ago all just died.

Thanks in advance.

Re: Lots and lots of timeout errors
 

Well its just taken me maybe 15 minutes to get to this page and log in, This packet loss is completely crippling my connection.

Done three pings to google.com ( or co.uk .. cant remember now )

here are the Shameful results.

Test1
Ping statistics for 66.102.9.99:
Packets: Sent = 10, Received = 7, Lost = 3 (30% loss),
Approximate round trip times in milli-seconds:
Minimum = 26ms, Maximum = 50ms, Average = 38ms

Test2
Ping statistics for 66.102.9.104:
Packets: Sent = 10, Received = 6, Lost = 4 (40% loss),
Approximate round trip times in milli-seconds:
Minimum = 27ms, Maximum = 38ms, Average = 31ms

Test3 (increased the count of pings to 25 to be fair )
Ping statistics for 66.102.9.104:
Packets: Sent = 25, Received = 14, Lost = 11 (44% loss),
Approximate round trip times in milli-seconds:
Minimum = 26ms, Maximum = 71ms, Average = 39ms


Have so far:
Called NTL
Had two engineer visits
Had new modem

Just for fun also:
connected laptop directly to cable modem
upgraded firmware in belkin router
completely removed all security from my wireless internet


not sure if this is 3 or 4 days of seriously no internet now; one thing is for sure that the next engineer that arrives either fixes it or takes the cable modem away with him.

Re: Lots and lots of timeout errors
 

Is anyone in the RM6 area having trobules browsing, for the last copule of mins, it has been going very slow, and keeps timing out

Re: Lots and lots of timeout errors
 

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.

Re: Lots and lots of timeout errors
 

"Hope NTL get their finger out and sort this ASAP."

- Damn right. ST5 area connection is a bloody pain in the butt at the mo. D/L from newsgroups fine, but surfing - hit and miss

Re: Lots and lots of timeout errors
 

The wife tells me that my latest engineer visit was cancelled the other day ( although i wasnt phone and told ) becouse apparently its a known area problem.

Funny thing is that there is no mention of it on the service status page.


I noticed last night was comparitively good with ping loss less than 15%

Is anybody else noticing anything ?