slower speeds and higher pings "help needed"

[#1]

Mode: ADSL_2plus
Traffic Type: ATM
Status: Up
Link Power State: L0 
 
  Downstream Upstream
Line Coding(Trellis): On On
SNR Margin (0.1 dB): 88 292
Attenuation (0.1 dB): 320 139
Output Power (0.1 dBm): 0 121
Attainable Rate (Kbps): 10244 1124
 
  Path 0  Path 1 
  Downstream Upstream Downstream Upstream
Rate (Kbps): 8679 444 0 0
 
MSGc (# of bytes in overhead channel message): 59 10 0 0
B (# of bytes in Mux Data Frame): 135 63 0 0
M (# of Mux Data Frames in FEC Data Frame): 1 1 0 0
T (Mux Data Frames over sync bytes): 2 1 0 0
R (# of check bytes in FEC Data Frame): 10 0 0 0
S (ratio of FEC over PMD Data Frame length): 0.4995 4.5309 0.0 0.0
L (# of bits in PMD Data Frame): 2338 113 0 0
D (interleaver depth): 64 1 0 0
Delay (msec): 7.99 1.13 0.0 0.0
INP (DMT symbol): 1.9 0.0 0.0 0.0
 
Super Frames: 81605 73036 0 0
Super Frame Errors: 0 0 0 0
RS Words: 10608714 0 0 0
RS Correctable Errors: 227406 0 0 0
RS Uncorrectable Errors: 34 0 0 0
 
HEC Errors: 4294967289 15 0 0
OCD Errors: 0 0 0 0
LCD Errors: 0 0 0 0
Total Cells: 27118102 314545 0 0
Data Cells: 1118433 5902 0 0
Bit Errors: 0 0 0 0
 
Total ES: 19 0
Total SES: 0 0
Total UAS: 32 4294967244
Line Rate - Upstream (Kbps): 444
Line Rate - Downstream (Kbps): 8679
LAN IP Address: 192.168.1.1
Default Gateway: 195.166.128.197(pppoa0)
Primary DNS Server: 212.159.6.10
Secondary DNS Server: 212.159.6.9
System Running time: 0 day(s) 00:24:49
------------------------------------------------------------
( Current line speed: 7.6 Mb )

BT speedtester says...
Download speedachieved during the test was - 6.81 Mbps
For your connection, the acceptable range of speeds is 2 Mbps-7.15 Mbps.
IP Profile for your line is - 7.66 Mbps

Upload speed achieved during the test was - 0.36Mbps
Additional Information:
Upstream Rate IP profile on your line is - 0.45 Mbps
And i ran this

[#2]

ping is all over the place ;(

[#3]

Unfortunately, as I said above, the sync speed has dropped to 8679 and your profile has dropped to match. The download (and upload) speedtest is at least consistent with the profile now. It looks like your Target Noise margin has gone up to 9dB, with the resultant slower speed.
The reason for the increased ping times is that interleaving is on at depth 64 and was previously either off or not to the same depth.
The big question is what has caused this raised SNRM and increased interleaving depth? Causes can be interference/noise or a dropping connection, any of which could be caused by a faulty phone line. Or you may have had some static (lightning) recently if there was a thunderstorm - did you notice if this was the case? The number of errors was quite high on the stats you posted initially.
Can you hear or recently heard any crackling or other noises on your line when using the phone, or had any problems with incoming or outgoing calls? Have you changed anything in your setup, bought any new electrical or electronic equipment or household appliances or had any go faulty?
If you could post your stats again tomorrow taken in daylight hours (at least an hour after sunrise and an hour before sunset) and If your connection is stable, and the sync speed remains at 8679 in the morning,  the try a resync, ideally around mid-day and then post another set of stats taken as soon as possible after the resync.
Edit: ping times (and speedtests) can vary significantly at peak times. They should be more steady and consistent outside peak hours.

[#4]

It looks like Plusnet have a problem:-

Quote

jeremy@HECTOR:~$ traceroute 195.166.128.195 traceroute to 195.166.128.195 (195.166.128.195), 30 hops max, 60 byte packets 1  ROUTER (192.168.1.1)  1.865 ms  1.848 ms  1.837 ms 2  lo0-central10.ptw-ag01.plus.net (195.166.128.195)  38.235 ms  38.253 ms  38.834 ms

[#5]

Last week we had alittle lighting and thunder, but ive noticed speed and ping issues for the past 3 weeks, ive never asked about it because sometimes your connection can have its up and downs. Todays been the worst by far for the speed and ping issues. Theres no noise on my phoneline all that seams normal.
The only other thing i can think of is that 2 week ago i had issues with playing battlefield 3 like a few other pn customers, i was getting odd lagg spikes which other customers posted about in the gaming section. We were told by mr.p.richardson i think it was that a temp fix had been put in place in order to carry on gaming.
Im not 100% sure but maybe this could have somthing to do with it.. well im just trying to rule things out.
Ive no idea why my connections like this, this is why ive dropped a support ticket in and asked you guys for advice.

[#6]

Maybe someone from the PN team can post your Radius log. What ever "fixes" they put on the network (traffic management I would guess) it won't directly affect your connection in this way. When you first noticed your ping had gone high was it similar to now?

Jeremy, Why, what's your normal time on that gateway. All looks OK pinging it from here.
Edit: rephrase question.

[#7]

noticed it going high about 3 weeks ago and it was then i noticed my speed slightly dropping. Im into my 4th month with PN now, my first 3 months was great but i was getting 10 meg speeds but each month/week it drops alittle, my av speed when working correctly is about 7/8 meg and aping of 25-30, upload speeds have always been the same and they have never changed so theres no issues with those.

Ok before i go to bed this is latest

[#8]

Post stats again tomorrow as I suggested earlier. It's possible that the lightning may have been responsible for the errors on your stats in reply #2.
The Gateway you were on before you rebooted might have had it's own issues.

[#9]

Quote from: Un

Quote jeremy@HECTOR:~$ traceroute 195.166.128.195 traceroute to 195.166.128.195 (195.166.128.195), 30 hops max, 60 byte packets 1  ROUTER (192.168.1.1)  1.865 ms  1.848 ms  1.837 ms 2  lo0-central10.ptw-ag01.plus.net (195.166.128.195)  38.235 ms  38.253 ms  38.834 ms

Strange...

Quote

jeremy@HECTOR:~$ ping 195.166.128.195 PING 195.166.128.195 (195.166.128.195) 56(84) bytes of data. 64 bytes from 195.166.128.195: icmp_req=1 ttl=126 time=10.5 ms 64 bytes from 195.166.128.195: icmp_req=2 ttl=126 time=10.6 ms 64 bytes from 195.166.128.195: icmp_req=3 ttl=126 time=10.3 ms 64 bytes from 195.166.128.195: icmp_req=4 ttl=126 time=12.9 ms ^C --- 195.166.128.195 ping statistics --- 4 packets transmitted, 4 received, 0% packet loss, time 3004ms rtt min/avg/max/mdev = 10.330/11.128/12.975/1.078 ms

10ms is only a little high but traceroute gives much larger times...

[#10]

Mode: ADSL_2plus
Traffic Type: ATM
Status: Up
Link Power State: L0  
 
 Downstream Upstream
Line Coding(Trellis): On On
SNR Margin (0.1 dB): 113 289
Attenuation (0.1 dB): 320 139
Output Power (0.1 dBm): 0 121
Attainable Rate (Kbps): 11232 1124
 
 Path 0   Path 1  
 Downstream Upstream Downstream Upstream
Rate (Kbps): 8679 444 0 0
 
MSGc (# of bytes in overhead channel message): 59 10 0 0
B (# of bytes in Mux Data Frame): 135 63 0 0
M (# of Mux Data Frames in FEC Data Frame): 1 1 0 0
T (Mux Data Frames over sync bytes): 2 1 0 0
R (# of check bytes in FEC Data Frame): 10 0 0 0
S (ratio of FEC over PMD Data Frame length): 0.4995 4.5309 0.0 0.0
L (# of bits in PMD Data Frame): 2338 113 0 0
D (interleaver depth): 64 1 0 0
Delay (msec): 7.99 1.13 0.0 0.0
INP (DMT symbol): 1.9 0.0 0.0 0.0
 
Super Frames: 2619854 495499 0 0
Super Frame Errors: 0 0 0 0
RS Words: 340581094 0 0 0
RS Correctable Errors: 8744032 0 0 0
RS Uncorrectable Errors: 6773 0 0 0
 
HEC Errors: 4294967289 844 0 0
OCD Errors: 1 0 0 0
LCD Errors: 0 0 0 0
Total Cells: 870710785 116492 0 0
Data Cells: 4008711 1223 0 0
Bit Errors: 0 0 0 0
 
Total ES: 805 0
Total SES: 0 0
Total UAS: 32 4294967244

Bt speed tester shows the following
Download speedachieved during the test was - 6.88 Mbps
For your connection, the acceptable range of speeds is 2 Mbps-7.15 Mbps.
IP Profile for your line is - 7.66 Mbps
Upload speed achieved during the test was - 0.36Mbps
Additional Information:
Upstream Rate IP profile on your line is - 0.45 Mbps

[#11]

[#12]

Kelly are you able to explain what that shows/tells us please Is it looking normal and if so then why/how have i been having some issues as reported.
Dont take any of my posts the wrong way, im just trying to get to the bottom of my sluggish connection over the past 3 weeks.

[#13]

Each red and green spike shows where your router has disconnected and then reconnected.  I don't know how often is likely to cause a problem; one of the Digicare guys will have a better idea.  It's worth working out if you did these disconnections yourself, or if it was something else which disconnected the router.

[#14]

The only disconnection i did was last night so this tells me somthings not right somewhere. If one of your guys could look into it deeper id be greatful.

[#15]

The stats you posted in reply #2 show "System Running time: 4 day(s) 23:57:58" which implies that there was a reboot on the 16th not long before 8 p.m.  This ties in with one of the events on the Radius log graph (otherwise known as a connection chart). Please bear in mind, the Radius log is showing the state of your PPP session, not sync with the exchange., although a loss of sync generally results in a session drop.
If you Gateway hop (using Disconnect/Connect) this results in a session close and session start.
Also bear in mind that a reboot can be caused by power dips/outages, as well as line faults, and bursts of interference maybe caused by lightning or other significant electrical disturbance.
In view of you last stats. no loss of sync occurred last night and the SNRM has improved today (11.3). If it is still showing close to that figure, I would try a reboot and then monitor the situation for a while. Post stats immediately after the resync and when you post them can you make sure they include the last few lines upto system running time.
The infrequency of the session drops in themselves indicate there may have been some problem but not severe enough (without other evidence) to track down a specific fault. Plugging into the test socket would also be a bit pointless at this time unless you find the problems continue over the next few days. The number of ES errors since last night (although not enormous) suggest there could well be an underlying fault. But, if the line turns out to be stable over the next few days, it would then be worth asking for Interleaving to be turned off.