As far as I can see, my exchange (Suckley - WMSUC) has ADSL Max but not 21CN.
Yes - that is indeed the case.
What I don't understand is why the BT wholesale speed test is so variable and often so far from reality.
I have to admit, I don't find it very trustworthy for giving me an idea of real throughput speeds. I find speedtest.net to be more reliable for me, especially when I ask it to use a London server or the Vodafone one in Newbury.
The BTW tester tends to be left for two purposes
- To see what IP profile is being reported by BT (for which you needto see the "extra diagnostics" at the end
- To run tests that the ISP can see
If I look at the BT broadband availability screen, I get results that say that "FTTC Range A (Clean)" speeds are from 12.8 to 19.6 Mbps and "Range B (Impacted)" speeds are from 5.3 to 14.4 Mbps.
I am at the bottom end of "Impacted" and the screen explains what it means by "Impacted" but doesn't tell me how I can find out whether my line is in that category or not. Or whether things can be "fixed".
The screen gives you a flavour of what it means, but even BT internal documents aren't tremendously clear as to what the two ranges mean, and when they should be applied.
However, the checker was upgraded to cater for self-install FTTC, a couple of years back, and that upgrade is what introduced two ranges. That's a clue as to why two ranges exist...
The BTW FTTC Handbook advises ISPs that, when offering a speed estimate to end-users, they should use the impacted range for self-install.
However, it doesn't explicitly tell ISPs when to use the clean range - we just have to assume they mean that it applies to engineer installations. The theory being that an engineer's tests will ensure that any wiring issues or copper line conditions are fixed during the installation, whereas they would be left in place in a self-install.
That, at least, gives us an idea of how an ISP should use the ranges when giving you an estimate before installation.
The document also explains the circumstances when Openreach will reject the fault (the 10th percentile I mentioned earlier), but that doesn't mention which range Openreach will choose to use.
The document also doesn't cope with complex issues, such as where you start out with an engineer install, but migrate to an ISP with a self-install. What threshold should the new ISP use? Or the case where a self-install happens, gets poor speeds, and a subsequent engineer visit fixes things. Should this now have a clean threshold?
All in all, it leaves things murky for fault fixing.
The best thing you have to go on is the speed estimate you were given during installation. But even that can be wrong.
As for being in the 0.05% there are times when one would prefer to be among the masses! I think I might have to wait for Fibre To The Pole (which is just across the road from me) - which is what I think G.Fast means.
It is indeed frustrating to fall outside the norm sometimes.
Unfortunately, while G.fast was originally designed to work from the DP on the pole (hence the term FTTdp), it looks like it will work well at much longer distances, so BT are re-evaluating just where in the network they will site the nodes.
It seems likely that the first round of installation (2017-2020) is very much likely to deal with the area immediately surrounding the existing cabinets.
But who knows where the new iteration of on-demand fibre could go over the next few years?
The current position is that my ISP has asked BT to look into it and will absord the charge (I won't post the name before the whole process is finished, I don't think it would be fair to them)
What was your estimated speed when you signed up? And was it a self-install, or engineer-install?