In reply to a post by Icaras:

Which cabs still need enabling?

Cabinet 8 is still waiting but I think I saw a date of between March and Oct 17 for the work to be carried out. No idea why the delay, the new cabinet is in situ waiting for the hook up but no signs or information from Openreach what the delays are due to.

Got an email from OpenReach today, they're still saying "by January at the latest" for cabinet 3. I politely pointed out that I've been given many many "by the latest" assurances before, but this time they seem quietly confident.

We will see!

In reply to a post by Irby:

Got an email from OpenReach today, they're still saying "by January at the latest" for cabinet 3. I politely pointed out that I've been given many many "by the latest" assurances before, but this time they seem quietly confident.

We will see!

According to Openreach Cabinet 2 and 3 are still down as being connected up and has a place holder date of 4 Months and are at stage 6 of 8 of the upgrade so not long to go maybe.

Cabinet 8 is still down as being reviewed.

Now whether this date is correct or just a default generic date length (aimed around a perfect upgrade where nothing goes wrong) is another thing.

Paul

Where did you see the 'stage 6 of 8' info?

In reply to a post by Irby:

Where did you see the 'stage 6 of 8' info?

Ahhh, on their where and when page, I won't say how to get or see the info, only that its there but just not displayed, basically I think its there for their external desktop apps to do the lookup.

Basically my desktop app that took 20 mins to write, sees all information (that they send to the browser, no personal information is there, mostly status info), I started seeing the new information a few days ago when my app broke and I had to figure our why and fix it.

Basically I can see information like (I have restructured some info for ease of reading):
[Exchange]
Name: Liverpool Irby
Status: Accepting Orders
Location: 53.3531494, -3.0981791

[Cabinet]
Number: 3
Status: Enabled Area
Due by: 4 Months
Stage: Connect (3) <-- This value goes down to 1 I think, when its ready.

RolloutStage: 6 (goes up-to 8 which means ready)

Basically my app just acts an a browser, but only does the request part and ignores any images or stylesheet files etc, so its faster than my browser.
I originally wrote this app due to Edge, and IE kept having issues and crashing and I basically wanted to check my own line for fibre availability, but I check others now and then.

That's all I am saying, every time I say how I am reading it, they break my app LOL.
And the last change they did broke the cookie side on Edge browser where it just spins the cogs the first time on the page when searching.

Paul

Amazing news, fingers crossed it does happen in january! will be a late christmas present if all works out.

Cheers paul for the info much appreciated, thats all openreach need to do give the customers a time frame.

In reply to a post by Sqwirral:

Amazing news, fingers crossed it does happen in january! will be a late christmas present if all works out.

Cheers paul for the info much appreciated, thats all openreach need to do give the customers a time frame.

Well they can't due to issues happen causing the date to get pushed back, that's why I said these was default place holder dates.

What has started getting me interested in this now is that Openreach has not removed the dueby date from its info, so now I will have no information on the dates.

See this is why I wished I kept quiet now

Paul

I wouldn't get too excited just yet. I keep a log, and the date for Irby as a whole, (including cabinet 3) has shifted twenty three times (23) since 2011

Oops spelling mistake, it should read:

Openreach has now removed the dueby date from its info

My bad

Paul

I don't suppose anyone has any news on the cabinets still waiting to be upgraded do they, there doesn't seem to be anyway to get info on why there is such a delay or when they are likely to be sorted.