20CN ..... is this PN or BBC Sunday night meltdown?

C:\Users\AM>ping bbc.co.uk

Pinging bbc.co.uk [212.58.244.20] with 32 bytes of data:
Reply from 212.58.244.20: bytes=32 time=383ms TTL=53
Reply from 212.58.244.20: bytes=32 time=389ms TTL=53
Reply from 212.58.244.20: bytes=32 time=395ms TTL=53
Reply from 212.58.244.20: bytes=32 time=450ms TTL=53

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

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

1 * * * Request timed out.
2 129 ms 155 ms 116 ms lo0-central10.pcl-ag01.plus.net [195.166.128.182]
3 196 ms 169 ms 163 ms link-b-central10.pcl-gw02.plus.net [212.159.2.162]
4 83 ms 71 ms 47 ms xe-10-0-0.pcl-cr02.plus.net [212.159.0.194]
5 55 ms 51 ms 51 ms ae2.pcl-cr01.plus.net [195.166.129.6]
6 61 ms 58 ms 63 ms ae1.ptw-cr01.plus.net [195.166.129.0]
7 60 ms 66 ms 61 ms kingston-gw.thdo.bbc.co.uk [212.58.239.6]
8 * * * Request timed out.
9 * * * Request timed out.
10 202 ms 202 ms 202 ms ae0.er01.telhc.bbc.co.uk [132.185.254.109]
11 139 ms 118 ms 117 ms 132.185.255.149
12 182 ms 181 ms 189 ms fmt-vip71.telhc.bbc.co.uk [212.58.244.20]

Trace complete.

Live link BQM:-
http://www.thinkbroadband.com/ping/share/78479ac4a0a...

Red block due to router powered off as the weather went bad with thunder,lightening,hail and sleet showers,however don't usually get such an angry looking graph maybe gateway change didn't help? ....... will hop at 9.30pm

Not sure if the small local 20CN exchange is congested, less than 400 subscribers.

Edited by Apprentice (Sun 12-Apr-15 22:38:17)

Something is very wrong . I thought I was getting funny lags, but this laptop is acting weird anyway.

Looking at my BQM I had a disconnection just after 4pm and am now on ptw-ag01. Base latency looks to be up a couple, but :-

Pinging bbc.co.uk [212.58.244.20] with 32 bytes of data:
Reply from 212.58.244.20: bytes=32 time=106ms TTL=55
Reply from 212.58.244.20: bytes=32 time=99ms TTL=55
Reply from 212.58.244.20: bytes=32 time=90ms TTL=55
Reply from 212.58.244.20: bytes=32 time=97ms TTL=55

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

Should be 12-14ms.

Edited by RobertoS (Sun 12-Apr-15 21:57:08)

Changed gateway at around 10.30pm ish

C:\Users\AM>ping bbc.co.uk

Pinging bbc.co.uk [212.58.244.20] with 32 bytes of data:
Reply from 212.58.244.20: bytes=32 time=48ms TTL=53
Reply from 212.58.244.20: bytes=32 time=67ms TTL=53
Reply from 212.58.244.20: bytes=32 time=122ms TTL=53
Reply from 212.58.244.20: bytes=32 time=108ms TTL=53

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

C:\Users\AM>tracert bbc.co.uk

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

1 <1 ms <1 ms <1 ms 192.168.0.1
2 * 48 ms 55 ms lo0-central10.pcl-ag02.plus.net [195.166.128.183]
3 48 ms 48 ms 48 ms link-a-central10.pcl-gw01.plus.net [212.159.2.164]
4 47 ms 47 ms 47 ms xe-10-1-0.pcl-cr01.plus.net [212.159.0.196]
5 48 ms 50 ms 48 ms ae1.ptw-cr01.plus.net [195.166.129.0]
6 66 ms 46 ms 48 ms kingston-gw.thdo.bbc.co.uk [212.58.239.6]
7 * * * Request timed out.
8 * * * Request timed out.
9 53 ms 48 ms 48 ms ae0.er01.telhc.bbc.co.uk [132.185.254.109]
10 151 ms 129 ms 98 ms 132.185.255.149
11 72 ms 72 ms 84 ms fmt-vip71.telhc.bbc.co.uk [212.58.244.20]

Trace complete.

In reply to a post by Apprentice:

Changed gateway at around 10.30pm ish

C:\Users\AM>ping bbc.co.uk

Pinging bbc.co.uk [212.58.244.20] with 32 bytes of data:
Reply from 212.58.244.20: bytes=32 time=48ms TTL=53
Reply from 212.58.244.20: bytes=32 time=67ms TTL=53
Reply from 212.58.244.20: bytes=32 time=122ms TTL=53
Reply from 212.58.244.20: bytes=32 time=108ms TTL=53

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

C:\Users\AM>tracert bbc.co.uk

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

1 <1 ms <1 ms <1 ms 192.168.0.1
2 * 48 ms 55 ms lo0-central10.pcl-ag02.plus.net [195.166.128.183]
3 48 ms 48 ms 48 ms link-a-central10.pcl-gw01.plus.net [212.159.2.164]
4 47 ms 47 ms 47 ms xe-10-1-0.pcl-cr01.plus.net [212.159.0.196]
5 48 ms 50 ms 48 ms ae1.ptw-cr01.plus.net [195.166.129.0]
6 66 ms 46 ms 48 ms kingston-gw.thdo.bbc.co.uk [212.58.239.6]
7 * * * Request timed out.
8 * * * Request timed out.
9 53 ms 48 ms 48 ms ae0.er01.telhc.bbc.co.uk [132.185.254.109]
10 151 ms 129 ms 98 ms 132.185.255.149
11 72 ms 72 ms 84 ms fmt-vip71.telhc.bbc.co.uk [212.58.244.20]

Trace complete.

And as my TAP3 test confirmed that it is a plusnet issue or was for me,

Fibre connection in Hants, showing issues (live graph):
http://www.thinkbroadband.com/ping/share/65b189a4f28...

Who in this thread is on ptw-ag01 like me?

Take a look at this page where Russell's is almost identical to mine. The next one, KevinAndrews, is very similar, and there is Stanman24 which bears some resemblance.

The rest look fine.

Edited by RobertoS (Sun 12-Apr-15 23:02:10)

Not me

Changed gateway again, could be that now Poldark is over things get a bit better ....... we will see what BQM looks like in a short while.

Edit:-

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

1 * * * Request timed out.
2 61 ms 63 ms 64 ms lo0-central10.ptn-ag02.plus.net [195.166.128.191]
3 62 ms 74 ms 81 ms link-b-central10.ptn-gw02.plus.net [212.159.2.134]
4 120 ms 113 ms 101 ms xe-1-2-0.ptw-cr02.plus.net [212.159.0.114]
5 150 ms 169 ms 161 ms ae2.ptw-cr01.plus.net [195.166.129.4]
6 132 ms 147 ms 136 ms kingston-gw.thdo.bbc.co.uk [212.58.239.6]
7 * * * Request timed out.
8 * * * Request timed out.
9 49 ms 52 ms 52 ms ae0.er01.telhc.bbc.co.uk [132.185.254.109]
10 50 ms 62 ms 69 ms 132.185.255.149
11 48 ms 49 ms 48 ms fmt-vip71.telhc.bbc.co.uk [212.58.244.20]

Trace complete.

C:\Users\AM>ping bbc.co.uk

Pinging bbc.co.uk [212.58.244.20] with 32 bytes of data:
Reply from 212.58.244.20: bytes=32 time=47ms TTL=55
Reply from 212.58.244.20: bytes=32 time=48ms TTL=55
Reply from 212.58.244.20: bytes=32 time=47ms TTL=55
Reply from 212.58.244.20: bytes=32 time=46ms TTL=55

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

Edited by Apprentice (Sun 12-Apr-15 23:52:12)

That's nothing in comparison to this one 100ms ping

Poldark doesn't fit in with the times on my BQM. Neither does anything else I can see on a quick flip through Radio Times.

Edit - now
Pinging bbc.co.uk [212.58.244.20] with 32 bytes of data:
Reply from 212.58.244.20: bytes=32 time=13ms TTL=55
Reply from 212.58.244.20: bytes=32 time=13ms TTL=55
Reply from 212.58.244.20: bytes=32 time=13ms TTL=55
Reply from 212.58.244.20: bytes=32 time=13ms TTL=55

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

Tracing route to thinkbroadband.com [80.249.99.130]
over a maximum of 30 hops:

1 47 ms 8 ms 10 ms router.asus.com [192.168.1.254]
2 13 ms 13 ms 35 ms lo0-central10.ptw-ag01.plus.net [195.166.128.195]
3 13 ms 12 ms 13 ms link-a-central10.ptw-gw01.plus.net [212.159.2.144]
4 12 ms 13 ms 12 ms xe-4-2-0.ptw-cr01.plus.net [212.159.0.240]
5 13 ms 13 ms 13 ms linx-gw1.thn.ncuk.net [195.66.224.240]
6 13 ms 13 ms 12 ms te2-1-9.star10g.bdr-rt3.thdo.ncuk.net [80.249.97.17]
7 20 ms 15 ms 18 ms te1-1-1-31.core-rs2.thdo.ncuk.net [80.249.97.85]
8 14 ms 13 ms 13 ms www.thinkbroadband.com [80.249.99.130]

Trace complete.

Edited by RobertoS (Mon 13-Apr-15 00:03:48)

Yes indeed Poldark finished around 10.00pm if I'm not mistaken