Hello Kami & welcome to the Kitz forum.
There are 3 speed sets reported in various places.
We need to be clear which you refer to.
Attainable rate - Reported by the modem as Max: Upstream rate = 15760 Kbps, Downstream rate = 49304 Kbps
Sync speed - Reported by the modem as Path: 0, Upstream rate = 15425 Kbps, Downstream rate = 42273 Kbps
IP Profile - Reported via BT's speed test
http://test.speedtester.bt.com/It should be noted that IP Profile is only updated when the
ROUTER has initiated a new PPPoE session.
The Openreach
MODEM can resync "on the fly" without causing a new PPPoE session, so the IP Profile as reported by the BT test can sometimes/often be incorrect.
The only sure way to ensure the correct IP Profile is being reported by BT is to force a new PPPoE session by disconnecting & reconnecting via the
ROUTER.
This will not be seen by DLM as instability whereas disconnecting & reconnecting the
MODEM would be.
However, we can quite accurately calculate IP Profile as 96.79% of sync speed.
e.g. a capped 40Mb service will have a sync speed of 39999 k (39.999Mb)
IP Profile = 39999 x 96.79% = 38715 k.
This would be reported as 38.72 Mbps by the BT speed test.
If BT's IP Profile has been updated, it should be reported as 40.92 Mbps for your sync speed of 42273 k.
As mentioned by
asbokid, the Windows Graphing Scripts would help in graphically plotting current and/or ongoing statistics.
Alternatively, but much harder to study over time, would be to run xdslcmd info --stats and xdslcmd info pbParams at regular intervals, posting the results here if you wish to discuss matters.
I see that DS Interleaving is on at a fairly low level, Impulse Noise Protection & delay are also on for your connection.
You only had 8 errored seconds within the 4 hour period & no serious errored seconds.
Your error counts are not massive, but could be monitored over time.
I had exactly the same symptoms when engineers messed about at the top of the pole with my DP on it while they were providing new connections from another DP on the same pole for other users.
It eventually turned out to be a very weak underground cable connection to my DP that took
3 MONTHS from first reporting it, regularly providing proof of intermittent disconnections etc. before it was finally fixed.
The cable end actually fell off in the engineer's hands as he was checking the joint.
I actually now suspect this dodgy joint had been a major contributor to my connection issues over the last 11 months.
The 12 month anniversary of FTTC being installed at my home was 2 days ago & it's still not performing as well as it did for the first month.
Much patience is required at times when attempting to get FTTC connection issues dealt with.
