Tracing route to bbc.co.uk [151.101.0.81]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms testwifi.here [192.168.86.1]
2 14 ms 14 ms 14 ms lo1.subs.bng1.wh-man.zen.net.uk [62.3.89.162]
3 14 ms 14 ms 14 ms ae5-161.cr2.wh-man.zen.net.uk [62.3.86.13]
4 15 ms 15 ms * vl-50.ph-0-4-3.cor1.manc1.ptn.zen.net.uk [51.148.73.58]
5 21 ms 20 ms 20 ms ae-2.pe1.ixn-lon.zen.net.uk [51.148.73.34]
6 * 21 ms 20 ms ae-1.br1.ixn-lon.zen.net.uk [51.148.73.121]
7 20 ms * 20 ms 195.66.225.91
8 20 ms 20 ms 20 ms 151.101.0.81
Lots of dropped packets. Pinging hop 4 shows how bad this is:
Pinging 51.148.73.58 with 32 bytes of data:
Reply from 51.148.73.58: bytes=32 time=14ms TTL=252
Reply from 51.148.73.58: bytes=32 time=14ms TTL=252
Reply from 51.148.73.58: bytes=32 time=14ms TTL=252
Reply from 51.148.73.58: bytes=32 time=14ms TTL=252
Request timed out.
Reply from 51.148.73.58: bytes=32 time=14ms TTL=252
Reply from 51.148.73.58: bytes=32 time=14ms TTL=252
Reply from 51.148.73.58: bytes=32 time=14ms TTL=252
Request timed out.
Request timed out.
Ping statistics for 51.148.73.58:
Packets: Sent = 10, Received = 7, Lost = 3 (30% loss),
Approximate round trip times in milli-seconds:
Minimum = 14ms, Maximum = 14ms, Average = 14ms.
This graph shows just how bad the throughput goes during peak times..... the scale isn't linear as it represents tests, but this is how bad it is...
https://testmy.net/compID/75852670545
Very happy to club together and force Zen to admit problems and sort them out. I'm currently out of contract paying the equivalent of fttp 150 and was going to upgrade to their fttp, but not if they can't solve these problems.
Edited by deleted (Sat 27-Jun-20 21:49:57)



Pages in this thread:
Print Thread
