I've noticed my ping has gone up to 65 from 45 on Zen over the past week.

Normal here; (London)

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

Reply from 212.58.224.138: bytes=32 time=7ms TTL=122
Reply from 212.58.224.138: bytes=32 time=7ms TTL=122
Reply from 212.58.224.138: bytes=32 time=7ms TTL=122
Reply from 212.58.224.138: bytes=32 time=8ms TTL=122

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

Edited by IamQ (Sun 24-Apr-11 13:39:27)

In reply to a post by IamQ:

Normal here; (London)

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

Reply from 212.58.224.138: bytes=32 time=7ms TTL=122
Reply from 212.58.224.138: bytes=32 time=7ms TTL=122
Reply from 212.58.224.138: bytes=32 time=7ms TTL=122
Reply from 212.58.224.138: bytes=32 time=8ms TTL=122

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

Could you post a trace please?

From the Linux box (Same end point)

[root@xs ~]# ping bbc.co.uk
PING bbc.co.uk (212.58.224.138) 56(84) bytes of data.
64 bytes from virtual-vip.thdo.bbc.co.uk (212.58.224.138): icmp_seq=1 ttl=122 time=8.22 ms
64 bytes from virtual-vip.thdo.bbc.co.uk (212.58.224.138): icmp_seq=2 ttl=122 time=7.98 ms
64 bytes from virtual-vip.thdo.bbc.co.uk (212.58.224.138): icmp_seq=3 ttl=122 time=8.21 ms
64 bytes from virtual-vip.thdo.bbc.co.uk (212.58.224.138): icmp_seq=4 ttl=122 time=7.96 ms
64 bytes from virtual-vip.thdo.bbc.co.uk (212.58.224.138): icmp_seq=5 ttl=122 time=8.16 ms
64 bytes from virtual-vip.thdo.bbc.co.uk (212.58.224.138): icmp_seq=6 ttl=122 time=7.41 ms
64 bytes from virtual-vip.thdo.bbc.co.uk (212.58.224.138): icmp_seq=7 ttl=122 time=8.13 ms
64 bytes from virtual-vip.thdo.bbc.co.uk (212.58.224.138): icmp_seq=8 ttl=122 time=7.86 ms
64 bytes from virtual-vip.thdo.bbc.co.uk (212.58.224.138): icmp_seq=9 ttl=122 time=8.58 ms
64 bytes from virtual-vip.thdo.bbc.co.uk (212.58.224.138): icmp_seq=10 ttl=122 time=8.06 ms

--- bbc.co.uk ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 9000ms
rtt min/avg/max/mdev = 7.412/8.061/8.582/0.287 ms



And the route (Over ICMP);

[root@xs ~]# traceroute -I bbc.co.uk
traceroute to bbc.co.uk (212.58.224.138), 30 hops max, 40 byte packets
1 gateway-to-the-void.goth.int (172.16.0.1) 0.216 ms 0.194 ms 0.192 ms
2 losubs.subs.dsl2.th-lon.zen.net.uk (62.3.84.21) 8.031 ms 8.477 ms 7.365 ms
3 ae0-114.cr1.th-lon.zen.net.net (62.3.84.185) 8.686 ms 8.646 ms 9.194 ms
4 82.71.254.134 (82.71.254.134) 11.313 ms 11.462 ms 12.052 ms
5 212.58.238.129 (212.58.238.129) 12.510 ms 13.959 ms 14.005 ms
6 virtual-vip.thdo.bbc.co.uk (212.58.224.138) 14.343 ms 16.138 ms 16.238 ms

In reply to a post by IamQ:

From the Linux box (Same end point)

[root@xs ~]# ping bbc.co.uk
PING bbc.co.uk (212.58.224.138) 56(84) bytes of data.
64 bytes from virtual-vip.thdo.bbc.co.uk (212.58.224.138): icmp_seq=1 ttl=122 time=8.22 ms
64 bytes from virtual-vip.thdo.bbc.co.uk (212.58.224.138): icmp_seq=2 ttl=122 time=7.98 ms
64 bytes from virtual-vip.thdo.bbc.co.uk (212.58.224.138): icmp_seq=3 ttl=122 time=8.21 ms
64 bytes from virtual-vip.thdo.bbc.co.uk (212.58.224.138): icmp_seq=4 ttl=122 time=7.96 ms
64 bytes from virtual-vip.thdo.bbc.co.uk (212.58.224.138): icmp_seq=5 ttl=122 time=8.16 ms
64 bytes from virtual-vip.thdo.bbc.co.uk (212.58.224.138): icmp_seq=6 ttl=122 time=7.41 ms
64 bytes from virtual-vip.thdo.bbc.co.uk (212.58.224.138): icmp_seq=7 ttl=122 time=8.13 ms
64 bytes from virtual-vip.thdo.bbc.co.uk (212.58.224.138): icmp_seq=8 ttl=122 time=7.86 ms
64 bytes from virtual-vip.thdo.bbc.co.uk (212.58.224.138): icmp_seq=9 ttl=122 time=8.58 ms
64 bytes from virtual-vip.thdo.bbc.co.uk (212.58.224.138): icmp_seq=10 ttl=122 time=8.06 ms

--- bbc.co.uk ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 9000ms
rtt min/avg/max/mdev = 7.412/8.061/8.582/0.287 ms



And the route (Over ICMP);

[root@xs ~]# traceroute -I bbc.co.uk
traceroute to bbc.co.uk (212.58.224.138), 30 hops max, 40 byte packets
1 gateway-to-the-void.goth.int (172.16.0.1) 0.216 ms 0.194 ms 0.192 ms
2 losubs.subs.dsl2.th-lon.zen.net.uk (62.3.84.21) 8.031 ms 8.477 ms 7.365 ms
3 ae0-114.cr1.th-lon.zen.net.net (62.3.84.185) 8.686 ms 8.646 ms 9.194 ms
4 82.71.254.134 (82.71.254.134) 11.313 ms 11.462 ms 12.052 ms
5 212.58.238.129 (212.58.238.129) 12.510 ms 13.959 ms 14.005 ms
6 virtual-vip.thdo.bbc.co.uk (212.58.224.138) 14.343 ms 16.138 ms 16.238 ms

Thanks. Interesting though. I wonder why can't I connect to the London gateway? :/

In reply to a post by Btcc22:

Thanks. Interesting though. I wonder why can't I connect to the London gateway? :/

It all depends where you are in the UK and which node your exchange is on. If you have a look at the zen network map it should make things a bit easier to understand the layout.

http://www.zen.co.uk/userfiles/images/shared/site/co...

Can you do a traceroute and ping to the same bbc address and post that back for us to have a look at.

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

1 <1 ms <1 ms <1 ms 10.0.0.2
2 20 ms 19 ms 18 ms losubs.subs.dsl1.mbr-roch.zen.net.uk [62.3.82.17
]
3 17 ms 18 ms 19 ms ae0-136.cr1.mbr-roch.zen.net.uk [62.3.80.137]
4 19 ms 18 ms 18 ms ae2-0.cr1.kp-leeds.zen.net.uk [62.3.80.70]
5 20 ms 18 ms 19 ms ge-3-1-0-0.cr2.kp-leeds.zen.net.uk [62.3.80.74]

6 23 ms 23 ms 22 ms ge-3-0-0-0.cr1.th-lon.zen.net.uk [62.3.80.78]
7 24 ms 23 ms 23 ms 82.71.254.134
8 25 ms 24 ms 23 ms 212.58.238.153
9 24 ms 24 ms 24 ms virtual-vip.thdo.bbc.co.uk [212.58.224.138]

Trace complete.

It connects me to the Rochdale, Leeds and Manchester gateways. I'd prefer the London ones to be added in, although it's not a huge deal. The latency as you can see has gone down quite a bit to an acceptable level since my original post, although it's still elevated in comparison to the original values.

Here's an example for Leeds gateway:
Tracing route to 95.211.120.168 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 10.0.0.2
2 39 ms 39 ms 41 ms losubs.subs.dsl1.kp-leeds.zen.net.uk [62.3.85.17
]
3 39 ms 39 ms 39 ms ae0-113.cr2.kp-leeds.zen.net.uk [62.3.85.181]
4 44 ms 44 ms 44 ms ge-3-0-0-0.cr1.th-lon.zen.net.uk [62.3.80.78]
5 44 ms 43 ms 43 ms ge-2-0-0-0.cr2.th-lon.zen.net.uk [62.3.80.42]
6 52 ms 51 ms 52 ms lon.tc2.leaseweb.net [195.66.225.100]
7 52 ms 52 ms 52 ms te4-3.sr10.evo.leaseweb.net [62.212.80.66]
8 52 ms 52 ms 51 ms 95.211.120.168

Trace complete.

Thanks for the link by the way. It's only around 8ms higher than optimal conditions at the moment anyway, so as said, it's not a big deal.

Edited by deleted (Sun 24-Apr-11 17:49:53)

You might be interested in this set of results then;

From another end point on the london network. - This line has interleaving switched on - without reading all the posts here I'd guess your line is also in interleaved mode going on the responce times.


[root@muffin ~]# traceroute -I bbc.co.uk
traceroute to bbc.co.uk (212.58.224.138), 30 hops max, 40 byte packets
1 gatekeeper.goth.int (172.16.10.1) 0.319 ms 0.312 ms 0.318 ms
2 losubs.subs.dsl2.th-lon.zen.net.uk (62.3.84.21) 19.052 ms 19.763 ms 20.746 ms
3 ae0-114.cr1.th-lon.zen.net.net (62.3.84.185) 21.950 ms 25.399 ms 26.368 ms
4 82.71.254.134 (82.71.254.134) 27.340 ms 28.071 ms 28.807 ms
5 212.58.238.153 (212.58.238.153) 30.265 ms 31.003 ms 31.733 ms
6 virtual-vip.thdo.bbc.co.uk (212.58.224.138) 32.705 ms 34.834 ms 35.295 ms



[root@muffin ~]# ping bbc.co.uk
PING bbc.co.uk (212.58.224.138) 56(84) bytes of data.
64 bytes from virtual-vip.thdo.bbc.co.uk (212.58.224.138): icmp_seq=1 ttl=122 time=18.9 ms
64 bytes from virtual-vip.thdo.bbc.co.uk (212.58.224.138): icmp_seq=2 ttl=122 time=18.5 ms
64 bytes from virtual-vip.thdo.bbc.co.uk (212.58.224.138): icmp_seq=3 ttl=122 time=19.0 ms
64 bytes from virtual-vip.thdo.bbc.co.uk (212.58.224.138): icmp_seq=4 ttl=122 time=19.5 ms
64 bytes from virtual-vip.thdo.bbc.co.uk (212.58.224.138): icmp_seq=5 ttl=122 time=18.9 ms
64 bytes from virtual-vip.thdo.bbc.co.uk (212.58.224.138): icmp_seq=6 ttl=122 time=18.6 ms
64 bytes from virtual-vip.thdo.bbc.co.uk (212.58.224.138): icmp_seq=7 ttl=122 time=19.0 ms
64 bytes from virtual-vip.thdo.bbc.co.uk (212.58.224.138): icmp_seq=8 ttl=122 time=19.0 ms
64 bytes from virtual-vip.thdo.bbc.co.uk (212.58.224.138): icmp_seq=9 ttl=122 time=18.9 ms
64 bytes from virtual-vip.thdo.bbc.co.uk (212.58.224.138): icmp_seq=10 ttl=122 time=19.4 ms

--- bbc.co.uk ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 9001ms
rtt min/avg/max/mdev = 18.576/19.037/19.557/0.340 ms

Nah, it's on fast path to the best of my knowledge. I'm able to force the sync up to 8128 with a low enough noise margin and as I understand it, an interleaved line can't go that high.

Edited by deleted (Sun 24-Apr-11 19:09:58)

It can...

I've had interleaved lines running by default at 8128 down so don't be tricked by that one.

Can you post your line stats and trace please.