Re: Think Broadband Ping Monitor Results (POST YOURS)
 

In that case do a hard reboot and let us know what happens.

Re: Think Broadband Ping Monitor Results (POST YOURS)
 

Apart from a touch of peak time congestion that's very good.

http://www.thinkbroadband.com/ping/s...15-11-2014.png

Re: Think Broadband Ping Monitor Results (POST YOURS)
 

Rebooted, still the same.

Re: Think Broadband Ping Monitor Results (POST YOURS)
 

No change here either.

Re: Think Broadband Ping Monitor Results (POST YOURS)
 

I did a reboot and still getting the same thing.

Re: Think Broadband Ping Monitor Results (POST YOURS)
 

So guys, what is it about switching into router mode and back again that did the trick for me?

https://www.cableforum.co.uk/images/...2014/11/34.png

Re: Think Broadband Ping Monitor Results (POST YOURS)
 

Yep same here:

http://www.thinkbroadband.com/ping/s...15-11-2014.png

1 <1 ms <1 ms <1 ms router.asus.com [192.168.1.1]
2 27 ms 8 ms 6 ms cpc13-telf11-2-0-gw.wolv.cable.virginm.net [77.98.26.1]
3 6 ms 8 ms 6 ms wolv-core-2a-ae8-615.network.virginmedia.net [80.3.159.101]
4 10 ms 10 ms 16 ms manc-bb-1c-ae12-0.network.virginmedia.net [213.105.159.141]
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 12 ms 14 ms 21 ms nrth-bb-1b-ae0-0.network.virginmedia.net [62.254.42.130]
9 100 ms 117 ms 95 ms tele-ic-4-ae0-0.network.virginmedia.net [62.253.174.18]
10 25 ms 17 ms 18 ms linx-gw1.thn.ncuk.net [195.66.224.240]
11 98 ms 96 ms 100 ms te2-1-9.star10g.bdr-rt3.thdo.ncuk.net [80.249.97.17]
12 104 ms 102 ms 100 ms te1-1-1-31.core-rs2.thdo.ncuk.net [80.249.97.85]
13 105 ms 103 ms 103 ms www.thinkbroadband.com [80.249.99.130]

Re: Think Broadband Ping Monitor Results (POST YOURS)
 

Best guess you changed IP address and ended up in a non-hosed IP range. The issue will be due to dodgy routing.

Looking at Jon's post there's at very least a problem with the return path from Think Broadband, and it looks like the routing is asymmetrical which isn't necessarily a problem in its own right but can be.

Either way your rebooting anything on your side unless it changed your IP would have zero impact as the fault is way deeper into the network.

It is alarming how frequently Virgin seem to be having these issues. Either they have some staff who aren't entirely competent with what they are doing or some routers with some dodgy software running on them that keeps breaking whenever they are looked at the wrong way.

EDIT: Looking at that traceroute best guess is that there are far too many VM customers using one of the links on the network as a return path. Could also be that a single router on the network is in strife and packets usually multipath through it and other locations on their way back from the Internet either can't use it so are concentrated elsewhere causing congestion or all packets going through that one router are slow while other paths are okay.

EDIT2: Network bods:

6 11 ms 57 ms 11 ms 195.66.236.23
7 11 ms 11 ms 12 ms popl-bb-1c-ae9-0.network.virginmedia.net [213.105.159.118]
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 15 ms 33 ms 15 ms brhm-bb-1b-ae0-0.network.virginmedia.net [62.254.42.106]
12 20 ms 16 ms 16 ms wolv-core-2b-ae0-0.network.virginmedia.net [213.105.159.146]
13 19 ms 19 ms 53 ms cpc13-telf11-2-0-gw.wolv.cable.virginm.net [77.98.26.1]

Doesn't that look like an MPLS path where they forgot to not increment TTL?

That's new - wonder if they were making changes on the core which went pearshaped?

Meh, all conjecture, could be a whole bunch of things. Looking at the blips in some people's TBB graphs looks like some planned work went wrong overnight. No idea why they'd be doing planned work on a Friday night / Saturday morning. Madness.

Re: Think Broadband Ping Monitor Results (POST YOURS)
 

:(

[img]Download Failed (1)[/img]

Re: Think Broadband Ping Monitor Results (POST YOURS)
 

Lincoln LN6

https://www.cableforum.co.uk/images/...2014/11/36.png


Trace route to bbc.co.uk

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\Owner>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 routerlogin.net [192.168.0.1]
2 16 ms 13 ms 8 ms 10.159.144.1
3 13 ms 11 ms 12 ms nott-core-2b-xe-1132-0.network.virginmedia.net [62.255.231.69]
4 * * * Request timed out.
5 15 ms 15 ms 17 ms nrth-bb-1b-ae0-0.network.virginmedia.net [62.254.42.130]
6 103 ms 103 ms 104 ms tele-ic-4-ae0-0.network.virginmedia.net [62.253.174.18]
7 108 ms 109 ms 110 ms pos6-1.rt0.thdo.bbc.co.uk [212.58.239.237]
8 * * * Request timed out.
9 * * * Request timed out.
10 107 ms 20 ms 17 ms ae0.er01.telhc.bbc.co.uk [132.185.254.109]
11 17 ms 17 ms 18 ms 132.185.255.149
12 17 ms 17 ms 17 ms fmt-vip71.telhc.bbc.co.uk [212.58.244.20]

Trace complete.

C:\Users\Owner>


Speedtest to London Namesco

https://www.cableforum.co.uk/images/...2014/11/37.png

Re: Think Broadband Ping Monitor Results (POST YOURS)
 

My IP is the same.

Although my up/down speed stats are back to normal, my TBB graph is still showing very high latency. My ping is usually 9ms . To speedtestnet it is 12ms today. BBC is 101ms! TBB 102ms . A trace showed longest delays at the ncuk.net stage.

Re: Think Broadband Ping Monitor Results (POST YOURS)
 

There is no issue or fault on your local line.

Re: Think Broadband Ping Monitor Results (POST YOURS)
 

Ah okay - broken to some destinations not others. Unless you are using a different speed tester post-reboot no idea why that would've improved things, issue is a way away from your kit.

Incidentally although you probably knew NCUK is fine.

Tracing route to nrth-bb-1b-ae7-0.network.virginmedia.net [62.253.174.17]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 * * * Request timed out.
3 11 ms 11 ms 11 ms lo0.11.central11.pcl-bng01.plus.net [195.166.130.139]
4 11 ms 11 ms 11 ms irb.11.PCL-CR01.plus.net [84.93.249.97]
5 11 ms 26 ms 11 ms ae1.ptw-cr01.plus.net [195.166.129.0]
6 12 ms 23 ms 12 ms 195.66.225.103
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 16 ms 23 ms 17 ms nrth-bb-1b-ae7-0.network.virginmedia.net [62.253.174.17]

Pinging tbbmeter.thinkbroadband.com [80.249.99.132] with 32 bytes of data:
Reply from 80.249.99.132: bytes=32 time=13ms TTL=122
Reply from 80.249.99.132: bytes=32 time=11ms TTL=122
Reply from 80.249.99.132: bytes=32 time=12ms TTL=122
Reply from 80.249.99.132: bytes=32 time=13ms TTL=122

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

Re: Think Broadband Ping Monitor Results (POST YOURS)
 

I'm getting those similar results on Speedtest but still have the same problem

Re: Think Broadband Ping Monitor Results (POST YOURS)
 

Ip changed :(

https://www.cableforum.co.uk/images/...2014/11/35.png