In reply to a post by sobol:

PlusNet high speed broadband shows:
Current line speed:
38.4 Mb

What I refered as BRAS profile(IP profile) And speeds I've got from https://windows.mouselike.org/be/index.asp?DoAction=...

Better to use the BT Wholesale Performance Test, (normally ignoring all the red instructions), then continue to the Further diagnostics at the bottom of the initial results page. That gives two decimal places as well so we can calculate your connection speed farily accurately.

So what you're saying is that even if PlusNet were limiting my speeds the BRAS/IP profile would be showing higher speeds if they were possible?

Yes. Or to be more precise, they would show the actual IP Profile. Divide that by 0.9679 to get the sync within a few kbps.

I've already run the mentioned test and it doesn't show much different speeds.
It's not biggie to have them off by few kbit/s. The issue I'm trying to solve is 39/18 Mbit/s sync. I feel downstream speeds can be much better.

Anything on DLM? Perhaps I should restart the VDSL modem?

PlusNet replied to me again with:

"Firstly the speeds quoted are only the estimated speeds for your line. After running a test on the line, here are the results of the test:

xDSL Status Summary Circuit Sync Status : In Sync Downstream Line Rate : 39.7 Upstream Line Rate : 18.2. This therefore means you are achieving more than the estimated speed. "

Not today.

The Openreach DLM normally leaves things alone on the first day, unless serious issues are encountered, and steps in on (or at the end of) day 2. Which is today.

I doubt if power-cycling the modem once would do any harm however.

As I said, the BT test gives 2 decimal places and if you run wired a useful speed test as well. Far better for diagnostics than that site you gave .

Was it a real BT engineer, or a contractor (Quinn's/Kelly's usually)?

Edited by RobertoS (Thu 28-Aug-14 17:25:13)

I've received this reply from a rep n the Plusnet forums

I'm pretty sure I know what the issue is after reading that thread so I will await the post

It would be an idea to post over there .

An 18.2 upstream could well be right. With a potential 47 down it suggests that over the full spectrum the attenuation and/or noise are such that the upstream is also tailing off from the potential maximum.

As an indicator, I tend to see lines that have a downstream of 55-60 will usually get full 20 up, with the achievable being just slightly over 20 - mainly due to attenuation.

I've run the BT wholesale tests.

Download speedachieved during the test was - 36.91 Mbps
For your connection, the acceptable range of speedsis 26.88 Mbps-38.4 Mbps .
Additional Information:
IP Profile for your line is - 38.4 Mbps

Upload speed achieved during the test was - 12.43Mbps
Additional Information:
Upstream Rate IP profile on your line is - 20 Mbps

As to real transfer values; I easily get 15.2 Mbps upload and 36,86 Mbps download to my RackSpace server, and that is over SCP which has considerable encryption overhead.

Thank you for your help. I will now start topic on PlusNet forum as suggested.

In reply to a post by RobertoS:

Not today.

The Openreach DLM normally leaves things alone on the first day, unless serious issues are encountered, and steps in on (or at the end of) day 2. Which is today.

I doubt if power-cycling the modem once would do any harm however.

As I said, the BT test gives 2 decimal places and if you run wired a useful speed test as well. Far better for diagnostics than that site you gave .

Was it a real BT engineer, or a contractor (Quinn's/Kelly's usually)?

I'll point out that for Downstream, the "IP Profile" value reported by the BT Wholesale test is indeed related to the downstream sync speed - using the factor RobertoS mentioned earlier.

However, the upstream "IP profile" value is always one of 20, 10 or 2 - and only depends on the package configured for your line. It does not depend on the actual upstream sync speed of the line.

Actually getting upload speeds of 15Mbps does indeed suggest that the sync speed is 17+, but isn't absolute proof that you are synced at 20. It probably matches with the value quoted by the PN rep: 18.2Mbps.

I was wondering why BT IP profile value is different to reported by PlusNet, so thanks for explaining that.

Seeing 18.2Mbps upstream sync I'd expect higher syncs on downstream, that's my only grief. I'll see how PlusNet staff deals with this Today and report back.

In reply to a post by WWWombat:

I'll point out that for Downstream, the "IP Profile" value reported by the BT Wholesale test is indeed related to the downstream sync speed - using the factor RobertoS mentioned earlier.

However, the upstream "IP profile" value is always one of 20, 10 or 2 - and only depends on the package configured for your line. It does not depend on the actual upstream sync speed of the line.

Actually getting upload speeds of 15Mbps does indeed suggest that the sync speed is 17+, but isn't absolute proof that you are synced at 20. It probably matches with the value quoted by the PN rep: 18.2Mbps.

Wild shot

The way the down and up sides are capped at the cabinet sync wise does go wrong, usually for upload, i.e. people order 80/20 and get something like 76/9 and then after some pushing it gets fixed.

If they can do the upload wrong, maybe they got the download wrong this time, or it is a sign of a more symmetric 40/20 on its way at the wholesale level.

for Downstream, the "IP Profile" value reported by the BT Wholesale test is indeed related to the downstream sync speed

That is usually the case.

I have found with HG612 and HH3 that sometimes the HG612 resyncs fast enough that the HH3 does not notice the dropped low level connection. Therefore it does not reset the PPPoE connection. It is the PPPoE reset that forces the profile to match (with the factor mentioned) the sync speed.

When connection is lost due to real line problems the downtime was always enough to force the new PPPoE connection.
However, when DLM was gradually allowing faster sync after a problem, the establishment of that faster sync often went unnoticed by HH3 and thus by profile.
Resetting the internet connection on the HH3 always resolved the issue.

I don't know if there are other situations where this can happen; but probably.
I am pretty sure it was MrSaffron who pointed this out to me originally, so he can say if there is any possibility it could apply here.