very poor in reading RG10
 

Yo all..

Very slow browing, up to 40% packet loss in the reading area. The normal checks completed (proxy, restart etc etc).

Anyone else finding this. I thought this was just to US sites - but even this site takes an age to load....

MArk

Re: very poor in reading RG10
 

I'm also noticing this especially when using eMeeting packages like Centra - is it my imagination or did this start back in mid-August when my connection was upgraded to 750kb? I'm in RG12 area......

Anyone else finding this?

czb

Re: very poor in reading RG10
 

not directly applicable as in not in reading, but my service has gone through the floor in hatfield since the upgrades. Im now not even getting a 1mb service, let alone 1.5mb! anyway, on the phone as i type to register my poor service to get a refund...

Re: very poor in reading RG10
 

I'm in RG10 and I'm seeing the same problem.

My connection just came back after having lost it for about 15 minutes.

Re: very poor in reading RG10
 

Hi Mark. This site (cableforum.co.uk) is hosted in the US too. Thats why it will be slow as well.

Re: very poor in reading RG10
 

Well, I haven't been able to load the NTL status page since Friday. I would assume that site is not in the US!

Re: very poor in reading RG10
 

I was going to suggest Learn Direct :D

Re: very poor in reading RG10
 

I've just checked from work and I don't see anything on the status page about this.

Here's the results of a traceroute to the status page, if that gives anyone an idea of the problem:

$ /usr/sbin/traceroute www.ntl-isp.ntl.com
traceroute to www.ntl-isp.ntl.com (212.250.5.117), 30 hops max, 38 byte packets
1 10.152.95.254 (10.152.95.254) 13.173 ms 13.261 ms 12.222 ms
2 rdng-t2cam1-b-ge94.inet.ntl.com (62.253.122.137) 11.966 ms 10.551 ms 10.540 ms
3 winn-t2core-b-ge-wan61.inet.ntl.com (62.253.121.129) 15.249 ms 15.540 ms 12.050 ms
4 win-bb-b-so-320-0.inet.ntl.com (62.253.184.117) 12.270 ms 12.120 ms 12.406 ms
5 bre-bb-a-so-100-0.inet.ntl.com (62.253.185.197) 12.721 ms 12.968 ms 12.027 ms
6 gfd-bb-b-so-700-0.inet.ntl.com (213.105.172.150) 12.809 ms 21.267 ms 45.239 ms
7 gfd-dc-d-v301.inet.ntl.com (213.105.172.181) 14.049 ms 12.091 ms 12.113 ms
8 gfd-alder-fa10.inet.ntl.com (194.168.121.2) 15.732 ms 13.761 ms 18.628 ms
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *

Re: very poor in reading RG10
 

I'm in RG10 and have been suffering intermittent 'drop outs' on my broadband NTL BB box for at least 3 months. We had this before and the tech who visited 'remade' some connections... however, the real problem was the green box down the road that sat with doors open letting in the rain. It took NTL three weeks to fix that one.
Just lately I've had a new BB box and a sympathetic tech. visit twice, with no drop outs during his visit. Most of the drop outs occur late in the evening (yes I have a line attenuator) which is when BB support is closed. Now they refuse to send out another tech... - BTW when I run Dan Elwells BBspeed test I also see packet loss probs...
I 'phoned and told CS this evening that I'm getting fed up and might change to another supplier - she promised to get me throught to 'faults', then while holding for 'faults' got cut off at the stroke of 8pm...:disturbd:

Broadband probs in Reading area
 

NTL just failed to turn up again.
That's two days I've taken off work. We have intermittent broadband (rdy light just goes out for a minute or two each time).
This has been going on for three months.
'Faults' told me that appointment 1 was cancelled and moved to this morning. Today they told me it's been cancelled again, without reason.:mad:

Assuming that I 'sack' NTL, who should I sign up with?

Re: Broadband probs in Reading area
 

Merged with the existing RG10 thread. :)

Re: [Merged] very poor in reading RG10
 

Update...

Two other NTL customers in my street have problems. One put it down to having a USB modem connection (and is still waiting for NTL to call back) and the other thought they had a virus problem and has just bought new anti-virus software.

I'll be lucky if I can post this before it cuts off again, so sorry for typos...

I called 'Head Office' in Hook and spoke to Douglas - I got a months credit, but basically gave them 7 days to sort it out...

Re: [Merged] very poor in reading RG10
 

Network tech was out today... he told me he'd changed amplifiers, etc.

BBST now checks out OK (no packet loss!).

It took 3 months to get a fix, but I'm still not holding my breath...