Any help with this? I'd really rather not play call centre roulette and simply deal directly with a mod if at all possible.
Hi @DanMax89,
To give us an idea of how your connection is performing, please can you post your router stats as shown - Top Tips to get help on the forum
Thanks
PaddyB
Hi Paddy,
Thanks for the response. Connection speeds are fine (currently syncing around 71/20), the issue is with interleaving being enabled on the line by DLM increasing latency which will not show in the HH5 stats.
Can we please take same steps that were taken in the post linked in my original post please to check which NGA profile is active and if necessary change it to standard.
OK so thinking there may be an issue with the line now. As can be seen below the noise margin is extremely low at 0.8 despite being at 5.8 this morning and the max rate has dropped well below the current sync rate. The last resync 8 days ago synced very slightly higher than it was previously, so could this be indicative of the line struggling at the new rate? This is extremely frustrating as I was syncing at near max infinity 2 speeds until around 4 months ago despite never getting rid of interleaving.
I have performed quiet line test and cannot hear any noise on the line.
1. Product Name: HomeHub5
2. Serial number: +076286+1549002260
3. Firmware version: v0.07.05.0A13-BT (Type B) Last updated 10/3/2016
4. Board version: 01
5. VDSL uptime: 7 days, 21:52:50
6. Data Rate: 20000 / 71585
7. Maximum Data Rate: 21752 / 66499
8. Noise Margin: 6.0 / 0.8
9. Line Attenuation: 14.4 / 15.6
10. Signal Attenuation: 0.0 / 0.0
Either way I would still like to get the NGA profile looked at as previously mentioned. Thanks in advance.
wow that is an extremely low down noise margin and am really surprised that you have managed 7 days connection time without router dropping conenction
Never seen one as low as that.
if you have already had a DLM reset which would start with latency at Fast and from what you say in a day or so the DLM had moved your latency to interleaved would suggest there are line errors. Not enough to cause a disconenction but enough for DLM to move latency to interleaved