|
|
So, after seeing lots of Openreach vans around recently, I decided to check on the status of fibre availability of my building. To my surprise it was available, and I decided to place an order with Plusnet.
Fast forward a week and Plusnet have had the order cancelled several times, with the last time getting a reason back that my line is EO.
Checking my full address on the ADSL Checker shows I'm connected to a cabinet that's just 10 meters away from my block of flats. I cannot check the phone number because it's currently with Sky.
FWIW, the checker didn't used to say a cabinet number - is it possible BT have moved the building to the PCP to enable FTTC?
Where do I go from here? Which one is more likely to be wrong?
ZeN > plusnet > entanet > <aaisp.net> > Sky LLU > WightWireless > Plusnet FTTC 73/17
Edited by mikehiow (Tue 27-Jan-15 10:31:28)
|
|
|
Need a cabinet number and exchange name to be able to say much more that is useful.
EO work usually involves connecting people to a brand new cabinet, but some re-arrangement of lines to existing cabinets is not unheard of.
Some providers operate on copies of the databases, so can be a few days behind in updating which can explain one system saying yes and another saying no.
|
|
The author of the above post is a thinkbroadband staff member. It may not constitute an official statement on behalf of thinkbroadband.
|
|
|
Hi,
Cab 24
Ex LNSTF
As I say, There has been a big OR presence around cab 24 for weeks, with some digging up of the pavement down the road, too.
The FTTC cabinet doesn't look particularly new, either, so I'm not sure that the associated work has been to do with FTTC go live.
ZeN > plusnet > entanet > <aaisp.net> > Sky LLU > WightWireless > Plusnet FTTC 73/17
Edited by mikehiow (Tue 27-Jan-15 11:09:50)
|
|
Register (or login) on our website and you will not see this ad.
|
|
|
Live since early 2013.
If I was a betting man would suggest your postcode is E15 2PG?
This looks to be an old EO postcode, that has been moved to cabinet 24 recently, so pester ISP again with details of what https://www.btwholesale.com/includes/adsl/main.html says for your exact address. If you get nowhere then email me with full address details to [email protected] and will verify with Openreach that the checkers are correct.
|
|
The author of the above post is a thinkbroadband staff member. It may not constitute an official statement on behalf of thinkbroadband.
|
|
|
Close, but I believe they would be subject to the same treatment as mine - several blocks in a development, each having it's own postcode.
So it's as I suspected then. I've already suggested the same to the ISP, so hopefully they listen.
ZeN > plusnet > entanet > <aaisp.net> > Sky LLU > WightWireless > Plusnet FTTC 73/17
|
|
|
To follow on from this, Plusnet have given up.
They attempted to place an order on a new line, which failed and then told me there is no escalation process to pursue the matter any further.
How do I progress with this? Is there someone/A department at BTOR that I can speak to, to clarify the situation?
Presumably, someone knows something about the work, and something must have happened to have the DSL checker go from saying no cabinet, to having a cabinet.
ZeN > plusnet > entanet > <aaisp.net> > Sky LLU > WightWireless > Plusnet FTTC 73/17
|
|
|
as Andrew said above
"If you get nowhere then email me with full address details to [email protected] and will verify with Openreach that the checkers are correct."
This iis the best route as Andrew has contacts within OR
|
|
|
That process is underway, and yes 50+ flats are on a PCP, number 24. Some further checking underway on the specific address in case something odd gone on.
My money is on this being a retail level issue, where the number of changes taking place are catching out mirrored or out of date databases.
|
|
The author of the above post is a thinkbroadband staff member. It may not constitute an official statement on behalf of thinkbroadband.
|
|
|
Thanks Andrew, I really appreciate your help.
ZeN > plusnet > entanet > <aaisp.net> > Sky LLU > WightWireless > Plusnet FTTC 73/17
|
|
|
Another thing I have noticed is a significant reduction in my ADSL speed.
I've no idea if it's related, but I've dropped from 11-12mbps sync to just 8.5mbps sync.
Not conclusion proof, I know, but perhaps an indication.
Hopefully Andrew comes up with something - this connection is killing me 
ZeN > plusnet > entanet > <aaisp.net> > Sky LLU > WightWireless > Plusnet FTTC 73/17
|
|
|
Have you had any luck with this?
Feel free to tell me to go away and be patient. 
ZeN > plusnet > entanet > <aaisp.net> > Sky LLU > WightWireless > Plusnet FTTC 73/17
|
|
|
Pester next Monday and I'll pass the pester on
|
|
The author of the above post is a thinkbroadband staff member. It may not constitute an official statement on behalf of thinkbroadband.
|
|
|
So, regarding this, I decided to spam a few BTOR email addresses to see if I could find anything out.
Today, I had a call from the Head of Sales at BTOR saying that he'd investigated it and my line is indeed an EO line.
He says there was some confusion when some shops at the bottom of the flats that are currently being fitted were connected to cabinet 24 rather than the existing EO cable.
ZeN > plusnet > entanet > <aaisp.net> > Sky LLU > WightWireless > Plusnet FTTC 73/17
|
|
|
|
I'm confused about the confusion...
Is it the case that you should have been moved to cab 24 but weren't? Or you should stay EO now, and have the database reverted?
|
|
|
I reckon they are either E15 2PP or E15 2PS going by their speed that they mentioned.
Did some checks...
Exchange Name: Stratford
Exchange Code: LNSTF
Cabinet: 24
Fibre Phase: Phase 05a 2011
Fibre Information: FTTC Available from 26th March 2013
Result Count (ADSL:P24): 6
Result Count (ADSL:EO): 211
Result Count (FTTC:P24): 656
Result Count (Total): 873 Seems there are still loads of EO lines that share the same postcodes as cabinet 24, so maybe those may be moved over later or are in the middle of being moved over, hence them seeing BTOR Vans.
There is still 6 addresses on cabinet 24 that are unable to get FTTC (according the BT DSL Checker).
Paul
|
|
|
I'm confused about the confusion...
Is it the case that you should have been moved to cab 24 but weren't? Or you should stay EO now, and have the database reverted?
I still don't know. BTOR's stance was that the retail units at the bottom of the building were recently connected to cabinet 24, and they think that perhaps the database was wrongly updated on the back of that.
The database has now been "corrected" and states that I cannot receive FTTC.
I don't quite understand why they would run a cable from Cabinet 24 to connect the new units when there are apparently 80+ spare pairs at the other DP for the building unless they were considering FTTC availability.
If they were considering FTTC availability, why not run a bigger cable and do it properly - moving the whole existing DP to cab 24, or is it a case of capacity at Cab 24?
ZeN > plusnet > entanet > <aaisp.net> > Sky LLU > WightWireless > Plusnet FTTC 73/17
|
Pages in this thread: 
Print Thread
mikehiow
