50M Think Broadband Ping Monitor Results (POST YOURS) - Page 155

roughbeast · 12-10-2012, 19:22

Quote:

Originally Posted by RealDiamond

If it follows last weeks pattern tonight and the weekend will be bump free...

Thanks. The time for its appearance has just passed. We will see what Monday brings.

So what is so different about Friday nights that VM don't feel the need to make us all suffer?

GrimUpNorth · 12-10-2012, 19:50

Call me paranoid, but I recon I can just see my graph starting to get the hump!!

Cheers

Grim

joglynne · 12-10-2012, 19:53

Quote:

Originally Posted by GrimUpNorth

Call me paranoid, but I recon I can just see my graph starting to get the hump!!

Cheers

Grim

Same here, maybe it's a northern hump?

GrimUpNorth · 12-10-2012, 19:59

Not paranoid, hold on tight - it's hump time

Cheers

Grim

dwarven · 12-10-2012, 20:00

Yep its creeping up again

Qtx · 12-10-2012, 20:01

Just starting!

Will see if I can get the layer4 pings done when the bump gets a bit bigger, although not sure what that would prove if anything?

asbo dog · 12-10-2012, 20:05

same hump, was going to stick one of my kids on onlive batman which he paid for out his pocket money but on starting onlive it gives the high latency wqarning and to expect a stressful time yader yader

going to wireshark some off onlive ip's an see what they give as tbb an bbc seem fine at mo

Qtx · 12-10-2012, 20:14

Getting some weird results, but part of that could be the crappy over-utilisation problem on my UBR. rst/ack packets are consistent at the last hop though....

Spoiler:

BBC for comparison....some lag on VM network

Spoiler:

Second BBC trace, getting more screwed than the previous one, syn/ack too, so maybe tcp route does that on the last hop anyway.

Spoiler:

roughbeast · 12-10-2012, 20:45

So we do have a bump on a Friday night! Here goes.

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

Trace complete.

Ping test not working. It is failing to find a ping server good enough it seems.
So here's a trace route to the ping test server selected as being the best!

tracert xilo.net

Tracing route to xilo.net [91.199.78.20]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms REDDWARF [192.168.1.1]
2 11 ms 7 ms 7 ms 10.14.112.1
3 6 ms 7 ms 8 ms brhm-core-2b-ae3-1179.network.virginmedia.net [2
13.106.229.225]
4 15 ms 7 ms 8 ms brhm-bb-1b-ae8-0.network.virginmedia.net [62.253
.174.77]
5 15 ms 9 ms 10 ms manc-bb-1a-as6-0.network.virginmedia.net [62.253
.185.134]
6 44 ms 38 ms 9 ms manc-bb-1b-ae0-0.network.virginmedia.net [62.253
.187.178]
7 16 ms 15 ms 16 ms tele-ic-3-ae0-0.network.virginmedia.net [212.43.
163.70]
8 16 ms 17 ms 16 ms 10ge-linx226.c4l.co.uk [195.66.236.201]
9 15 ms 24 ms 15 ms swanzo-wolverine.c4l.co.uk [84.45.90.194]
10 22 ms 15 ms 21 ms ge-0-1-0-6.rtr-0.bs3.mhd.uk.as44574.net [84.45.4
8.6]
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.

craigj2k12 · 12-10-2012, 20:56

Cant understand why this is only affecting VM? Mines fine

Code:

C:\Users\Craig>tracert pingbox1.thinkbroadband.com

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

  1    <1 ms    <1 ms    <1 ms  E4200 [192.168.1.1]
  2     *        *        *     Request timed out.
  3    13 ms    11 ms    11 ms  ip-84-38-37-10.easynet.co.uk [84.38.37.10]
  4    13 ms    15 ms    15 ms  te0-0-0-2.er11.thlon.ov.easynet.net [89.200.135.
133]
  5    11 ms    10 ms    10 ms  linx-gw1.thn.ncuk.net [195.66.224.240]
  6    12 ms    12 ms    12 ms  gi0-24-10-star1.core-rs2.thdo.ncuk.net [80.249.9
7.9]
  7    11 ms    11 ms    11 ms  pingbox1.thinkbroadband.com [80.249.99.164]

Trace complete.

C:\Users\Craig>

alwaysabear · 12-10-2012, 20:59

Its started later tonight .

thenry · 12-10-2012, 21:14

Quote:

Originally Posted by thenry

07/10/2012

08/10/2012

09/10/2012

10/10/2012

11/10/2012

12/10/2012

roughbeast · 12-10-2012, 21:57

Quote:

Originally Posted by craigj2k12

Cant understand why this is only affecting VM? Mines fine

It's because it's a VM network problem. VM is deciding that around 7.00pm that they will heavily diminish everybody's service, presumably to prevent some from losing all their service. At around 10.30 they switch off whatever device it is that is making a mockery of their sales pitch, and we get our proper service back.

What bugs me is that it happens at precisely the time when we need maximum service for streaming and gaming.

edit.............................................. .................................................. ...........

Normal service just resumed.

Currently, on hold, on the phone to our man in Bangalore.

ferretuk · 12-10-2012, 22:13

Quote:

Originally Posted by roughbeast

It's because it's a VM network problem. VM is deciding that around 7.00pm that they will heavily diminish everbody's service, presumably to prevent some from losing all their service. At around 10.30 they switch off whatever device it is that is making a mockery of their sales pitch, and we get our proper service back.

What bugs me is that it happens at precisely the time when we need maximum service for streaming and gaming.

www.conspiracytheory.com is that way ------->

craigj2k12 · 12-10-2012, 22:14

Quote:

Originally Posted by roughbeast

It's because it's a VM network problem. VM is deciding that around 7.00pm that they will heavily diminish everbody's service, presumably to prevent some from losing all their service. At around 10.30 they switch off whatever device it is that is making a mockery of their sales pitch, and we get our proper service back.

What bugs me is that it happens at precisely the time when we need maximum service for streaming and gaming.

Thats not what happening here