Interleaving Request
I like the analysis there x47c 
but that does about sum it up even if it was 12½days uptime. I'm reckoning that there's been one or more significant bursts of noise/interference. Usual questions - had any thunderstorm at the time in question? Can you hear/have you heard any crackling or other noises on the line when using the phone? Have you had any problems with incoming or outgoing calls? OR been messing in your Cabinet? Any power dips etc?
but that does about sum it up even if it was 12½days uptime. I'm reckoning that there's been one or more significant bursts of noise/interference. Usual questions - had any thunderstorm at the time in question? Can you hear/have you heard any crackling or other noises on the line when using the phone? Have you had any problems with incoming or outgoing calls? OR been messing in your Cabinet? Any power dips etc?
I thought I'd have a look at the stats before bed and my BT profile is up at 14.2Mbs 
Not surprised considering the SNRM.....attached.
My PN profile is way behind now at 12Mbs.
Not surprised considering the SNRM.....attached.
My PN profile is way behind now at 12Mbs.
PN profile has kicked up to 14.2Mbs...that was quick.
Speed prior to all this.....
Current speed...
Crazy stuff
Speed prior to all this.....
Current speed...
Crazy stuff
Obviously your Delta report got through last night and one of Plusnet's script runs last night upped your Current Line speed
I am going to refer to what ever caused the drop in sync and the application of Interleaving as "the Event". There is no doubt whatsoever, that something has made conditions on the line worse compared to the previous Fast Path stats back in January (note - the change in product will have no bearing on this).
First just a quick comment on the Upstream - the Errors are very low, certainly not worse, in fact strangely seem better, although there have been more Bit-swaps.
Now the Downstream -
Immediately prior to/at the point of the Event there was a significant increase in errors (rather obviously or DLM wouldn't have acted) but the very large number of SES errors suggest either a prolonged burst of noise/interference or multiple shorter bursts. This resulted in at least an order of magnitude increase in CRC errors and possibly slightly less of an increase in HEC & ES errors. However there seemed to be a decrease in the number of bit swaps which could possibly be interpreted as meaning that the noise was fairly broad spectrum affecting many tones and hence less possibility of swaps. Note that back in January there were only 8 SES errors in just over 19 days!
DLM applied Interleaving at depth 64, not exactly the lowest - not surprisingly CRC, HEC & ES errors were at a lower rate than on Fastpath however initially (over that 2 days of stats) the RS corrected errors were 0.5% of the total RS.
DLM was obviously unhappy about what seems to have been an increasing error rate and has now applied Interleaving at depth 128 & in these later stats over a 7 hour period the RS corrected errors have increased 10 fold and the RS uncorrected errors have increase by just over 15%.
DLM also seems to have lowered the Target SNRM
The CRC & HEC errors have increased and the ES errors are an order of magnitude bigger despite the increase in Interleaving depth. There is also significant SES errors compared to the initial Interleaved period when there were none.
Whether the latest stats will show a continuing deterioration or improvement remains to be seen. It seems rather co-incidental that works have been going on to install new street lighting. One has to question whether the trench digging etc has resulted in possible damage to a cable, maybe a power cable, not necessarily phone. Do you know where they were digging the day/time of the Event when you lost sync and Interleaving got applied Strat?
The other possibility I suppose is the proximity of a new electric cable close to a phone cable, but that is hypothesis as the phone cables could be overhead.
Check of course whether you end up with any crackling or other noises on the line when using the phone or any problems with incoming or outgoing calls which would indicate a phone line fault.
This also seems to be one of those rarer cases where DLM is not adjusting the line in the most sensible way, especially if ping time is more important than speed.
First just a quick comment on the Upstream - the Errors are very low, certainly not worse, in fact strangely seem better, although there have been more Bit-swaps.
Now the Downstream -
Immediately prior to/at the point of the Event there was a significant increase in errors (rather obviously or DLM wouldn't have acted) but the very large number of SES errors suggest either a prolonged burst of noise/interference or multiple shorter bursts. This resulted in at least an order of magnitude increase in CRC errors and possibly slightly less of an increase in HEC & ES errors. However there seemed to be a decrease in the number of bit swaps which could possibly be interpreted as meaning that the noise was fairly broad spectrum affecting many tones and hence less possibility of swaps. Note that back in January there were only 8 SES errors in just over 19 days!
DLM applied Interleaving at depth 64, not exactly the lowest - not surprisingly CRC, HEC & ES errors were at a lower rate than on Fastpath however initially (over that 2 days of stats) the RS corrected errors were 0.5% of the total RS.
DLM was obviously unhappy about what seems to have been an increasing error rate and has now applied Interleaving at depth 128 & in these later stats over a 7 hour period the RS corrected errors have increased 10 fold and the RS uncorrected errors have increase by just over 15%.
DLM also seems to have lowered the Target SNRM
The CRC & HEC errors have increased and the ES errors are an order of magnitude bigger despite the increase in Interleaving depth. There is also significant SES errors compared to the initial Interleaved period when there were none.
Whether the latest stats will show a continuing deterioration or improvement remains to be seen. It seems rather co-incidental that works have been going on to install new street lighting. One has to question whether the trench digging etc has resulted in possible damage to a cable, maybe a power cable, not necessarily phone. Do you know where they were digging the day/time of the Event when you lost sync and Interleaving got applied Strat?
The other possibility I suppose is the proximity of a new electric cable close to a phone cable, but that is hypothesis as the phone cables could be overhead.
Check of course whether you end up with any crackling or other noises on the line when using the phone or any problems with incoming or outgoing calls which would indicate a phone line fault.
This also seems to be one of those rarer cases where DLM is not adjusting the line in the most sensible way, especially if ping time is more important than speed.
I believe you are correct about the CRC error counts.
I haven't done any gaming in the last 36 hours as my daughter presented me with a crashed Micro SD card with 1,200 irreplaceable photos to recover
Edit: I've just done a bit of gaming and it was well down to my usual standard, the connection is fine.
I haven't done any gaming in the last 36 hours as my daughter presented me with a crashed Micro SD card with 1,200 irreplaceable photos to recover
Edit: I've just done a bit of gaming and it was well down to my usual standard, the connection is fine.
