Well, after a few days of fun and games (largely, it has to be said, for Shaun not me) I finally got migrated this morning. So thanks to Shaun and co for getting it sorted

Was there a good reason for the delay ?
i.e. .Why didn't BT turn up..

Can I ask which area your in ?

Sooooo what speed you on up and down we might as well all be jealous....

Not really a good reason, no. Apparently the BT ordering system cancelled the original order because it deemed it "incomplete". It was a manual order, so I guess there shouldn't really have been a way for it to be incomplete at the point it was submitted, hence BTs ordering process mangled it at some point.

Exchange code = EACHE

Currently synced at 39712K Can't get the upstream as A&A's stats don't show it directly but it should be 10M and my BRAS is 35M/9999K. Speed tests are a bit variable on the downstream but I'm getting a pretty reliable 8M+ on the upstream tests. Haven't been at home much the last couple of days so haven't really had a chance to test it properly ie. real downloads & uploads with a known server.
I'm still dabbling with trying to get some stats directly from the BT-supplied modem, so no idea of the attenuation figures etc.

Just out of interest, the test that the engineer ran during installation showed my line as being capable of 47M/15M - his tester synced at 40M/10M @ 9dB. I'm about 60 metres from the PCP and I have the benefit of having been here on the day that BT pulled the cables to the property some 12 years ago so I know the cable run is just about 90 metres.

I suspect the BT Modem is a dead end as far as stats go.. it seems to be a dumb bridge with no smarts at all.

47M at 60 metres would be pretty poor for VDSL2, but the way they've got it configured it wouldn't surprise me.

Figured that might be the case, oh well. I only got a quick glance at the stats and sadly the budget doesn't run to a JDSU tester.