No

Will be asking officially during the week

It is a bit pestilential, because of the LLU line problem on the normal dsl checker.

We all know the postcode one isn't to be trusted. If they wanted to axe one, it should have been that.

I think it's because too many people have been putting mass automated requests into it. First BTW recently removed the direct access to it and made us have to go through the "home" phone number page to getto it. Now I've seen two or three people on here defeat that and get back to going straight to it - so their mass enquiry works.

BT Wholesale have removed address option because of system abused by peoples like change my page etc as bt doubt don't like this abused

Ok have asked, and am told it should be back in a couple of days.

I did not ask which planet these days are on though.

Andrew

Thanks for finding that out, as it is an important facility for advising many people. I wonder if when it returns it will be with the multi-address function removed ....

If it was me coding it, then would be adding captcha and other tweaks to break the automation, but then its not my code

+1

The DSL Checker data is supplied by Openreach to Wholesale (who provide the web checker - original link https://www.btwholesale.com/includes/adsl/adsl.htm). Both Openreach and Wholesale sell this data in bulk form to ISPs, this is where you go to an ISP page and it tells you what you can order.

I know for a fact some people were creating scripts to essentially pull data from this and it wouldn't surprise me if people were either profiting from it or using it rather than paying for the bulk data.

Edited by deleted (Mon 17-Oct-16 17:52:27)

It may have been changed because of the rise of infill cabinets. The one in our village is now taking orders if you do not have an existing fttc service but for lines on the same postcode (indeed the same premises) with an fttc service the telephone checker says you cannot get fibre.

Database seems to happily cope with infill cabinets in some areas, just some seem to hit issues, suggesting those are a data input or integrity issue rather than a data presentation issue when retrieving data on the public site.