How often is codelook updated

What looks like an all in one cabinet has just been put in our village. This is to cope with long lines not an EO cabinet. There is no reference in Codelook to a cabinet at the postcode so does anyone know how long it is likely to be until Codelook picks this up?

When you start codelook you will see the dates of the various BT datasets and lists used in constructing the database. The current database was created on 24 March and used the BT broadband datasets dated 17 March. Codelook is updated quite frequently however the BT broadband datasets used tend to be updated less frequently ranging from two weekly to monthly.

Thanks for that.

So at the worse case it should not be more 5 or 6 weeks out of date so before the end of April we should see the cabinet being identified by postcode and shown as being built .

The postcodes given by codelook as the location of a cab are often seriously in error, or at least that is the case in central London where the area covered by each postcode is quite small. Is the new cab in use yet, or as in our case, a new all in one to serve a cluster of 75+ longish EO lines, is it listed but with a projected live date? For ours, WRVAUX54, it states "FTTC being Connected, live due by May 2016" Codelook also still lists the exchange bundle, Exchange 71, through which our lines are currently connected. How long it will be until we go live is anyone's guess as Lambeth are preventing BT from carrying out the last piece of required work.

Does the BR Wholesale Broadband Availability Checker still list the old cab as being the one through which your phone is connected? Use your phone number not your post code when checking or if the number isn't recognised, use your full address. You want to see this change to the new cab before you will be able to order an FTTC based connection - assuming you cannot on the old cab.

The cabinet we are connected to at the moment is shown to be in the middle of nowhere, about a mile and a half further away than it actually is.

The availability checker gives the same cabinet number as codelook.

The availability checker seems for no apparent reason to have doubled the already optimistic speed estimate that it used to show and is now more than 3 times the actual 2.2Mpbs line speed, and infinitely more times the speed any other line in the post code can get, as no one else has managed to get a working FTTC service.

Out of curiosity does Mouselike give a truer location for your current cab or does it give the same location as Codelook?

Mouselike is exactly right

Edited by deleted (Thu 24-Mar-16 23:13:06)

Thanks.. I wondered if it might be as I've found it to be pretty good other than in the case of the cab serving a friend's property in south London where it suggests the cab is located in Manchester. In some cases, rather than "guessing" it says it doesn't know or something to that effect.

Codelook recently seems to be very conservative where new cabinets are being added for EO lines. The cab gets a name to match the EO bundle, but don't get any postcodes, so it is hard to figure coverage in advance ... questions spring to mind about how the cab will be ultimately numbered, and whether EO bundles will share one cab.

The old behaviour, during the build, was that postcodes would appear to be covered by both an EO bundle as well as a new cabinet.

Figuring long-line upgrades, like an AIO, in advance seems similar, or maybe harder if you can't remember the highest cab number a few weeks ago. Some things can be seen, (iirc your exchange name, it looks like a lot can be seen) as far as cab names are concerned, but with missing postcodes, nothing looks certain.

In reply to a post by MCM:

Out of curiosity does Mouselike give a truer location for your current cab or does it give the same location as Codelook?

Mouselike is only good for postcodes that are only used by a single cabinet, for post codes that are covered by more than one cabinet will only return a single result, like our postcode is covered by 2 cabinets and that site only shows the result for the other cabinet and not ours.

I sent them an email stating this and as I had expected, there was no change and no reply either.

But I can say that the location for the other cabinet was correct though. so I cannot fault that

Paul