It is the speed test result.

In reply to a post by Fastman2:

suggest don't use the postode checker use the tel number as that will be far more accurate

I didn't the postcode checker, I used the address checker due to I had no phone numbers, granted the check via phone number is more accurate to do with speeds etc, but 9/10 chances address and phone checks will return the types of services.

Paul

In reply to a post by MrSaffron:

Not always the case, I see a good number of phone errors that get pushed through for correction.

The clever bit is gathering all the data and not hearsay to try and figure out if worth putting forward a correction request.

Agreed, I normally try the phone number when checking, but that has often failed in that past so I have had to fall back to the address checker.
Plus a lot of people are not comfortable giving out their phone number to a stranger.

Like my BT phone number for our FTTP which is on FVA fails the checks via phone number and all I get is the following message:

In reference to www.dslchecker.bt.com/adsl/ADSLChecker.telephone:

There is no data available for this number. This could be either because it is not a BT line or it is a new BT number that has just been provided. Most new numbers will appear on the checker 24 hours after BT has installed the line.

And I think its the same for some other phone providers, so in most cases the address checker is more reliable than the phone number.

Paul

Paul

The OR checker will rarely ( never) have date for FVA lines as this is not OR data and the number could be anywhere ( In the world in an extreme case!)

For WLR fixed line numbers ( and in rare cases numbers ported to FVA) they will have the data as it is OR data.

They do not have data for LLU numbers as LLU operators do not tell OR which line each number is physically connected to.

OR can only check by number for their own numbers.

In reply to a post by airebase:

My assumption is that I should be getting about the same as our nearest neighbours, Haws Barn and Haws Farm and much better than Skythorns and Higher Windhill.

You'll be 200m further on that those two, plus the length of your drive. You should expect to be at least a couple of Mbps lower.

In reply to a post by airebase:

Interestingly, whenever BT engineers have called in the past, they have commented that the head office diagrams do not reflect the actual routing of the cables. The last engineer to call, said he would get them changed, but I don't know if this has been done. Could this have a bearing on the matter?

The data held in BT's database that describes the losses between the cabinet and your DP (black joint box at the top of the pole) could be wrong ... and this is one of the primary sources for the estimator when deciding whether to offer the service.

I'd say it has to be worth trying ... anything's better than 0.7Mbps.

If all else fails, I'd be thinking of a wireless point-point link to that neighbour who gets 9Mbps - to the extent of getting a second line put in there!

It may appear to be simplistic; but have you been through the basics of the Quiet Line Test, including your own internal (phone) wiring?

Costs nothing apart from about 5 to 15 minutes of your time.

Thanks for your input. I am only 50 metres further on from Haws Barn and Haws Farm, as the line runs underground from the junction that supplies them, so the loss should be about 1 Mbps.
It looks like the database may be incorrect, but how do I get it checked and changed?
Many thanks,
John.

What formula is the 50metre and 1 Mbps loss based on? VDSL2 due to the higher frequencies does perform differently to ADSL2+

Have seen lines where same distance from DP and same bundle with different performance levels, reason being that somewhere else there are repair joints or other differences in the lines.

Apparently you can use the below form

https://www.formwize.com/run/survey3.cfm?id=7214&embed

Or email the CEO of BT explaining the problem, and laying out your evidence.

In reply to a post by kitcat:

Paul

The OR checker will rarely ( never) have date for FVA lines as this is not OR data and the number could be anywhere ( In the world in an extreme case!)

For WLR fixed line numbers ( and in rare cases numbers ported to FVA) they will have the data as it is OR data.

They do not have data for LLU numbers as LLU operators do not tell OR which line each number is physically connected to.

OR can only check by number for their own numbers.

I agree with most of that, but even the Openreach Where and when checker says there is no data.

Paul