50M : Think Broadband Ping Monitor Results (POST YOURS)

[GrimUpNorth]

Tracing route to pingbox1.thinkbroadband.com [80.249.99.164]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms my.router [192.168.1.1]
2 19 ms 13 ms 20 ms cpc2-wake8-2-0-gw.barn.cable.virginmedia.com [77.97.161.1]
3 14 ms 24 ms 16 ms brad-core-2b-xe-311-712.network.virginmedia.net[81.97.80.149]
4 10 ms 11 ms 13 ms leed-bb-1b-ae6-0.network.virginmedia.net [81.97.80.121]
5 11 ms 12 ms 15 ms leed-bb-1a-ae0-0.network.virginmedia.net [62.253.187.185]
6 13 ms 17 ms 85 ms brnt-bb-1b-as2-0.network.virginmedia.net [213.105.175.26]
7 15 ms 15 ms 33 ms brnt-tmr-1-ae5-0.network.virginmedia.net [213.105.159.50]
8 15 ms 24 ms 15 ms telc-ic-1-as0-0.network.virginmedia.net [62.253.185.74]
9 18 ms 20 ms 16 ms linx-gw2.thdo.ncuk.net [195.66.236.240]
10 15 ms 14 ms 15 ms gi0-24-10-star1.core-rs2.thdo.ncuk.net [80.249.97.9]
11 65 ms 75 ms 75 ms pingbox1.thinkbroadband.com [80.249.99.164]
Trace complete.

Cheers

Grim

[craigj2k12]

That doesnt explain much, maybe its a problem at the server farm, with ncuk?

[roughbeast]

Evidence that TBB is at least partly responsible for the evening blip. Compare the last steps to TBB with that of BBC.co.uk Until that point the Virgin network has no issues that I can see. Please tell me if I am wrong. Speed test TBB only 45Mb. NAMESCO = 104Mb. Time now is 8.17 pm

I will repeat identical tests tomorrow before 6 am.


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

1 <1 ms <1 ms <1 ms REDDWARF [192.168.1.1]
2 5 ms 7 ms 7 ms 10.14.112.1
3 6 ms 19 ms 7 ms brhm-core-2b-ae3-1179.network.virginmedia.net [2
13.106.229.225]
4 34 ms 8 ms 9 ms brhm-bb-1b-ae8-0.network.virginmedia.net [62.253
.174.77]
5 10 ms 9 ms 9 ms manc-bb-1a-as6-0.network.virginmedia.net [62.253
.185.134]
6 15 ms 15 ms 15 ms brnt-bb-1b-ae1-0.network.virginmedia.net [212.43
.163.86]
7 15 ms 16 ms 14 ms brnt-tmr-1-ae5-0.network.virginmedia.net [213.10
5.159.50]
8 17 ms 15 ms 16 ms telc-ic-1-as0-0.network.virginmedia.net [62.253.
185.74]
9 16 ms 15 ms 16 ms linx-gw2.thdo.ncuk.net [195.66.236.240]
10 18 ms 16 ms 16 ms gi0-24-10-star1.core-rs2.thdo.ncuk.net [80.249.9
7.9]
11 102 ms 103 ms 105 ms pingbox1.thinkbroadband.com [80.249.99.164]

Trace complete.



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

1 <1 ms <1 ms <1 ms REDDWARF [192.168.1.1]
2 8 ms 7 ms 5 ms 10.14.112.1
3 7 ms 7 ms 8 ms brhm-core-2b-ae3-1179.network.virginmedia.net [2
13.106.229.225]
4 9 ms 7 ms 9 ms brhm-bb-1b-ae8-0.network.virginmedia.net [62.253
.174.77]
5 8 ms 18 ms 7 ms brhm-bb-1a-ae0-0.network.virginmedia.net [62.253
.185.153]
6 14 ms 13 ms 13 ms nrth-bb-1b-ae2-0.network.virginmedia.net [62.253
.185.85]
7 27 ms 16 ms 16 ms tele-ic-4-ae0-0.network.virginmedia.net [62.253.
174.18]
8 14 ms 15 ms 16 ms pos6-1.rt0.thdo.bbc.co.uk [212.58.239.237]
9 * * * Request timed out.
10 15 ms 15 ms 14 ms ae1.er01.rbsov.bbc.co.uk [132.185.254.46]
11 19 ms 16 ms 18 ms 132.185.255.60
12 14 ms 21 ms 15 ms 212.58.241.131

Trace complete.

[Qtx]

W:\>time
The current time is: 20:07:59.22
Enter the new time:

W:\>pathping pingbox1.thinkbroadband.com

Tracing route to pingbox1.thinkbroadband.com [80.249.99.164]
over a maximum of 30 hops:
0 VMcust [192.168.0.2]
1 10.89.184.1
2 croy-core-1a-ge339.network.virginmedia.net [81.96.224.213]
3 croy-core-2a-ae2-0.network.virginmedia.net [195.182.178.82]
4 brnt-bb-1a-ae9-0.network.virginmedia.net [81.96.226.1]
5 brnt-bb-1b-ae0-0.network.virginmedia.net [213.105.174.226]
6 brnt-tmr-1-ae5-0.network.virginmedia.net [213.105.159.50]
7 telc-ic-1-as0-0.network.virginmedia.net [62.253.185.74]
8 linx-gw2.thdo.ncuk.net [195.66.236.240]
9 gi0-24-10-star1.core-rs2.thdo.ncuk.net [80.249.97.9]
10 pingbox1.thinkbroadband.com [80.249.99.164]

Computing statistics for 250 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 VMcust [192.168.0.2]
0/ 100 = 0% |
1 --- 100/ 100 =100% 100/ 100 =100% 10.89.184.1
0/ 100 = 0% |
2 23ms 0/ 100 = 0% 0/ 100 = 0% croy-core-1a-ge339.network.virginmedia.net [81.96.224.213]
0/ 100 = 0% |
3 21ms 0/ 100 = 0% 0/ 100 = 0% croy-core-2a-ae2-0.network.virginmedia.net [195.182.178.82]
0/ 100 = 0% |
4 23ms 0/ 100 = 0% 0/ 100 = 0% brnt-bb-1a-ae9-0.network.virginmedia.net [81.96.226.1]
0/ 100 = 0% |
5 25ms 0/ 100 = 0% 0/ 100 = 0% brnt-bb-1b-ae0-0.network.virginmedia.net [213.105.174.226]
0/ 100 = 0% |
6 23ms 0/ 100 = 0% 0/ 100 = 0% brnt-tmr-1-ae5-0.network.virginmedia.net [213.105.159.50]
0/ 100 = 0% |
7 22ms 0/ 100 = 0% 0/ 100 = 0% telc-ic-1-as0-0.network.virginmedia.net [62.253.185.74]
0/ 100 = 0% |
8 91ms 0/ 100 = 0% 0/ 100 = 0% linx-gw2.thdo.ncuk.net [195.66.236.240]
0/ 100 = 0% |
9 86ms 0/ 100 = 0% 0/ 100 = 0% gi0-24-10-star1.core-rs2.thdo.ncuk.net [80.249.97.9]
0/ 100 = 0% |
10 86ms 0/ 100 = 0% 0/ 100 = 0% pingbox1.thinkbroadband.com [80.249.99.164]

Trace complete.

So the problem is one end of that peering link. The standard VM support reply would be that the latency shows as being off their network...

[Sephiroth]

Anybody sussed this yet? Doesn't seem so.

[jamonymo]

Originally Posted by LenMackin

Here's mine. I am already pursing this in another thread but essentially been getting regular service dropouts here in Warwick area for over a week now.

for just over a week my internet keeps losing conection just like yours some times for 5 mins and some times for an hour

[roughbeast]

Whoops error. Accidentally repeated post. Now DELETED

[Qtx]

Can't understand why we have similar routes near the peering but my pings increase at a different point to you. Very strange!

[Sirius]

Seems to be a common trend then

[qasdfdsaq]

Originally Posted by craigj2k12

That doesnt explain much, maybe its a problem at the server farm, with ncuk?

Cockup on the outbound path from the hosting network. Not surprising as that's the direction most traffic flows in for most hosting providers.

[roughbeast]

Originally Posted by Sirius

Seems to be a common trend then

Just been on to Bangalore Ending up speaking a slow Indian accent. Why do I keep doing that?

Anyway, I explained to CS guy about the repeated blip; how it appears and disappears abruptly nation-wide almost as if someone was throwing a switch. He said it was probably because of high usage during that time! I agreed, but also said that didn't explain its abruptness. Surely the blip would commence gradually as folk got home from work and then would tail off as users went to bed. He offered to send a technician! I growled at this point and repeated what I had said in an even slower manner, and added that I have friends all over the country observing the same thing.

He has escalated the problem and has promised that I will get a phone call from higher up; from the Himalayas I guess. He thanked me for my technical observations as we said our bye byes.

[craigj2k12]

Originally Posted by qasdfdsaq

Cockup on the outbound path from the hosting network. Not surprising as that's the direction most traffic flows in for most hosting providers.

define cockup

4 or 5 days in a row, or whatever its been itsnt a cockup, its a pattern. You think a website hosted with NCUK are releasing TV episodes or something at that time causing massive amounts of data to saturate NCUK's bandwidth?

---------- Post added at 21:14 ---------- Previous post was at 21:13 ----------

Originally Posted by roughbeast

Just been on to Bangalore Ending up speaking a slow Indian accent. Why do I keep doing that?

Anyway, I explained to CS guy about the repeated blip; how it appears and disappears abruptly nation-wide almost as if someone was throwing a switch. He said it was probably because of high usage during that time! I agreed, but also said that didn't explain its abruptness. Surely the blip would commence gradually as folk got home from work and then would tail off as users went too bed. He offered to send a technician! I growled at this point and repeated what I had said in an even slower manner, and added that I have friends all over the country observing the same thing.

He has escalated the problem and has promised that I will get a phone call from higher up; from the Himalayas I guess. He thanked me for my technical observations as we said our bye byes.

is it actually service affecting? looks like just an issue between TBB and VM

[Qtx]

Originally Posted by craigj2k12

is it actually service affecting? looks like just an issue between TBB and VM

Its not just to TBB. Just a random site that happens to use a similar route.... blackhatworld.com

Gets slow around the same time, same place for the ping increase too.

[Sephiroth]

It's affecting my upstream noticeably. So I'd say service affecting.

---------- Post added at 21:41 ---------- Previous post was at 21:33 ----------

Originally Posted by qasdfdsaq

Cockup on the outbound path from the hosting network. Not surprising as that's the direction most traffic flows in for most hosting providers.

What cockup on the outbound path?

[roughbeast]

Originally Posted by craigj2k12

is it actually service affecting? looks like just an issue between TBB and VM

It grieves me to say so, but I have just run a series of speed tests Speedtest.net/NAMESCO and I am getting < 40Mb. Also on Wolfenstein Enemy Territory my ping is >100Ms; worse than the average 40Ms for other players.

I reckon we are getting a mixed effect/cause here. VM's connection to TBB has never been that good, so it will sometimes appear relatively bad. However, this does not explain the abrupt arrival and disappearance of the blip each evening. Neither does it explain some of the service effects that others and now I have been reporting. Is someone throwing a switch? Is it an automated and timed response to expected congestion issues aimed at avoiding wholesale outages, but at the qualitative expense of everybody's evening service?