Latency/ping times query.

For my connection would it be too much to assume that an increase in latency/ping times is due to Plusnet putting Madasafish users (my exchange is 20CN) onto IPStream Connect (IPSC) to link to the rest of their WBC setup?

How much of a change?

This was done a few minutes ago:-

Pinging bbc.co.uk [212.58.241.131] with 32 bytes of data:

Reply from 212.58.241.131: bytes=32 time=61ms TTL=247
Reply from 212.58.241.131: bytes=32 time=61ms TTL=247
Reply from 212.58.241.131: bytes=32 time=63ms TTL=247
Reply from 212.58.241.131: bytes=32 time=62ms TTL=247

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

Previously the average would be around 46ms.

An earlier 2Meg connection from madasafish had an average of around 23ms, but it was fast path.

BQM:- image link

It is worth doing a tracert just incase its something beyond the wholesale components

OK,

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

1 1 ms <1 ms <1 ms 192.168.0.1
2 64 ms 62 ms 62 ms lo0-central1.ptn-ag04.plus.net [195.166.130.22]
3 64 ms 62 ms 62 ms gi2-2-411.ptn-gw01.plus.net [84.92.2.129]
4 64 ms 63 ms 62 ms po4.ptn-gw02.plus.net [212.159.1.139]
5 62 ms 63 ms 63 ms po6.thn-gw1.plus.net [212.159.1.136]
6 63 ms 63 ms 71 ms po4.thn-gw2.plus.net [212.159.1.135]
7 62 ms 63 ms 63 ms rt0.thdo.bbc.co.uk [212.58.239.25]
8 62 ms 62 ms 62 ms 212.58.238.149
9 63 ms 62 ms 63 ms virtual-vip-231.thdo.bbc.co.uk [212.58.241.131]

Trace complete.

Your numbers look similar to my BT Business Broadband lines on 20CN only exchanges in Scotland.

Interleaving on or off?

It's on and the downstream and upstream depths are the same as they were eleven months ago according to data from the DMT tool.

Have they increased at all if the connection has changed to IPSC WBC?

Following the loss of my internet connection (no issue with exchange sync) from around 10.45pm last night and into this morning, all was back to normal when I checked at 11.55am, even the ping times/latency had gone back to around what it used to be:-

Pinging bbc.co.uk [212.58.241.131] with 32 bytes of data:

Reply from 212.58.241.131: bytes=32 time=50ms TTL=248
Reply from 212.58.241.131: bytes=32 time=48ms TTL=248
Reply from 212.58.241.131: bytes=32 time=49ms TTL=248
Reply from 212.58.241.131: bytes=32 time=49ms TTL=248

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

Wonder what happened?