Some spiking is possible if for example you download or upload a lot e.g. a speediest so best guide is leaving it idle over night (even switching wireless off) and seeing how stable it is then

The jitter looks very low compared to say VIrgin Media your few spikes look most like usage at present.

20ms first hop looks reasonable for Lincoln. FTTC can be fairly low ping across the VDSL2 segment and for the majority of people it is the regional routing that is the issue these days i.e. FTTP is not the magic answer to low latency unless you had problems due to interleaving etc on VDSL2

Edited by MrSaffron (Mon 13-May-19 20:13:16)

In reply to a post by dan_miles86:

They are saying its normal and are not interested at all.

Their service really has been shocking. I would love to leave if I could find a way.

That's not sound likely from Zen Internet as they always the best service provider, I be shocked if they don't wanna to know your FTTP problem with slow speed. Hope Zen Internet will ask BT Wholesale to put u on different SVLAN.

Edited by adslmax (Mon 13-May-19 23:56:54)

In reply to a post by brookheather:

Are you testing with a wired connection - where in the country are you as latency increases the further you are from London typically. I live in London and get 2-3ms ping to bbc.co.uk and get the full 330/30 from my Cerberus FTTPoD connection.

Agreed, I am about 5 miles (by road) from Telehouse in the docklands (where it goes as far as I am aware) and I get between 1.7 and 2.8ms (on average 2.6ms) ping to the BBC Site.

[ON PC]
ping -4 bbc.co.uk

Pinging bbc.co.uk [151.101.128.81] with 32 bytes of data:
Reply from 151.101.128.81: bytes=32 time=2ms TTL=57
Reply from 151.101.128.81: bytes=32 time=1ms TTL=57
Reply from 151.101.128.81: bytes=32 time=1ms TTL=57
Reply from 151.101.128.81: bytes=32 time=2ms TTL=57

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

I think those 1ms on my results are more close to 2ms due to it rounds down, but the last time I checked on my Linux box it shows the 2 decimal points and its close to 2ms.

So if the OP is in London they "should" be getting the same or close to it.

Paul

In reply to a post by PaulKirby:

So if the OP is in London they "should" be getting the same or close to it.

The OP is in Lincoln not London.

What matters most is the variability in RTT, rather than the absolute value. If it's 20ms consistently, then I'd expect it's just a speed-of-light limit based on the distance travelled (*). However if it varies widely, then that's a sign of congestion. The lowest RTT observed is the path delay, and the variation is queuing delays. What RTT is observed at 3am?

(*) Having said that, if the backhaul path is over fibre, 20ms ought to get you to Scotland. RTT increases roughly 1ms per 100km (light travelling at 200km/sec in fibre). For comparison: London to AWS in Ireland is about 10ms.

There's another thing you can do. If you have a Virtual Private Server in the cloud somewhere, you can find your home IP address (whatsmyip.org) and then traceroute back to that address. RTT is the total delay A->B->A, and sometimes the A->B path is very different to the B->A path.

In reply to a post by candlerb:

In reply to a post by PaulKirby:

So if the OP is in London they "should" be getting the same or close to it.

The OP is in Lincoln not London.

What matters most is the variability in RTT, rather than the absolute value. If it's 20ms consistently, then I'd expect it's just a speed-of-light limit based on the distance travelled (*). However if it varies widely, then that's a sign of congestion. The lowest RTT observed is the path delay, and the variation is queuing delays. What RTT is observed at 3am?

(*) Having said that, if the backhaul path is over fibre, 20ms ought to get you to Scotland. RTT increases roughly 1ms per 100km (light travelling at 200km/sec in fibre). For comparison: London to AWS in Ireland is about 10ms.

There's another thing you can do. If you have a Virtual Private Server in the cloud somewhere, you can find your home IP address (whatsmyip.org) and then traceroute back to that address. RTT is the total delay A->B->A, and sometimes the A->B path is very different to the B->A path.

I'm in Inverness yet getting ~20ms on FTTP, so the OP being in Lincoln (ie much closer to London) should be getting around half of that, unless the OP's fibre circuit takes a scenic route around the British Isles.

OP, if Zen aren't being helpful over the phone, I would message their TBB rep, ajays (Andrew) on these forums who should be able to investigate further.

C:\>ping bbc.co.uk

Pinging bbc.co.uk [151.101.0.81] with 32 bytes of data:
Reply from 151.101.0.81: bytes=32 time=20ms TTL=58
Reply from 151.101.0.81: bytes=32 time=21ms TTL=58
Reply from 151.101.0.81: bytes=32 time=20ms TTL=58
Reply from 151.101.0.81: bytes=32 time=20ms TTL=58

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

In reply to a post by candlerb:

In reply to a post by PaulKirby:

So if the OP is in London they "should" be getting the same or close to it.

The OP is in Lincoln not London.

Yeah you are right, I was half asleep when I replied, all I saw in my head was London, my bad.

Paul

I am wondering if they are having routing issues and being routed to a further Internet Exchange.

Maybe one of the Manchester Internet Exchanges or the one in Leeds might of been better for them instead of a London one.

Paul

I wonder if the OP has tried a different router .... ?

In reply to a post by PaulKirby:

I am wondering if they are having routing issues and being routed to a further Internet Exchange.

Maybe one of the Manchester Internet Exchanges or the one in Leeds might of been better for them instead of a London one.

Paul

Nah. Across the BT Wholesale network, I presume, to Telehouse North then straight across LINX London according to their trace

1 <1 ms <1 ms <1 ms 192.168.50.1
2 20 ms 20 ms 85 ms vt1.cor1.lond2.ptn.zen.net.uk [51.148.72.23] << Telehouse North
3 31 ms 37 ms 30 ms ae-17.agg3.lond2.ptn.zen.net.uk [51.148.73.32]
4 20 ms * 20 ms 195.66.225.91 << LINX LON1 / Juniper LAN
5 20 ms 20 ms 20 ms 151.101.64.81

Might be taking a rather circuitous route across the BT Wholesale network, mind.

In reply to a post by Zarjaz:

I wonder if the OP has tried a different router .... ?

Yeah, that too, not too sure if Zen are hiding some hops, but 20ms from the router to the next hop seems a bit too high.

Or even done a complete power recycle of the ONT and Router to see if that helped.

Paul