That's because its not a ping and we never call it a ping

sorry I could of worded that a bit better..

In reply to a post by mlmclaren:

Could you try pinging the BBC via command! I don't find the TBB tests ping to be very accurate

Yes no problem, hope it helps. ping is slightly lower on the TBB tester 55 ms tonight


ADSL Line:

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

2 losubs.subs.dsl2.wh-man.zen.net.uk [62.3.87.147]
3 ae1-114.cr1.wh-man.zen.net.uk [62.3.87.169]
4 ge-3-0-0-0.cr2.th-lon.zen.net.uk [62.3.80.45]
5 ge-2-0-0-0.cr1.th-lon.zen.net.uk [62.3.80.41]
6 82.71.254.134
7 * * *
Computing statistics for 150 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% 10.0.0.1
0/ 100 = 0% |
2 20ms 0/ 100 = 0% 0/ 100 = 0% losubs.subs.dsl2.wh-man.zen.net.uk [62.3.87.147]
0/ 100 = 0% |
3 25ms 0/ 100 = 0% 0/ 100 = 0% ae1-114.cr1.wh-man.zen.net.uk [62.3.87.169]
0/ 100 = 0% |
4 30ms 0/ 100 = 0% 0/ 100 = 0% ge-3-0-0-0.cr2.th-lon.zen.net.uk [62.3.80.45]
0/ 100 = 0% |
5 30ms 0/ 100 = 0% 0/ 100 = 0% ge-2-0-0-0.cr1.th-lon.zen.net.uk [62.3.80.41]
0/ 100 = 0% |
6 27ms 0/ 100 = 0% 0/ 100 = 0% 82.71.254.134

Trace complete.

Fibre Line:

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

2 losubs.subs.dsl4.wh-man.zen.net.uk [62.3.83.6]
3 ae1-118.cr1.wh-man.zen.net.uk [62.3.86.1]
4 ge-3-0-0-0.cr2.th-lon.zen.net.uk [62.3.80.45]
5 ge-2-0-0-0.cr1.th-lon.zen.net.uk [62.3.80.41]
6 82.71.254.134
7 * * *
Computing statistics for 150 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% 192.168.1.1
0/ 100 = 0% |
2 18ms 0/ 100 = 0% 0/ 100 = 0% losubs.subs.dsl4.wh-man.zen.net.uk [62.3.83.6]
0/ 100 = 0% |
3 21ms 0/ 100 = 0% 0/ 100 = 0% ae1-118.cr1.wh-man.zen.net.uk [62.3.86.1]
0/ 100 = 0% |
4 26ms 0/ 100 = 0% 0/ 100 = 0% ge-3-0-0-0.cr2.th-lon.zen.net.uk [62.3.80.45]
0/ 100 = 0% |
5 27ms 0/ 100 = 0% 0/ 100 = 0% ge-2-0-0-0.cr1.th-lon.zen.net.uk [62.3.80.41]
0/ 100 = 0% |
6 25ms 0/ 100 = 0% 0/ 100 = 0% 82.71.254.134

Trace complete.

those traces don't seem to be making it too the BBC but I can see that your connections are routed via Manchester...

Am I correct to asume your Fibre line is a fair distance from the DSLAM (Cab)

The cab is about 900+ ish M away, ironically there is another cab about 400 M away that I'm not connected to.

Is this better as I pathpinged the last lot

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

1 14 ms 2 ms <1 ms
2 20 ms 20 ms 21 ms losubs.subs.dsl2.wh-man.zen.net.uk [62.3.87.147]
3 21 ms 29 ms 21 ms ae1-114.cr1.wh-man.zen.net.uk [62.3.87.169]
4 28 ms 28 ms 28 ms ge-3-0-0-0.cr2.th-lon.zen.net.uk [62.3.80.45]
5 27 ms 32 ms 30 ms ge-2-0-0-0.cr1.th-lon.zen.net.uk [62.3.80.41]
6 28 ms 27 ms 26 ms 82.71.254.134
7 * * * Request timed out.
8 30 ms 31 ms 32 ms ae0.er01.cwwtf.bbc.co.uk [132.185.254.93]
9 31 ms 34 ms 29 ms 132.185.255.165
10 29 ms 31 ms 31 ms fmt-vip132.cwwtf.bbc.co.uk [212.58.246.103]

Thanks I do find the results easier to read like that though I did manage to navigate through the others,

At 900m I kind of understand there being some interleaving then really, do you know if your fibre cabinet is Huawei or ECI? or if G.INP or even what depth of interleaving has been applied to your connection?

I'm currently on a line that I estimate with a generous load of loops to be about 450m and see a few errors with my line at the moment which I think might be affecting packet perfect apps like gaming, so I'm waiting for DLM to put some error correction in place in due course.

I too am now with Zen, though its via there own backhaul and being 20-25 miles south of London see pretty nice pings to BBC and most servers.

Tracing route to fmt-vip132.cwwtf.bbc.co.uk [212.58.246.103]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms router.asus.com [192.168.1.1]
2 7 ms 7 ms 7 ms losubs.subs.dsl3.th-lon.zen.net.uk [62.3.84.25]

3 7 ms 7 ms 7 ms ae1-117.cr2.th-lon.zen.net.uk [62.3.84.197]
4 7 ms 7 ms 7 ms ge-2-0-0-0.cr1.th-lon.zen.net.uk [62.3.80.41]
5 7 ms 7 ms 7 ms 82.71.254.134
6 * * * Request timed out.
7 8 ms 8 ms 8 ms ae0.er01.cwwtf.bbc.co.uk [132.185.254.93]
8 * 9 ms 9 ms 132.185.255.165
9 8 ms 8 ms 8 ms fmt-vip132.cwwtf.bbc.co.uk [212.58.246.103]

Trace complete.

Im on a ECI cab/ECI modem and inter is switched on at what setting I have no idea

Oh right, I feared that...

Looks like your connection has significant amount of Interleaving then.

Shame OR got stingy and started installing ECI's somewhat incapable of upgrades equipment!

If it where Huawei, you would have G.INP now and not have to worry about the baseline latency so much

The strange this is just around the corner there are Huawei cabs fitted! The upgrade to fibre cabs has had no continuity with a particular manufacturer as one week they have ECI cabs then Huawei cabs fitted in the same area. Also I don't understand the vast distance to the new cab considering there is one literally at the bottom of the road I'm not connected too.

I've noticed that cabinets fitted using the BDUK scheme are all Huawei's, even in areas where BT's initial rollout was ECI.

have you had a look here: https://www.telecom-tariffs.co.uk/codelook.htm