Recent increase in Ping

Sorry to moan guys but I have noticed a 10ms increase in ping to websites such as bbc.co.uk

use to be in mid teens but now mid 20's

the increase seems to be starting from 3rd hop

Target Name: www.bbc.co.uk
IP: 212.58.246.93
Date/Time: 17/06/2013 10:27:48 to 17/06/2013 10:27:55

1 2 ms 2 ms 2 ms 2 ms 5 ms 2 ms 2 ms 2 ms home.gateway.home.gateway [192.168.1.254]
2 15 ms 15 ms 14 ms 15 ms 15 ms 15 ms 20 ms 14 ms lo0-central10.ptw-ag03.plus.net [195.166.128.197]
3 24 ms 29 ms 25 ms 25 ms 25 ms 24 ms 24 ms 25 ms link-a-central10.ptw-gw01.plus.net [212.159.2.152]
4 24 ms 25 ms 25 ms 25 ms 24 ms 24 ms 24 ms 24 ms xe-7-2-0.ptw-cr01.plus.net [212.159.1.20]
5 24 ms 24 ms 25 ms 25 ms 24 ms 24 ms 24 ms 24 ms kingston-gw.thdo.bbc.co.uk [212.58.239.6]
6 * * * * * N/A N/A N/A [-]
7 26 ms 25 ms 26 ms 29 ms 24 ms 25 ms 25 ms N/A ae0.er01.cwwtf.bbc.co.uk [132.185.254.93]
8 26 ms 26 ms 28 ms 26 ms 26 ms 26 ms 26 ms N/A [132.185.255.164]
9 25 ms 24 ms 25 ms 26 ms 29 ms 25 ms 25 ms N/A bbc-vip014.cwwtf.bbc.co.uk [212.58.246.93]

Ping statistics for www.bbc.co.uk
Packets: Sent = 7, Received = 7, Lost = 0 (0.0%)
Round Trip Times: Minimum = 24ms, Maximum = 29ms, Average = 25ms

Edited by Stanman_24 (Mon 17-Jun-13 10:29:09)

DLM has changed connection from Fast Path to Interleaved. Nowt you can do about it.

Not so sure....

The router to the gateway is 14ms which is quite normal for fastpath, unlikely to be interleaved, and then within their own network (ISP), it increases by 10~ms.

Matt

exactly

are you sure?

14ms to gateways is high, some isps can get the user to london for under 10ms over 100miles.

my gateway (on diff isp) is 5ms.

My base latency on fast path with IDNet was 13ms. On moving to PlusNet it stayed the same for a while then went up to 21ms when interleaving was turned on.

Yes. Such low latency depends on your locality too.

The key was in the OPs original post where he said latency has gone up 10ms and is now mid-20s, which if you review the trace, shows 14ms on the second hop (gateway) increasing by around 10ms on the third hop which then remains 25~ throughout.

This shows the increase is within the PN network, not the line, otherwise second hop would have the increase too.

Matt

Possibly restricted to that gateway?

Mine is fine (though this is from an ADSL2+line):

$ tracert www.bbc.co.uk

Tracing route to www.bbc.net.uk [212.58.246.91]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.0.1
  2    15 ms    13 ms    13 ms  lo0-central10.pcl-ag01.plus.net [195.166.128.182]
  3    13 ms    12 ms    12 ms  link8-central10.pcl-gw02.plus.net [84.93.249.14]
  4    12 ms    12 ms    12 ms  194.core.access.plus.net [212.159.0.194]
  5    12 ms    12 ms    12 ms  ae2.pcl-cr01.plus.net [195.166.129.6]
  6    14 ms    11 ms    13 ms  ae1.ptw-cr01.plus.net [195.166.129.0]
  7    12 ms    12 ms    11 ms  kingston-gw.thdo.bbc.co.uk [212.58.239.6]
  8     *        *        *     Request timed out.
  9    14 ms    43 ms    13 ms  ae0.er01.cwwtf.bbc.co.uk [132.185.254.93]
 10    13 ms    16 ms    13 ms  132.185.255.164
 11    13 ms    13 ms    13 ms  bbc-vip012.cwwtf.bbc.co.uk [212.58.246.91]

Trace complete.

Mine is very similar to yours and I'm on the same gateway as the OP:

Text

1 23 45 67 89 1011 1213 1415

Tracing route to bbc.co.uk [212.58.253.67] over a maximum of 30 hops:    1    <1 ms    <1 ms     1 ms  zyxel.com [192.168.1.2]  2    13 ms    13 ms    13 ms  lo0-central10.pcl-ag03.plus.net [195.166.128.184]   3    12 ms    12 ms    12 ms  link9-central10.pcl-gw01.plus.net [84.93.249.80]  4    12 ms    12 ms    12 ms  200.core.access.plus.net [212.159.0.200]   5    12 ms    12 ms    12 ms  ae1.ptw-cr01.plus.net [195.166.129.0]  6    12 ms    12 ms    12 ms  kingston-gw.thdo.bbc.co.uk [212.58.239.6]   7     *        *        *     Request timed out.  8    13 ms    13 ms    13 ms  ae0.er01.cwwtf.bbc.co.uk [132.185.254.93]   9    14 ms    13 ms    13 ms  132.185.255.156 10    14 ms    13 ms    14 ms  www-vip.cwwtf.bbc.co.uk [212.58.253.67]  Trace complete.

If that's your trace, you aren't on the same gateway. OP is on a ptw gateway, that trace shows PCL.

(I'm having a look at what's caused that change)

Oh yes, wondered why the IP address was different, kept staring at it, still didn't spot the obvious!

appreciate it as Iike to boast about my ping in blops2 etc

that looks to me odd.

it seems plusnet have their gateways located close to london as is 1ms between your gateway and the bbc. or you are located in london?

Looks like -2ms to me?

6    14 ms    11 ms    13 ms  ae1.ptw-cr01.plus.net [195.166.129.0]
7    12 ms    12 ms    11 ms  kingston-gw.thdo.bbc.co.uk [212.58.239.6]

On my FTTC line I've noticed Plusnet pings go up by about 2-3ms. It coincided with the upgrades to their gateways and traffic management upgrades.

In reply to a post by Chrysalis:

it seems plusnet have their gateways located close to london as is 1ms between your gateway and the bbc. or you are located in london?

Plusnet's gateways are indeed all in London - with feeds off 3 different BT exchanges (Colindale, Faraday, Stepney, all visible on the network performance graphs)

The gateways are, I believe located in 3 different London locations:
ptw - Telehouse West
ptn - Telehouse North
pcl - City Lifeline

I think this diagram is fairly current.

The location of the gateway is seen in the first non-local hops of the traceroute. In my case, the connection is pcl-ag03:

In reply to a post by kasg:

1 <1 ms <1 ms 1 ms zyxel.com [192.168.1.2]
2 13 ms 13 ms 13 ms lo0-central10.pcl-ag03.plus.net [195.166.128.184]

However, it does have to be said that this particular traceroute was done from a location in Surrey, so not too far from London either.

ok thanks, so yeah its different to how bt operates its own service then.

eg. here is my trace, notice a low latency to my gateway. but then higher overall latency than yours. is always a big jump to the ealing hop.

1 <1 ms <1 ms <1 ms home.gateway [192.168.1.253]
2 5 ms 5 ms 5 ms bt.gateway [217.32.144.166]
3 6 ms 6 ms 5 ms bt.internal [217.32.144.190]
4 8 ms 8 ms 7 ms bt.internal [213.120.181.58]
5 7 ms 7 ms 7 ms 217.41.169.213
6 9 ms 9 ms 8 ms bt.internal [217.41.169.109]
7 8 ms 7 ms 7 ms 109.159.251.235
8 16 ms 16 ms 15 ms core2-te-0-13-0-11.ealing.ukcore.bt.net [109.159
.251.173]
9 15 ms 16 ms 14 ms peer2-xe9-1-0.telehouse.ukcore.bt.net [109.159.2
54.114]
10 18 ms 18 ms 16 ms 194.74.65.42
11 * * * Request timed out.
12 * * * Request timed out.
13 15 ms 15 ms 17 ms ae0.er01.telhc.bbc.co.uk [132.185.254.109]
14 18 ms 18 ms 18 ms 132.185.255.140
15 16 ms 16 ms 16 ms www-vip.telhc.bbc.co.uk [212.58.251.195]

That's the experience here, too, when running a Huawei DSLAM on the bench.

The ping response from the PPP "gateway" (surely we should call this an aggregator or access concentrator?) was a minimum of 4ms. That was with the DSL connection placed on a fast path with Forward Error Correction disabled.

The ping time was measured with the "gateway" server connected directly to the DSLAM upstream port by a two metres gbE patch cable. So no issues of geographical distance adding latency. Just the packet processing overheads of the DSLAM itself, and the fast PPP server.

cheers, a

Edited by deleted (Wed 19-Jun-13 21:12:15)

I wonder if the differences are explained by BT running their service as pure WBC, while Plusnet are using a WBMC infrastructure.

All those "bt.gateway" and "bt.internal" timings would then be part of their (BT Retail) WBC infrastructure, in passing back from the individual exchanges to the "ukcore" section.

Meanwhile for Plusnet, the equivalent WBMC infrastructure (owned by BT Wholesale) stays invisible to the IP layer, so gets no individual ping timing until passing back into Plusnet's own infrastructure.

all those ips at the start have no rdns, I set the hostnames in my hosts file to stop tracert taking an age to progress. Ocassionally tho as you can see new ip's popup that I havent got in my hosts file.

But yeah basically between you and telehouse you dont see the hops on plusnet, whilst I do on BT.

Edited by Chrysalis (Thu 20-Jun-13 00:53:16)

any updates guys ?

found it to be devolo firmware I flashed to my solwise home plugs that caused the 10 ms spike

strange how the ms increase was not reflected until the 3rd hop

sorry for wasting your time guys !