Great news! The IP Profile has shifted and is now on
6500 

According to the router stats it's only taken just under 3 days
DSL Connection
Link Information
Uptime: 2 days, 21:33:52
Modulation: G.992.1 annex A
Bandwidth (Up/Down) [kbps/kbps]: 448 / 7,616
Data Transferred (Sent/Received) [MB/GB]: 421.82 / 1.85
Output Power (Up/Down) [dBm]: 11.5 / 19.5
Line Attenuation (Up/Down) [dB]: 17.0 / 29.0
SN Margin (Up/Down) [dB]: 25.0 / 6.5
Vendor ID (Local/Remote): TMMB / ALCB
Loss of Framing (Local/Remote): 0 / 0
Loss of Signal (Local/Remote): 0 / 0
Loss of Power (Local/Remote): 0 / 0
Loss of Link (Remote): 0
Error Seconds (Local/Remote): 0 / 0
FEC Errors (Up/Down): 0 / 7,150
CRC Errors (Up/Down): 0 / 46
HEC Errors (Up/Down): 0 / 43
Line Profile: Interleaved
The SNR seems to have creeped up a little though, and when monitoring it every night it goes up to 7-7.5 and I have seen it at 8. Which is a little strange as there's nothing new in the house, no roadworks going on nearby etc. It used to stay steady at 6.0 day and night.
Whilst the profile has increased in line with the sync speed, I'm a little disappointed because the ping speeds which were fantastic, have begun rising again and packet loss is being experienced quite regularly too

Although it's nowhere near as high as it was, it's still a darn sight higher than the ~27ms is had gone down to:
Pinging google.co.uk [173.194.37.104] with 32 bytes of data:
Reply from 173.194.37.104: bytes=32 time=128ms TTL=52
Reply from 173.194.37.104: bytes=32 time=117ms TTL=52
Reply from 173.194.37.104: bytes=32 time=122ms TTL=52
Reply from 173.194.37.104: bytes=32 time=136ms TTL=52
Ping statistics for 173.194.37.104:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 117ms, Maximum = 136ms, Average = 125ms
What could explain this? The router is pretty ancient, we've had it for about 6 years. I do have a home hub 2.0 which I haven't tried, but was planning to hook up after sorting everything else out. I've read mixed reviews about the 2.0 causing more problems though so I'm in two minds whether to bother or not?
Interleaving is still turned on btw, which I understand does increase latency slightly, but I don't think explains the sudden rise in latency from a low steady ~26-27ms. And it's all still plugged into the test socket via a filter. Could it help if I changed the filter possibly?
Edited by deleted (Tue 11-Jan-11 15:58:19)