Latency improvement

[gymno]

Just realised that the gateway ipv4 address shown in the router's gui has changed.

It still doesn't respond to my pings, but as with the previous address (which i'm sure has never changed before) it does show up on a ping or reverse trace using the tools here

Old gateway address:
traceroute to 2.127.238.127 (2.127.238.127), 25 hops max, 40 byte packets
1 static-ip-188-138-112-3.inaddr.ip-pool.com (188.138.112.3) 1.409 ms
2 217.118.16.161 (217.118.16.161) 0.316 ms
3 149.14.12.49 (149.14.12.49) 0.597 ms
4 te0-3-0-2.rcr21.sxb01.atlas.cogentco.com (154.54.74.245) 0.957 ms
5 be2476.ccr41.fra03.atlas.cogentco.com (130.117.1.246) 4.160 ms
6 be2184.agr21.fra03.atlas.cogentco.com (130.117.48.69) 4.275 ms
7 tiscali.fra03.atlas.cogentco.com (130.117.14.86) 3.526 ms
8 xe-1-3-0.lon80.ip4.gtt.net (89.149.182.94) 18.830 ms
9 bskyb-gw.ip4.gtt.net (77.67.65.174) 19.070 ms
10 sr10.enips.isp.sky.com (2.127.238.127) 25.983 ms

new gateway address:
traceroute to 2.127.238.114 (2.127.238.114), 25 hops max, 40 byte packets
1 static-ip-188-138-112-3.inaddr.ip-pool.com (188.138.112.3) 1.429 ms
2 217.118.16.162 (217.118.16.162) 0.286 ms
3 te1-8.ccr01.sxb03.atlas.cogentco.com (149.11.26.9) 0.484 ms
4 te0-5-1-7.rcr21.sxb01.atlas.cogentco.com (154.54.38.97) 0.847 ms
5 be2477.ccr42.fra03.atlas.cogentco.com (130.117.49.34) 4.286 ms
6 be2188.agr21.fra03.atlas.cogentco.com (130.117.48.113) 4.720 ms
7 tiscali.fra03.atlas.cogentco.com (130.117.14.86) 3.620 ms
8 xe-0-0-1.lon80.ip4.gtt.net (141.136.106.182) 18.654 ms
9 bskyb-gw.ip4.gtt.net (77.67.65.174) 19.001 ms
10 sr10.enbas.isp.sky.com (2.127.238.114) 20.723 ms

[Angel_Rex]

My latency went up 2 days ago from 8ms to bbc.co.uk to 16ms



PING 212.58.244.20 (212.58.244.20): 56 data bytes
64 bytes from 212.58.244.20: seq=0 ttl=57 time=16.072 ms
64 bytes from 212.58.244.20: seq=1 ttl=57 time=15.851 ms
64 bytes from 212.58.244.20: seq=2 ttl=57 time=15.762 ms
64 bytes from 212.58.244.20: seq=3 ttl=57 time=15.697 ms


PING 216.58.210.67 (216.58.210.67): 56 data bytes
64 bytes from 216.58.210.67: seq=0 ttl=59 time=17.396 ms
64 bytes from 216.58.210.67: seq=1 ttl=59 time=17.578 ms
64 bytes from 216.58.210.67: seq=2 ttl=59 time=17.539 ms
64 bytes from 216.58.210.67: seq=3 ttl=59 time=17.428 ms


PING 212.58.246.103 (212.58.246.103): 56 data bytes
64 bytes from 212.58.246.103: seq=0 ttl=58 time=17.718 ms
64 bytes from 212.58.246.103: seq=1 ttl=58 time=16.567 ms
64 bytes from 212.58.246.103: seq=2 ttl=58 time=16.253 ms
64 bytes from 212.58.246.103: seq=3 ttl=58 time=16.698 ms


Interestingly though : this one -
PING 90.222.188.237 (90.222.188.237): 56 data bytes
64 bytes from 90.222.188.237: seq=0 ttl=62 time=8.835 ms
64 bytes from 90.222.188.237: seq=1 ttl=62 time=8.855 ms
64 bytes from 90.222.188.237: seq=2 ttl=62 time=8.302 ms
64 bytes from 90.222.188.237: seq=3 ttl=62 time=8.471 ms

[gymno]

Interesting.

Did you have a resync causing a change of ip address 2 days ago?
If so it looks like you may be seeing the same phenomena that i had for a long time - different addresses apparently being routed differently.

[Angel_Rex]

Nope, same IP. Connection been up for 18 days.

DSLAM/MSAN type: BDCM:0xa459 / v0xa459
Modem/router firmware: AnnexA version - A2pv6C038m.d24j
DSL mode: VDSL2 Profile 17a
Status: Showtime
Uptime: 18 days 8 hours 40 min 41 sec
Resyncs: 0 (since 12 Oct 2015 19:05:02)

Downstream Upstream
Line attenuation (dB): 22.9 0.0
Signal attenuation (dB): Not available on VDSL2
Connection speed (kbps): 40000 6604
SNR margin (dB): 6.8 6.4
Power (dBm): 11.0 -1.3
Interleave depth: 16 1
INP: 45.00 0
G.INP: Enabled

RSCorr/RS (%): 0.3744 0.2849
RSUnCorr/RS (%): 0.0000 0.0000
ES/hour: 1.43 12.5

[gymno]

OK.

My issue ran from jan 2014 right up until yesterday (hopefully) with 1 main break of 5 months when things went back to normal immediately after sky did some maintenance on the network.

After some time i became aware that a new ip address wasn't needed for the phenomena to occur (although initially it did make it more obvious).

Here's the best example i have of that because all 3 latency levels i experienced are on the same graph:


If latency is important to you, i'd say it's worth keeping an eye on.
Or even if it isn't, because every one of those 'switchover' points on my graph would destroy a download, it's definitely worth keeping an eye on.

[Angel_Rex]

[gymno]

Yeah, see if you're getting 8ms to google.co.uk then normally one would expect to see around 8ms to bbc & the tbb bqm (80.249.99.164) too.
(The bqm is usually 1ms above other benchmark addresses from my experience).

Your bqm looks to be more like 17ms & matches your pings to bbc, which until recently were 8ms.

Folks more knowledgeable than me may have something more complex to add, however all i can say is that the tbb bqm is / was a great indicator of when my line's problematic 'switchover's' occurred.

[marjohn56]

Deleted

[gymno]

From here: http://www.skyuser.co.uk/forum/sky-r...tml#post455343

Any reason the trace to google differs to bbc??


Tracing route to google.co.uk [2.127.252.231]
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 10 ms 10 ms 10 ms be104.pr2.thlon.isp.sky.com [2.120.10.118]
5 9 ms 9 ms 9 ms 02780a33.bb.sky.com [2.120.10.51]
6 9 ms 9 ms 8 ms host231-rangeB-google-ggc.cdn.thlon.isp.sky.com
[2.127.252.231]


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 17 ms 18 ms 16 ms ip-84-38-37-36.easynet.co.uk [84.38.37.36]
4 16 ms 16 ms 16 ms ntl-ge2-9.prt0.rbsov.bbc.co.uk [212.58.238.189]

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

I don't know, but that's obviously where the latency increase is.
Hop 2 should be your exchange & so presumably hop 3 should be sky's core network.

Traceroutes are something i wasn't able to do for the near 22 months i had this issue, so already you're further towards understanding it than i ever was.
And i'm quite sure now that you are seeing the exact same phenomena i had.

Take your bqm from here for instance:
(Which btw is currently a live graph, not a static snapshot one).


That temporary drop back to normal at midnight was very common for me & you've had it 2 nights in a row now:


Do you know if you are connected directly to a 'main' exchange or a smaller daisy chained 'satellite' one?

[Angel_Rex]

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??