Too bad for FritzBox users

I also have my own personal smokeping monitoring my line, mouselike I would use if I didnt need to login every 30 days to keep it going.

27th (unfortunately firebrick monitoring had not activated at this stage)

http://i63.tinypic.com/2quorc3.png

28th, 29th, 30th
http://i67.tinypic.com/20p4ps2.png

AAISP by comparison:
http://i64.tinypic.com/ileuyf.png


Clear contention and also visible packet loss at peak times occuring on the core zen network, it would seem.

http://i68.tinypic.com/16gl93o.jpg

All in all I am a little bit dissapointed to see this. I went with Zen (and paid the premium) so that this sort of thing would not be happening. Should have just gone with BT or TalkTalk.

Would welcome other people's thoughts...

Edited by Pipexer (Sun 31-Jan-16 22:10:34)

So your Avg ping times are around 20ms and its maxing out around 75ms and you are loosing less then 0.1% of ping's. Looks pretty good to me, its not something I study much though.

Ping isn't a true reflection of how normal traffic will flow, and occasional loss of packets is expected (yes expected) this is why we have TCP/IP and apps that use UDP are also designed to cope with lost packets.

Ok now i have stopped ranting ill try to be more helpful.

You try to work out where the delay is coming from... start with a traceroute (at a time you are seeing lots of delay) and then try pining every hop:




-bash-4.1$ traceroute aaisp.co.uk
traceroute to aaisp.co.uk (81.187.30.81), 30 hops max, 40 byte packets
1 gw (82.70.x.x) 0.644 ms 0.528 ms 0.567 ms
2 losubs.subs.dsl4.th-lon.zen.net.uk (62.3.84.19) 25.632 ms 25.784 ms 25.291 ms
3 ae1-119.cr2.th-lon.zen.net.uk (62.3.84.209) 25.800 ms 25.579 ms 25.825 ms
4 xe-0-0-2-0.mario.as34270.net (195.66.225.36) 25.535 ms 26.212 ms 25.918 ms
5 no-dns-yet.inetc.co.uk (85.91.238.219) 25.541 ms 26.193 ms 26.023 ms
6 * a.weightless.thn.aa.net.uk (90.155.53.61) 26.188 ms 26.476 ms
7 a.needless.thn.aa.net.uk (81.2.80.193) 26.804 ms 26.947 ms 26.288 ms
8 a.homeless.tch.aa.net.uk (217.169.11.93) 28.073 ms 28.278 ms 27.954 ms
9 limitless.aa.net.uk (81.187.30.81) 28.799 ms 28.808 ms 28.289 ms

-bash-4.1$ ping -s 62.3.84.19
PING 62.3.84.19: 56 data bytes
64 bytes from losubs.subs.dsl4.th-lon.zen.net.uk (62.3.84.19): icmp_seq=0. time=25.160 ms
64 bytes from losubs.subs.dsl4.th-lon.zen.net.uk (62.3.84.19): icmp_seq=1. time=24.979 ms
64 bytes from losubs.subs.dsl4.th-lon.zen.net.uk (62.3.84.19): icmp_seq=2. time=26.082 ms

-bash-4.1$ ping -s 62.3.84.209
PING 62.3.84.209: 56 data bytes
64 bytes from ae1-119.cr2.th-lon.zen.net.uk (62.3.84.209): icmp_seq=0. time=25.500 ms
64 bytes from ae1-119.cr2.th-lon.zen.net.uk (62.3.84.209): icmp_seq=1. time=25.889 ms
64 bytes from ae1-119.cr2.th-lon.zen.net.uk (62.3.84.209): icmp_seq=2. time=26.107 ms


-bash-4.1$ ping -s 195.66.225.36
PING 195.66.225.36: 56 data bytes
64 bytes from xe-0-0-2-0.mario.as34270.net (195.66.225.36): icmp_seq=0. time=74.655 ms
64 bytes from xe-0-0-2-0.mario.as34270.net (195.66.225.36): icmp_seq=1. time=57.076 ms
64 bytes from xe-0-0-2-0.mario.as34270.net (195.66.225.36): icmp_seq=2. time=25.931 ms


-bash-4.1$ ping -s 85.91.238.219
PING 85.91.238.219: 56 data bytes
64 bytes from no-dns-yet.inetc.co.uk (85.91.238.219): icmp_seq=0. time=25.560 ms
64 bytes from no-dns-yet.inetc.co.uk (85.91.238.219): icmp_seq=1. time=25.334 ms
64 bytes from no-dns-yet.inetc.co.uk (85.91.238.219): icmp_seq=2. time=26.051 ms


-bash-4.1$ ping -s 90.155.53.61
PING 90.155.53.61: 56 data bytes
64 bytes from a.weightless.thn.aa.net.uk (90.155.53.61): icmp_seq=0. time=26.182 ms
64 bytes from a.weightless.thn.aa.net.uk (90.155.53.61): icmp_seq=1. time=25.942 ms
64 bytes from a.weightless.thn.aa.net.uk (90.155.53.61): icmp_seq=2. time=26.410 ms


-bash-4.1$ ping -s 81.2.80.193
PING 81.2.80.193: 56 data bytes
64 bytes from a.needless.thn.aa.net.uk (81.2.80.193): icmp_seq=0. time=26.258 ms
64 bytes from a.needless.thn.aa.net.uk (81.2.80.193): icmp_seq=1. time=26.220 ms
64 bytes from a.needless.thn.aa.net.uk (81.2.80.193): icmp_seq=2. time=26.601 ms

I did that in my OP, perhaps go back and read it.

Is your connection using Zen LLU or is it BT WBMC ?

I'm not currently seeing peak time issues ,well nothing that is evident of ping graphs at least, But i have seen similar on my graphs several months back, It was down to BT and it's over contended Svlans ect, as there's no Zen LLU presence in my connected exchange, I have had this sorted twice so far by zen and that is within 12mths

Those hops in your trace route that are showing a small drop in packets isn't really a sign of an issue, just shows those switches are busy and icmp isn't programmed as a high priority so they start to not respond to every ping, if all successive hops from a particular hop to the target where showing similar packet loss then that could be an indication of a issue,

Edited by tommy45 (Mon 01-Feb-16 09:30:38)

Follow up. I lost PPP during a morning this week and since reconnecting things have been much better - looks like I have landed on a different gateway which is not hitting its limits.

http://oi68.tinypic.com/212s6tg.jpg

^ Much happier with the above!