I told you. The IP Profile is screwed when the line is banded.

There is nothing wrong with the IP Profile when the line is not banded. Which is the vast majority of lines.

You haven't read my post correctly. Mine is still wrong, so something isn't right somewhere! It may not be wrong for your line, but it is for others including mine!

Edited by deleted (Sun 26-Mar-17 11:29:15)

Doesn't look like my line has been banded. The sync rate fluctuates between 71.9 and 73. Yet the BT op profile stays stuck on 66mbps. Furthemore the plusnet GEA test reveals no banding either on DS or US.

Plusnet forum members have posted that recently people on G.INP have fudged BT ip profiles around 91% instead of the usual 96.9%.

Exactly the same issue I'm facing and I'm on BT!

Huawei or ECI cabinets, or both?

Huawei here. I did turn off G.INP and when the line resynced the IP profile was correct, back on and incorrect.

Edited by deleted (Sun 26-Mar-17 18:44:56)

I'm on Huawei cab and experiencing it too.

Excerpt from GEA test plusnet carried out for me:

0.128M-80M Downstream, Error Protection Off - 0.128M-20M Upstream, Error Protection Off

Strange as it doesn't report any G.INP as being on (should say retransmission low).
Also confirms no banding as my actual sync rate does fluctuate from 70-73mbps.

Edited by fishpan (Sun 26-Mar-17 19:08:22)

I do find that GEA tests are often wrong and somewhat lacking in detail. I would always go with what the router reports. I really hope this gets sorted soon, because some EU's including both of us aren't getting the correct download speed!

Edited by deleted (Sun 26-Mar-17 19:37:48)

In reply to a post by fishpan:

Plusnet forum members have posted that recently people on G.INP have fudged BT ip profiles around 91% instead of the usual 96.9%.

Whatever the issue is, it isn't consistent.

We have Plusnet, 80/20 FTTC, with G.INP on a Huawei 288.

Sync is 79,999 / 19,999

IP Profile is 77.35Mbps, or 96.69%.

Interestingly, since the DLM reset and G.INP reactivation, the IP profile is now correct on my line. I wonder if this problem only occurs when the downstream SNR margin is set to 3, 4 or 5 dB.

Edited by deleted (Thu 06-Apr-17 16:48:15)