Thanks for the replies, it makes sense now.
I saw this link http://bt.custhelp.com/app/answers/detail/a_id/9760/~/what-is-my-broadband-ip-profile-and-why-is-it-... which says that after 3 days of stable connection, the exchange will return the IP profile to it's pre-fault rate.
The hub is still connected to the test socket, so hopefully I will find out in the next day or so if it's me or them.
Do you think there is a chance there was a fault in the past which caused it to drop so much, and now the fault is fixed but the IP Profile/DLM got stuck or something? I don't know if it is possible to get stuck.
I think that was these two figures from the first page:
|Data rate:||19890 / 61908|
|Maximum data rate:||24737 / 62830|
Which seems to be correct then
Sorry, I mis-read your last post. These are the only entries in the WAN section for reconnects before the log stops.
13:47:01, 11 Feb. (92382.000000) PPPoE is up - Down Rate=62327000Kbps, Up Rate=19671000Kbps; SNR Margin Down=6.5dB, Up=6.0dB
12:28:00, 10 Feb. ( 1241.280000) PPPoE is up - Down Rate=62307000Kbps, Up Rate=19876000Kbps; SNR Margin Down=6.5dB, Up=5.8dB
17:34:34, 02 Feb. ( 1859.690000) PPPoE is up - Down Rate=61908000Kbps, Up Rate=19890000Kbps; SNR Margin Down=6.6dB, Up=5.8dB
I changed to the test socket on the 10th and on the 11th I pressed disconnect/connect link in the homehub admin panel.
Todays other data:
|6. Data rate:||19671 / 62327|
|7. Maximum data rate:||24608 / 62449|
|8. Noise margin:||6.1 / 6.5|
|9. Line attenuation:||15.5 / 13.6|
|10. Signal attenuation:||15.6 / 13.7|
I just don't understand why, if the noise margin is optimal, then why am I at the lower end of the impacted line. Would a impacted line not have a higher noise margin? Thanks again
Also the IP Profile now says:
For your connection, the acceptable range of speeds is 60 Mbps-60.33 Mbps
IP Profile for your line is - 60.33 Mbps
So again it has gone up a tiny bit.