If no audible noise can be heard, no point in reporting a ptsn voice fault, but if you have changed the router, adsl lead ,filter, and it still drops out when in the test socket, then there is a fault somewhere and it isn't in your home, so open reach couldn't say fault with customers wiring or router ect

Edited by tommy45 (Mon 07-Jun-10 04:27:37)

I have just been speaking to a neighbour on the same Exchange as me and she has had no internet at all since Thursday she lives 1 mile SW from me and is closer to the exchange she works 2 miles north of me also on the same exchange and has very slow Broadband and she knows of many others one who had been convinced by BT that the fault was in her computer and she even took it to be repaired .

It looks as if it is still a common fault in the area and is the same one that started over 2 weeks since and BT are still telling ISP's that there is no fault and sending engineers out to test individual lines but the results always come back no fault on the line .

The engineers that are sent out to do these tests are not allowed access to the exchange to investigate further so I don't think I will be booking an appointment to have my line checked because this confirms what I heard over a week since that the fault was widespread .

Is there any way in which collective evidence could be used to make BT act on this .

An email to the office of the CEO often gets results.

In this case I would suggest trying to seperate your IP connectivity problems from the actual line aspects which BT control.

I presume you've done the usual test of plugging router straight into master socket.

If so I'd then see if you can get any adsl line stats out of your router -- this will vary by router but should give figures on sync speed, noise margins, error rates. There are a variety of tools such as "RouterStats" which will log/graph these figures.

If those stats look fine then the issue is almost definately not in OpenReach's domain - it's either your kit (suggest trying different end device/pc + alternate router borrowed?) or the ISP's kit/backhaul/network.

Which ISP is it? Is it LLU?

In reply to a post by planetf1:

In this case I would suggest trying to seperate your IP connectivity problems from the actual line aspects which BT control.

I presume you've done the usual test of plugging router straight into master socket.

If so I'd then see if you can get any adsl line stats out of your router -- this will vary by router but should give figures on sync speed, noise margins, error rates. There are a variety of tools such as "RouterStats" which will log/graph these figures.

If those stats look fine then the issue is almost definately not in OpenReach's domain - it's either your kit (suggest trying different end device/pc + alternate router borrowed?) or the ISP's kit/backhaul/network.

Which ISP is it? Is it LLU?

I've done all the checks 2 different routers in the test socket 3 different computers line stats have been good same as normal 8128 line rate .

It's not LLU isp newnet but many people are affected by this some BT customers some other isp's.

Do ISP's maintain the kit in the exchange at this end or is it shared .

If the stats are consistently good, then it doesn't seem likely it's a line problem that could be found/fixed by BT OpenReach as this would be reflected in stats from the router

If non-LLU then the kit that terminates your ADSL connection will be a BT wholesale managed DSLAM.

If both you & other customers are affected by slowdowns then it would suggest to me that the BT wholesale links from the exchange are overloaded - or that the DSLAM/line cards are faulty-- the ISP should be able to chase this.

Personally I'd not got for SFI. I don't have experience of the process, but it seems they would not find a fault and you could get charged.

I'd contact/push ISP, and in parallel consider writing direct to BT as someone else suggested, see if you can at least get some information out of BTw?

Edited by planetf1 (Wed 09-Jun-10 14:07:16)

I wonder if you've been switched to 21CN?

In reply to a post by Deadbeat:

I wonder if you've been switched to 21CN?

I think that's years off.