Interleaving Request

[#1]

I have an app running on my PC which performs a brief test of my connection once an hour.
It pings bbc.co.uk and results have been consistent at around 15ms.
At around 4:45pm on the 15th of this month it jumped to 28ms and has stayed there.
I checked my TBB graph which confirmed it.
What would cause this solid change rather than a fluctuation....my D/L and U/L speeds haven't changed.
Update: I have rebooted my router and D/L sync has gone from 13806Kbps to 14776Kbps....now I'm worried.

[#2]

This may sound harsh, and its not meant to come across that way, but if you're not experiencing any loss in real world usage, which a 13ms ping drop wouldn't be noticeable IMO, personally I wouldn't say this was a problem as such?

[#3]

I'll see how it affects gaming.
I see a lot harsher comments than that on here avinitski

[#4]

As a big gamer myself I wouldn't be able to tell the difference between 15ms and 28ms, but that's just me.

[#5]

The DLM has switched on your interleaving
The ping figure match those typically for ADSL (30 interleaved, 15 fast path)

[#6]

I'll check that tomorrow...thanks.

[#7]

@x47c    so it is. I wonder what caused that to happen
I might just leave it alone for and see how things progress especially considering my sync has gone up by 1Mbs.
Maybe one of the DC guys can nudge my profile on Monday up to 13Mbs to match BT

[#8]

Do you know what Gateways you were on initially and then before and after the reboot?
Is your Billion reporting RS errors or are they still 0 ?

[#9]

Would anyone know if ping times include DNS forward / reverse lookup time?
Or would a delay in DNS responsiveness as per http://community.plus.net/forum/index.php/topic,115025.0.html simply impact the time to display the ping result?
Might be grasphing at straws or pointing to red herrings... there again...!

Kevin

[#10]

Straws perhaps? No issue with my pings, despite the DNS issues I am seeing, unless it's Gateway dependant as you've suggested with the DNS problems.

[#11]

@Anotherone I didn't note the gateway unfortunately.
Current stats attached.
I didn't have RouterStats running on the 15th but here is the log around that time:

Quote

Mon 13 May 2013  13:18:05 Rx-Noise=5.0 Tx-Noise=0.0 Rx-Sync=13895 Tx-Sync= DownstreamAttenuation=27.0 UpstreamSync=1135 nas0=12days,12:23:01 Mon 13 May 2013  13:18:35 Rx-Noise=5.0 Tx-Noise=0.0 Rx-Sync=13895 Tx-Sync= DownstreamAttenuation=27.0 UpstreamSync=1135 nas0=12days,12:23:32 Mon 13 May 2013  13:19:05 Rx-Noise=5.0 Tx-Noise=0.0 Rx-Sync=13895 Tx-Sync= DownstreamAttenuation=27.0 UpstreamSync=1135 nas0=12days,12:24:04 Mon 13 May 2013  13:19:35 Rx-Noise=5.0 Tx-Noise=0.0 Rx-Sync=13895 Tx-Sync= DownstreamAttenuation=27.0 UpstreamSync=1135 nas0=12days,12:24:35 Fri 17 May 2013  14:15:47 Rx-Noise=7.7 Tx-Noise=0.0 Rx-Sync=13806 Tx-Sync= DownstreamAttenuation=27.0 UpstreamSync=1124 nas0=1days,23:47:25 Fri 17 May 2013  14:16:17 Rx-Noise=7.7 Tx-Noise=0.0 Rx-Sync=13806 Tx-Sync= DownstreamAttenuation=27.0 UpstreamSync=1124 nas0=1days,23:47:57 Fri 17 May 2013  14:16:50 Rx-Noise=7.7 Tx-Noise=0.0 Rx-Sync=13806 Tx-Sync= DownstreamAttenuation=27.0 UpstreamSync=1124 nas0=1days,23:48:31 Fri 17 May 2013  14:17:17 Rx-Noise=7.7 Tx-Noise=0.0 Rx-Sync=13806 Tx-Sync= DownstreamAttenuation=27.0 UpstreamSync=1124 nas0=1days,23:49:00 Fri 17 May 2013  14:18:08 nas0=1days,23:49:00  (Router rebooted) Fri 17 May 2013  14:18:20 Rx-Noise=0.0 Tx-Noise=0.0 Rx-Sync= Tx-Sync= DownstreamAttenuation= UpstreamSync= nas0=1days,23:49:00 Fri 17 May 2013  14:18:47 Rx-Noise=5.9 Tx-Noise=0.0 Rx-Sync=14766 Tx-Sync= DownstreamAttenuation=27.0 UpstreamSync=1124 nas0=0days,00:00:00 Fri 17 May 2013  14:19:17 Rx-Noise=6.1 Tx-Noise=0.0 Rx-Sync=14766 Tx-Sync= DownstreamAttenuation=27.0 UpstreamSync=1124 nas0=0days,00:00:39 Fri 17 May 2013  14:19:47 Rx-Noise=6.1 Tx-Noise=0.0 Rx-Sync=14766 Tx-Sync= DownstreamAttenuation=27.0 UpstreamSync=1124 nas0=0days,00:01:11 Fri 17 May 2013  14:20:17 Rx-Noise=6.1 Tx-Noise=0.0 Rx-Sync=14766 Tx-Sync= DownstreamAttenuation=27.0 UpstreamSync=1124 nas0=0days,00:01:42 Fri 17 May 2013  14:20:49 Rx-Noise=6.1 Tx-Noise=0.0 Rx-Sync=14766 Tx-Sync= DownstreamAttenuation=27.0 UpstreamSync=1124 nas0=0days,00:02:15 Fri 17 May 2013  14:21:17 Rx-Noise=6.1 Tx-Noise=0.0 Rx-Sync=14766 Tx-Sync= DownstreamAttenuation=27.0 UpstreamSync=1124 nas0=0days,00:02:45 Fri 17 May 2013  14:21:47 Rx-Noise=6.1 Tx-Noise=0.0 Rx-Sync=14766 Tx-Sync= DownstreamAttenuation=27.0 UpstreamSync=1124 nas0=0days,00:03:16 Fri 17 May 2013  14:22:17 Rx-Noise=6.1 Tx-Noise=0.0 Rx-Sync=14766 Tx-Sync= DownstreamAttenuation=27.0 UpstreamSync=1124 nas0=0days,00:03:47

[#12]

Well Interleaving is definitely on Downstream as you can see from the stats - depth 64 on the Upstream it isn't on - depth 1 and No RS errors.
If Interleaving wasn't on before, then for it to be on now at depth 64 coupled with the number of RS corrected and uncorrected errors suggests a noisy environment to me.
Your sync speed is lower than I would have expected for your attenuation as well. But at least the CRC, HEC and ES errors are pretty reasonable in the circumstances.
Do you have any previously saved stats from before this cropped up?

[#13]

I've been told in the past that it is impossible to have downstream interleaving on and upstream fastpath on ADSL2+
I knew the source was talking out of their arrrrrrrrse....but you know...........you just give up and go and do the ironing instead
This image proves it is possible....Cheers

[#14]

Stats from the 13th attached.
Thanks for your comments so far Anotherone.
At first I thought OR had been in my cabinet with a tin of Brasso when I saw the new sync rate.

[#15]

The DLM would have been
Unhappy at the CRC's,
Distressed at the Error Seconds
Outraged at the Severe Error Seconds
So 'on' goes the interleaving.............