So No 26 could not now order FTTC but in actual fact has 2 connections? Other addresses that have fibre have the same issue. One gets 38 Mbs, I keep saying this, but they are facts because we are not too far away from the new cabinet. Just assume that everything I have posted in the thread is fact for a moment, the checkers are only as good as the data fed into them. What could have changed so that addresses that it once felt could get FTTC can no longer?

Edited by deleted (Mon 11-Jan-16 17:13:14)

CCXO who 1st replied to you will be the poster with local knowledge for you.

My earlier post is from the results of that link, using the postcode in the Address options then selecting each entry in turn.

I didn't put a link Bob ??

True. I assume the poster of it lives near there, from what your say, but the link in their post is what I was referring to. So it would need to be information that contradicts that checker.

In reply to a post by APH999:

What could have changed so that addresses that it once felt could get FTTC can no longer?

You answer that question yourself.

You mention the facts about what is connected where, and then state

In reply to a post by APH999:

the checkers are only as good as the data fed into them.

This is the answer ... the data being fed into the checker must have changed, and must now fail to match the reality of "the facts" you mentioned.

The database within Openreach is probably known as ROSE, and represents their understanding of the physical world. When I moved home 18 months ago, a surveyor checked for an existing line ... but put the wrong cab number into the database.

Simple mistake, and easy to understand - the property is right next to that cab, and the rest of the street use it. Unfortunately, the property was actually wired into the cab in the next street. Just a 21 instead of a 20.

Unfortunately, the order for FTTC took nearly 4 months to get sorted, just to get that cabinet number changed. Without it, the FTTC back-office system kept allocating a port in the wrong FTTC cabinet.

Getting the order through required numerous visits from Openreach and Kelly's engineers; mostly fruitless. It took constant effort from the ISP to escalate through BTW into Openreach - and eventually got some traction when an engineer was allocated to do a "pair prove", which was then fed back into the ROSE database.

The important thing in your case is that you mention this ...

In reply to a post by APH999:

So Cab 2 is closer to a mile away at the far end of the village. This was the our local cabinet until autumn last year. I assume most of the estate still remain connected there - the engineer said there were only 7 connections to the new cab 12.

I have noticed no recent connection speed change, so assume I am still connected to Cab 2.

It sounds like Openreach have gone through a process of "copper re-arrangement", which is relatively rare, and seems to be fraught with difficulty as far as getting the database updates correct.

However, if Openreach have really done a re-arrangement, you have to ask both *why* and *who for*.

On "why": Obviously to shorten copper lines, to make broadband speeds better - usually where lines are too long to get service elsewhere, or on EO lines that have no cabinet option.

On "who for": The answer is NOT "just for those ordering FTTC". Openreach do not have a system that allows you (on cab 2) to order FTTC, and for your line to be subsequently moved to cab 12.

Instead, Openreach run a process to first cut your line over physically, then update their internal databases to match, then to make estimates of your FTTC capability, then to allow you to order.

It sounds like you've hit the problem that either a) Your line hasn't physically been moved to cab 12; or b) the database updates haven't gone through, and need to be chased.

Edit: Typical! After writing all that ... I used the information from PaulKirby's last post in the DSL checker again, and can see that the checker is now reporting a connection to cab 12, with decent FTTC estimates.

Properties 27-31 remain on cab 2, though. Physical reality, or is the database still wrong for them?

Edited by deleted (Sat 16-Jan-16 12:30:28)

I think it will be physical reality. All the Cab 12's now have high estimates, whereas at the time of my earlier post they had none.

Thanks Wombat for your long post it was appreciated and thanks Robert and everyone else who has taken the time and trouble to post. I did feel confident that this was an "admin" error.There were at least two of us applying pressure through our ISP's to get it sorted and another existing user was in constant contact with Openreach over connection speed issues, so somehow one of us has got through to BT.

Just to clarify the situation (for me) this is just a logical/dbase change isn't it? I haven't seen vans near the cabinet or noticed any disruption/change to my current service. I only ask because it came to my attention yesterday that another neighbour has been told he cant be connected to cab12 as its full!

Thanks

Andy

Hi Andy, after BT have physically moved/rerouted the copper connections (copper rearrangement) to the new cabinet and the cab is powered up and active, then the rest is a database change and updating their reocrds before anyone can physically order fibre from that cabinet.

This is happening to quite a few people here in Cumbria too in the later stages of the Phase 1 rollout. I myself am on Cabinet 1 but almost too far for FTTC (estimated 10 Mbps download), however a new Cabinet 3 has been built much closer to me. However Cab 3 is not activated yet (On the 'Connect' stage), the connections haven't been moved over yet and the ADSL Wholesale checker still shows I am connected to Cab 1. I'm holding fire before ordering as I've been promised by Connecting Cumbria that I will be connected to Cabinet 3. These things just take time I guess but of course the situation has been causing quite a lot of confusion locally.

Edited by deleted (Mon 18-Jan-16 12:13:29)