Latency improvement

[Angel_Rex]

Well, I've just checked my stats - http://www.mydslwebstats.co.uk/Container.htm Username Angel-Rex

None of my G.INP or and line settings were changed so this can only be routing.

Possibly shaping?

[gymno]

I posted the 'live graph' intentionally!

I was going to say today that I've had the ping drop again. Very strange.

My house line is 790 meters from my fibre cabinet, the fibre cabinet then goes a further 1km to the main exchange in Uckfield - NDUCK.

- - - Updated - - -

As a thought, we know DLM makes more changes in the 'wee' hours.

Could DLM / G.INP be dropping the ping, line errors increase then DLM is putting the interleaved depth back up??

Regarding your exchange, i guess i was asking if NDUCK was a main or satellite one.
It doesn't really matter, it's just that i know mine is in a chain of 3 - one of two before the main one.

If it is the same issue i had then it won't be DLM making profile changes.
I'm on ADSL & everything requires a resync to take effect, which often didn't happen (& in relation to any graph i post never did).
Besides, parameters like interleave depth will affect the ping wholesale & not only to some addresses.

I'd be willing to bet that had you pinged bbc between 12 & 6 this morning it would have been back to the normal 8ms too.
Then what the traceroute revealed would be really interesting.

Possibly shaping?

TBH i think i'm already a little way past my knowledge of such things.

[Angel_Rex]

Ok, I'll do a tracert at 1am

[gymno]

Ok, I'll do a tracert at 1am

Any time during a period of normality where the bqm shows 8ms again is good, although admittedly for me that was between 12 & 6am 90% of the time.

Occasionally though it would occur at other times, which is when the phenomena went from being a mere curiousity to an actual problem because any download running at the switchover point would be killed.
Luckily i'm not one of those folks who like to stack up downloads to run overnight.

I've not gamed online during a switchover but i have browsed a lot & all that happened then was that the next page/link i clicked on wouldn't load.
A quick refresh sorted that out every time.

So unless you are a night-time downloader i can't see it causing any actual problems.
It would be great to get to the bottom of why it's happening though...

[Angel_Rex]

Just noticed :

Pinging bbc.co.uk [212.58.244.20] with 32 bytes of data:
Reply from 212.58.244.20: bytes=32 time=9ms TTL=56
Reply from 212.58.244.20: bytes=32 time=9ms TTL=56
Reply from 212.58.244.20: bytes=32 time=9ms TTL=56
Reply from 212.58.244.20: bytes=32 time=9ms TTL=56

Ping statistics for 212.58.244.20:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 9ms, Maximum = 9ms, Average = 9ms



Pinging google.co.uk [2.127.252.237] with 32 bytes of data:
Reply from 2.127.252.237: bytes=32 time=9ms TTL=61
Reply from 2.127.252.237: bytes=32 time=9ms TTL=61
Reply from 2.127.252.237: bytes=32 time=9ms TTL=61
Reply from 2.127.252.237: bytes=32 time=10ms TTL=61

Ping statistics for 2.127.252.237:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 9ms, Maximum = 10ms, Average = 9ms

[Angel_Rex]

Tracing route to thinkbroadband.com [80.249.99.130]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 * * * Request timed out.
3 18 ms 19 ms 19 ms ip-84-38-37-36.easynet.co.uk [84.38.37.36]
4 18 ms 18 ms 18 ms linx-gw2.thdo.ncuk.net [195.66.236.240]
5 19 ms 20 ms 18 ms po3-30.core-rs1.thdo.ncuk.net [80.249.97.81]
6 18 ms 18 ms 18 ms thinkbroadband :: The UK's largest independent Broadband / ADSL troubleshooting website (incorporating news, reviews and comparisons) [80.249.99.130]

Trace complete.

Tracing route to bbc.co.uk [212.58.244.20]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 * * * Request timed out.
3 10 ms 10 ms 10 ms ip-84-38-37-34.easynet.co.uk [84.38.37.34]
4 9 ms 10 ms 9 ms ntl-ge2-9.prt0.rbsov.bbc.co.uk [212.58.238.189]

5 * * * Request timed out.
6 * * * Request timed out.
7 9 ms 9 ms 9 ms ae0.er01.telhc.bbc.co.uk [132.185.254.109]
8 10 ms 10 ms 14 ms 132.185.255.149
9 9 ms 9 ms 10 ms fmt-vip71.telhc.bbc.co.uk [212.58.244.20]

Trace complete.

Tracing route to google.co.uk [2.127.252.177]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 * * * Request timed out.
3 10 ms 11 ms 10 ms ip-84-38-37-34.easynet.co.uk [84.38.37.34]
4 11 ms 9 ms 10 ms be104.pr2.thlon.isp.sky.com [2.120.10.118]
5 * 9 ms 10 ms 02780a33.bb.sky.com [2.120.10.51]
6 9 ms 9 ms 9 ms host177-rangeA-google-ggc.cdn.thlon.isp.sky.com
[2.127.252.177]

Trace complete.

[gymno]

So...

Hop 3 with pings to BBC at 17ms:
3 17 ms 18 ms 16 ms ip-84-38-37-36.easynet.co.uk [84.38.37.36]

Hop 3 with pings to BBC at 9ms:
3 10 ms 10 ms 10 ms ip-84-38-37-34.easynet.co.uk [84.38.37.34]

Hop 3 with pings to google at 9ms:
3 10 ms 10 ms 10 ms ip-84-38-37-34.easynet.co.uk [84.38.37.34]

Hop 3 with pings to thinkbroadband at 18ms:
3 17 ms 18 ms 16 ms ip-84-38-37-36.easynet.co.uk [84.38.37.36]

[gymno]

The silence is deafening.

[Angel_Rex]

Nothing really to add I guess

Routing seems to change.

I noticed that my line retrained on Wednesday early hours last week and I didnt notice until Friday. Odd though.

[Angel_Rex]

was fine this morning and now.......



Tracing route to bbc.co.uk [212.58.244.20]
over a maximum of 30 hops:

1 1 ms 1 ms 2 ms 192.168.0.1
2 * * * Request timed out.
3 18 ms 17 ms 18 ms ip-84-38-37-36.easynet.co.uk [84.38.37.36]
4 18 ms 17 ms 17 ms ntl-ge2-9.prt0.rbsov.bbc.co.uk [212.58.238.189

5 * * * Request timed out.
6 * * * Request timed out.
7 24 ms 58 ms 19 ms ae0.er01.telhc.bbc.co.uk [132.185.254.109]
8 21 ms 18 ms 21 ms 132.185.255.149
9 19 ms 17 ms 17 ms fmt-vip71.telhc.bbc.co.uk [212.58.244.20]

Trace complete.