Rate cap?

Hi,

I've been switched over to AA, as of about 4am this morning and it was way more seamless and prompt than the last ISP change, so a good start. However, the line won't sync at more than about 46Mb/s when the attainable is 55Mb/s on the downstream. Could this be due to a rate cap on the line? It would set at 55Mb/s consistently with the previous ISP.

I hadn't appreciated that G.INP would not be enabled on the new line, so I expect latency to reduce, back to the levels I'm used to when it does kick in.

Paul

Latency and sync speed are not related in any significant way.

The most probable explanation is that you have upgraded from a 55/10 Openreach product to the 80/20 one. This resets DLM, but with interleaving and no G.INP.

That would sort itself out within 2-3 days as long as you haven't done a large number of re-syncs to try to improve things. Just leave it connected.

The 46 actual v 55 attainable does suggest interleaving.

There are no speed caps on AAISP at all. There isn't even a product option below the Openreach 80/20 product.

Did you take your landline to them as well, and which initial allowance did you choose?

Your sig and profile are now out of date .

Edited by RobertoS (Fri 28-Sep-18 23:46:29)

New line activations start with interleaving and INP=3 (low interleaving).
The max attainable is exaggerated with interleaving.

Interleaving also takes roughly 10% of the sync speed so you will probably sync about 51-52Mb when G.INP activates.
If DLM chooses to lower the target SNRM to 3dB you could get nearer 60Mb.

How much extra you get from the change to 3dB target SNRM varies for every line. Lines that make use of the D3 band benefit the most in my experience.

Stability is the key for the first 2 weeks of you want the target SNRM lowered so try not to resync or change modems a lot.

Agree with the above replies, just don't expect interleaving to be replaced with G.INP quickly, it can take weeks, in some cases.

In reply to a post by WilliamGrimsley:

Agree with the above replies, just don't expect interleaving to be replaced with G.INP quickly, it can take weeks, in some cases.

Out of interest, any idea why it takes so long? I ask because I have been with AAISP for about 6 weeks and my max attainable is falling as more adjacent plots are connected to FTTC.

I've no idea. The time it takes to activate is random, as in there's no set time. I think some of it is down to how noisy the line is (amount of FECs (as G.INP activates only when INP+FEC is on)).

Edited by deleted (Sat 29-Sep-18 18:15:26)

99% of lines on Huawei cabinets have G.INP activated within 2-3 days.
The majority also try a lower target SNRM within the first week.

It is the odd exception that can take considerably longer. My own line took around 11 weeks to apply G.INP.

Back near the start of the G.INP rollout there was an average of 3-4 week wait for G.INP on new lines but that isn't the case now.

Thanks for the responses.

I was indeed interleaved, which I should have mentioned and what I should have also asked, was whether the service was banded, not capped. I blame the sleep deprevation from having a 9 week old!

The line had G.INP enabled the following day and after 1 or 2 resyncs (Lost Carrier), has been climbing back up to nigh on the max I've seen on the line, sync wise. The upstream sync is also the highest it's been since the line initially settled down after being fibre enabled.
Latency has increased from around 11ms to 16ms to www.bbc.co.uk, my usual benchmark. So I'd like to understand why that's happened.

I'm monitoring it for a separate gateway related issue but it seens to be more resiliant than before, despite some choppiness on the SNRM. Maybe that's because i'm now going via TTB backhaul and not BTW?!

Thus far I'm very impressed with AA. Bearing in mind when I migrated, I chose the 2TB package and as of today, I have 2.98TB of capacity, which just adds the icing on the cake.

The control panel is excellent too, meaning I no longer feel the need for the TB BQM. And the listed view of occurences on the service and account. Now I just need them to sort out the log running line issue!

Paul

Edited by deleted (Mon 01-Oct-18 13:06:57)

In reply to a post by youngsyp:

Thanks for the responses.

No worries!

In reply to a post by youngsyp:

Latency has increased from around 11ms to 16ms to www.bbc.co.uk, my usual benchmark. So I'd like to understand why that's happened.

It could potentially be because the route in which your connection takes between the CPE (router/modem combo) and the ISP has become "longer", as in there are more hops (IP addresses of different routers through the network), or because the distance those hops are from you, have increased. You can prove this by pasting a tracert to bbc.co.uk.

Edited by deleted (Mon 01-Oct-18 16:56:17)

The base latency on AA, and every ISP I've been with, can vary depending on which route your connection is taking from the exchange to the ISP's gateways. This route is established when the PPP session is initiated. Sometimes from where I am they seem to route via Edinburgh or somewhere like that, other times to head directly south from Manchester.

My best with AA has been 11-12ms and that is my most common. Occasionally I get a higher one of 16-20ms, as at the moment. (Live BQMs in my sig).

It doesn't really affect me much, though complex pages load a bit slower. I don't game, where it could be important.

With some routers and modem/routers you can drop the PPP session and start another. Best left for a while before restarting. Some other routers you may need to reboot or even power off for several minutes to clear the session. With modem/routers where you can't drop the PPP session you have to be wary of upsetting DLM by re-sync'ing too much.