Peak time speed problem - purleigh
While that might be a perfectly good explanation for what's happening tonight, I've been having this exact same problem for FOUR MONTHS.
The trouble is that there is ALWAYS yet another excuse for almost every week that goes by, and when there isn't I'm told it must be my line - for which I've yet to see any evidence.
Plusnet clearly don't have sufficient network resilience with enough network paths to prevent these problems happening on a near daily basis.
They might have enough theoretical trunk capacity for their current network loading projections, but why are these gateways running constantly at near full capacity when any competent network designer would aim for 50% equipment utilization under maximum user traffic throughput.
I still have had no explanation why my line latency two months ago was 17 to 19ms, but suddenly it went to 31 to 34ms. Do they not know ?
In fact, come to think about it, they have never had any idea what my line is doing, or how my exchange is really performing, when shouted at they have to manually look to be able to tell when points on the network are overloading and then manually make adjustment. Why the hell aren't there alarms going off every time each piece of networking kit exceeds say 80% saturation, so more resources can be bought online to cope.
It seems ludicrous that some people on this forum complain of a peak time slowdown from 77Mbps to 65Mbps, when tonight I've seen less than 1Mbps for long periods of time which will then go back to normal (7.15Mbps) at midnight. If the system out of balance, why are the biggest percentages of speed loss affecting the slowest connections most, rather than bringing the speed ceiling down for all users ? i.e. how can the network still be feeding ADSL2 and FTTC connections with much more data than 8Mbps but at the same time my "up to" 8Mbps line is utterly strangled to the point of being unusable ?
It is infuriating that for the past four months when these issues have been going on, that Plusnet don't have their best engineers working weekends and evenings to bloody well sort it out. Working super long hours to sort out the consequences of your own designs shortcomings certainly focuses the mind on getting it right, it was always a requirement for engineering staff in all the telecoms companies I've work for in the past !
The trouble is that there is ALWAYS yet another excuse for almost every week that goes by, and when there isn't I'm told it must be my line - for which I've yet to see any evidence.
Plusnet clearly don't have sufficient network resilience with enough network paths to prevent these problems happening on a near daily basis.
They might have enough theoretical trunk capacity for their current network loading projections, but why are these gateways running constantly at near full capacity when any competent network designer would aim for 50% equipment utilization under maximum user traffic throughput.
I still have had no explanation why my line latency two months ago was 17 to 19ms, but suddenly it went to 31 to 34ms. Do they not know ?
In fact, come to think about it, they have never had any idea what my line is doing, or how my exchange is really performing, when shouted at they have to manually look to be able to tell when points on the network are overloading and then manually make adjustment. Why the hell aren't there alarms going off every time each piece of networking kit exceeds say 80% saturation, so more resources can be bought online to cope.
It seems ludicrous that some people on this forum complain of a peak time slowdown from 77Mbps to 65Mbps, when tonight I've seen less than 1Mbps for long periods of time which will then go back to normal (7.15Mbps) at midnight. If the system out of balance, why are the biggest percentages of speed loss affecting the slowest connections most, rather than bringing the speed ceiling down for all users ? i.e. how can the network still be feeding ADSL2 and FTTC connections with much more data than 8Mbps but at the same time my "up to" 8Mbps line is utterly strangled to the point of being unusable ?
It is infuriating that for the past four months when these issues have been going on, that Plusnet don't have their best engineers working weekends and evenings to bloody well sort it out. Working super long hours to sort out the consequences of your own designs shortcomings certainly focuses the mind on getting it right, it was always a requirement for engineering staff in all the telecoms companies I've work for in the past !
I nearly forgot, It's after midnight and everything is wonderful again ! 
[quote=spraxyt]are you aware whether or not Trellis was On (see <<<<< mark-up) when you previously had the lower values?
Unfortunately, the step change in latency occurred while my Draytek Vigor 2710 gateway had been in continuous use for about eight or nine months, and the ADSL stats for that don't show the detail of whether trellis was active or not.
The trellis status you have highlighted is from my currently connected Netgear DG834GT gateway with DGTeam firmware.
When my 10 day line retraining period has completed (should have been three hours ago ?), then I could experiment with using the router firmware to override the trellis setting to see whether that has any affect on latency. I have my doubts whether it will make any difference, as all the other stats are as near perfect as could possibly be expected, but it will be interesting to find out ! - although my eventual aim is to move back to the Draytek gateway for ongoing use after the peak time problem has been resolved, and that doesn't have a trellis override option, so the experiment will be of limited practical use.
[Edit :] I have since found the following information regarding trellis coding -
Digital Subscriber Line (DSL) Transmission Methods
and
Unfortunately, the step change in latency occurred while my Draytek Vigor 2710 gateway had been in continuous use for about eight or nine months, and the ADSL stats for that don't show the detail of whether trellis was active or not.
The trellis status you have highlighted is from my currently connected Netgear DG834GT gateway with DGTeam firmware.
When my 10 day line retraining period has completed (should have been three hours ago ?), then I could experiment with using the router firmware to override the trellis setting to see whether that has any affect on latency. I have my doubts whether it will make any difference, as all the other stats are as near perfect as could possibly be expected, but it will be interesting to find out ! - although my eventual aim is to move back to the Draytek gateway for ongoing use after the peak time problem has been resolved, and that doesn't have a trellis override option, so the experiment will be of limited practical use.
[Edit :] I have since found the following information regarding trellis coding -
Digital Subscriber Line (DSL) Transmission Methods
Quote The trellis code, specified in the ANSI DS1.413-1995 standard, is used as the inner code in the concatenated coding scheme of ADSL systems, with the Reed-Solomon code serving as the outer code. The trellis code operates on the data spread on the various subcarriers, and thus does not add extra latency. The trellis code improves the noise margin measured for stationary added noise (such as white noise and typical NEXT and FEXT noise) without requiring additional bandwidth.
and
When you re-read that entire thread, there are a noticeably high incidence of tactical answer avoidance by staff !
As last Saturday - no peak time speed drop tonight, very consistent speeds all evening, even if very slightly slower than normal.
Quote You are currently connected to gateway pcl-ag08
Tonight's final test, as usual just around midnight, speed is nearly at full line profile.
