Re: Think Broadband Ping Monitor Results (POST YOURS)
 

Just did a speedtest with their own London server and full speed :mad:

https://www.cableforum.co.uk/images/...2013/10/23.png

Everywhere else reporting slow speed.....

Re: Think Broadband Ping Monitor Results (POST YOURS)
 

Do a traceroute to pingbox1.thinkbroadband.com and see if anything looks unusual.

Re: Think Broadband Ping Monitor Results (POST YOURS)
 

traceroute to pingbox1.thinkbroadband.com (80.249.99.164), 64 hops max, 52 byte packets
1 10.0.1.1 (10.0.1.1) 0.543 ms 0.420 ms 0.270 ms
2 10.27.180.1 (10.27.180.1) 10.611 ms 9.151 ms 8.192 ms
3 cmbg-core-1a-ae2-598.network.virginmedia.net (80.1.203.53) 10.603 ms 8.863 ms 10.820 ms
4 popl-bb-1b-ae16-0.network.virginmedia.net (212.43.163.141) 14.766 ms 12.939 ms 13.993 ms
5 nrth-bb-1b-et-700-0.network.virginmedia.net (62.253.175.53) 48.180 ms 37.107 ms
nrth-bb-1b-et-010-0.network.virginmedia.net (62.253.175.57) 47.589 ms
6 tele-ic-4-ae0-0.network.virginmedia.net (62.253.174.18) 42.607 ms 42.542 ms 40.710 ms
7 linx-gw1.thn.ncuk.net (195.66.224.240) 43.563 ms 43.299 ms 41.980 ms
8 gi1-24-10-star1.core-rs2.thdo.ncuk.net (80.249.97.9) 45.663 ms 44.711 ms 43.568 ms
9 pingbox1.thinkbroadband.com (80.249.99.164) 41.702 ms 42.267 ms 42.478 ms

Re: Think Broadband Ping Monitor Results (POST YOURS)
 

Looks like a large spike between hop 4 and 5 there. Within VM's network.

Re: Think Broadband Ping Monitor Results (POST YOURS)
 

Very strange how Snoop and myself are both affected at the exact same time as per our TBB graphs. Obviously a East Anglia issue!

Re: Think Broadband Ping Monitor Results (POST YOURS)
 

I could be wrong, but both traces are going through nrth-bb-1b-et-xxx.network.virginmedia.net so I'd say that's where the issue is. Someone better qualified than I can comment though.

Re: Think Broadband Ping Monitor Results (POST YOURS)
 

Yeah, pretty obvious core network congestion.

Re: Think Broadband Ping Monitor Results (POST YOURS)
 

Well here is my 120/12 in modem mode on the Super Hub 1

http://www.thinkbroadband.com/ping/s...14-10-2013.png

Here is my speetest, also watching Twitch.tv and playing world of tanks at the same time

https://www.cableforum.co.uk/images/...2013/10/19.png

Re: Think Broadband Ping Monitor Results (POST YOURS)
 

Made a post on the official forums, see what they have to say. Funnily enough around midnight things returned to normal as if a switch had been flicked. Be interesting to see how tonight turns out :erm:

Re: Think Broadband Ping Monitor Results (POST YOURS)
 

It's entirely possible it's not congestion but either a routing or a configuration issue. The fact that it disappeared exactly at midnight leans towards this. If it was congestion, I'd expect to see a decline over a couple of hours as people go to bed.

Re: Think Broadband Ping Monitor Results (POST YOURS)
 

I tend to agree Kushan, the fact Snoop and I were both affected at the exact time with similar Pings supports that too.

Ignore the on the hour spikes thats just SamKnows running.

Re: Think Broadband Ping Monitor Results (POST YOURS)
 

I had the same issues, and a smaller peak the night before.

CM21 area (near Harlow, Essex)

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

Re: Think Broadband Ping Monitor Results (POST YOURS)
 

That's exactly how congestion works. Congestion is caused by load. Midnight, people go to bed. Load goes down, congestion goes down. Things return to normal.

Re: Think Broadband Ping Monitor Results (POST YOURS)
 

I too had the smaller spike the previous night too, obviously a problem within our area.

Re: Think Broadband Ping Monitor Results (POST YOURS)
 

Disagree. This has been seen many times before, this is exactly how core congestion manifests. It does not decline gradually over a couple of hours. Big pipes do not see gradual changes in latency. All the way up to around 95% load latency is perfectly normal, and between 95% and 100% you get a big, sudden jump.

Also it's obvious from the graph it did not disappear exactly at midnight. It was declining throughout the period from about 10:15pm to 11:45pm. Funny how people go to bed at around that time...

Finally, routing and configuration issues are the most common causes of congestion