General Discussion
  >> Broadband Quality Monitor


Register (or login) on our website and you will not see this ad.


Pages in this thread: 1 | [2] | 3 | (show all)   Print Thread
Standard User Squibbles
(newbie) Fri 16-Dec-16 14:51:53
Print Post

Re: Virgin Media BQM Graph - Lots of jitter? and 'Yellow'


[re: ian72] [link to this post]
 
Here is another one from bbc about 7-8 spikes in the list which is above the 25ms mark - I counted 7 that don't look normal before I stopped it.

C:\Users\ping www.bbc.co.uk -t

Pinging www.bbc.net.uk [212.58.246.94] with 32 bytes o
Reply from 212.58.246.94: bytes=32 time=27ms TTL=51
Reply from 212.58.246.94: bytes=32 time=25ms TTL=51
Reply from 212.58.246.94: bytes=32 time=24ms TTL=51
Reply from 212.58.246.94: bytes=32 time=27ms TTL=51
Reply from 212.58.246.94: bytes=32 time=175ms TTL=51
Reply from 212.58.246.94: bytes=32 time=194ms TTL=51

Reply from 212.58.246.94: bytes=32 time=94ms TTL=51
Reply from 212.58.246.94: bytes=32 time=35ms TTL=51

Reply from 212.58.246.94: bytes=32 time=27ms TTL=51
Reply from 212.58.246.94: bytes=32 time=25ms TTL=51
Reply from 212.58.246.94: bytes=32 time=26ms TTL=51
Reply from 212.58.246.94: bytes=32 time=25ms TTL=51
Reply from 212.58.246.94: bytes=32 time=106ms TTL=51
Reply from 212.58.246.94: bytes=32 time=25ms TTL=51
Reply from 212.58.246.94: bytes=32 time=63ms TTL=51
Reply from 212.58.246.94: bytes=32 time=29ms TTL=51
Reply from 212.58.246.94: bytes=32 time=25ms TTL=51
Reply from 212.58.246.94: bytes=32 time=25ms TTL=51
Reply from 212.58.246.94: bytes=32 time=29ms TTL=51
Reply from 212.58.246.94: bytes=32 time=24ms TTL=51
Reply from 212.58.246.94: bytes=32 time=27ms TTL=51
Reply from 212.58.246.94: bytes=32 time=25ms TTL=51
Reply from 212.58.246.94: bytes=32 time=27ms TTL=51
Reply from 212.58.246.94: bytes=32 time=24ms TTL=51
Reply from 212.58.246.94: bytes=32 time=29ms TTL=51
Reply from 212.58.246.94: bytes=32 time=28ms TTL=51
Reply from 212.58.246.94: bytes=32 time=28ms TTL=51
Reply from 212.58.246.94: bytes=32 time=27ms TTL=51
Reply from 212.58.246.94: bytes=32 time=25ms TTL=51
Reply from 212.58.246.94: bytes=32 time=25ms TTL=51
Reply from 212.58.246.94: bytes=32 time=27ms TTL=51
Reply from 212.58.246.94: bytes=32 time=25ms TTL=51
Reply from 212.58.246.94: bytes=32 time=26ms TTL=51
Reply from 212.58.246.94: bytes=32 time=26ms TTL=51
Reply from 212.58.246.94: bytes=32 time=26ms TTL=51
Reply from 212.58.246.94: bytes=32 time=25ms TTL=51
Reply from 212.58.246.94: bytes=32 time=27ms TTL=51
Reply from 212.58.246.94: bytes=32 time=23ms TTL=51
Reply from 212.58.246.94: bytes=32 time=27ms TTL=51
Reply from 212.58.246.94: bytes=32 time=27ms TTL=51
Reply from 212.58.246.94: bytes=32 time=26ms TTL=51
Reply from 212.58.246.94: bytes=32 time=27ms TTL=51
Reply from 212.58.246.94: bytes=32 time=27ms TTL=51
Reply from 212.58.246.94: bytes=32 time=28ms TTL=51
Reply from 212.58.246.94: bytes=32 time=25ms TTL=51
Reply from 212.58.246.94: bytes=32 time=25ms TTL=51
Reply from 212.58.246.94: bytes=32 time=25ms TTL=51
Reply from 212.58.246.94: bytes=32 time=25ms TTL=51
Reply from 212.58.246.94: bytes=32 time=27ms TTL=51
Reply from 212.58.246.94: bytes=32 time=29ms TTL=51
Reply from 212.58.246.94: bytes=32 time=86ms TTL=51
Reply from 212.58.246.94: bytes=32 time=24ms TTL=51
Reply from 212.58.246.94: bytes=32 time=54ms TTL=51
Reply from 212.58.246.94: bytes=32 time=24ms TTL=51
Reply from 212.58.246.94: bytes=32 time=29ms TTL=51
Reply from 212.58.246.94: bytes=32 time=27ms TTL=51
Reply from 212.58.246.94: bytes=32 time=27ms TTL=51
Reply from 212.58.246.94: bytes=32 time=24ms TTL=51
Reply from 212.58.246.94: bytes=32 time=29ms TTL=51
Reply from 212.58.246.94: bytes=32 time=25ms TTL=51
Reply from 212.58.246.94: bytes=32 time=27ms TTL=51
Reply from 212.58.246.94: bytes=32 time=24ms TTL=51
Reply from 212.58.246.94: bytes=32 time=27ms TTL=51
Reply from 212.58.246.94: bytes=32 time=26ms TTL=51
Reply from 212.58.246.94: bytes=32 time=28ms TTL=51
Reply from 212.58.246.94: bytes=32 time=25ms TTL=51
Reply from 212.58.246.94: bytes=32 time=27ms TTL=51
Reply from 212.58.246.94: bytes=32 time=26ms TTL=51
Reply from 212.58.246.94: bytes=32 time=25ms TTL=51
Reply from 212.58.246.94: bytes=32 time=25ms TTL=51
Reply from 212.58.246.94: bytes=32 time=32ms TTL=51
Reply from 212.58.246.94: bytes=32 time=25ms TTL=51
Reply from 212.58.246.94: bytes=32 time=27ms TTL=51
Reply from 212.58.246.94: bytes=32 time=25ms TTL=51
Reply from 212.58.246.94: bytes=32 time=25ms TTL=51
Reply from 212.58.246.94: bytes=32 time=29ms TTL=51
Reply from 212.58.246.94: bytes=32 time=27ms TTL=51
Reply from 212.58.246.94: bytes=32 time=25ms TTL=51
Reply from 212.58.246.94: bytes=32 time=27ms TTL=51
Reply from 212.58.246.94: bytes=32 time=27ms TTL=51
Reply from 212.58.246.94: bytes=32 time=25ms TTL=51
Reply from 212.58.246.94: bytes=32 time=27ms TTL=51
Reply from 212.58.246.94: bytes=32 time=25ms TTL=51
Reply from 212.58.246.94: bytes=32 time=25ms TTL=51
Reply from 212.58.246.94: bytes=32 time=25ms TTL=51
Reply from 212.58.246.94: bytes=32 time=24ms TTL=51
Reply from 212.58.246.94: bytes=32 time=25ms TTL=51
Reply from 212.58.246.94: bytes=32 time=25ms TTL=51
Reply from 212.58.246.94: bytes=32 time=52ms TTL=51
Reply from 212.58.246.94: bytes=32 time=25ms TTL=51
Reply from 212.58.246.94: bytes=32 time=29ms TTL=51
Reply from 212.58.246.94: bytes=32 time=27ms TTL=51
Reply from 212.58.246.94: bytes=32 time=23ms TTL=51
Reply from 212.58.246.94: bytes=32 time=25ms TTL=51
Reply from 212.58.246.94: bytes=32 time=28ms TTL=51
Reply from 212.58.246.94: bytes=32 time=26ms TTL=51

Ping statistics for 212.58.246.94:
Packets: Sent = 96, Received = 96, Lost = 0 (0% lo
Approximate round trip times in milli-seconds:
Minimum = 23ms, Maximum = 194ms, Average = 32ms
Control-C

Edited by Squibbles (Fri 16-Dec-16 15:00:08)

Standard User Squibbles
(newbie) Fri 16-Dec-16 14:57:07
Print Post

Re: Virgin Media BQM Graph - Lots of jitter? and 'Yellow'


[re: Squibbles] [link to this post]
 
Here is google..

C:\Users\ping www.google.co.uk -t

Pinging www.google.co.uk [62.253.72.187] with 32 bytes of data:
Reply from 62.253.72.187: bytes=32 time=19ms TTL=59
Reply from 62.253.72.187: bytes=32 time=11ms TTL=59
Reply from 62.253.72.187: bytes=32 time=13ms TTL=59
Reply from 62.253.72.187: bytes=32 time=11ms TTL=59
Reply from 62.253.72.187: bytes=32 time=12ms TTL=59
Reply from 62.253.72.187: bytes=32 time=13ms TTL=59
Reply from 62.253.72.187: bytes=32 time=17ms TTL=59
Reply from 62.253.72.187: bytes=32 time=13ms TTL=59
Reply from 62.253.72.187: bytes=32 time=12ms TTL=59
Reply from 62.253.72.187: bytes=32 time=12ms TTL=59
Reply from 62.253.72.187: bytes=32 time=12ms TTL=59
Reply from 62.253.72.187: bytes=32 time=13ms TTL=59
Reply from 62.253.72.187: bytes=32 time=13ms TTL=59
Reply from 62.253.72.187: bytes=32 time=13ms TTL=59
Reply from 62.253.72.187: bytes=32 time=12ms TTL=59
Reply from 62.253.72.187: bytes=32 time=14ms TTL=59
Reply from 62.253.72.187: bytes=32 time=12ms TTL=59
Reply from 62.253.72.187: bytes=32 time=12ms TTL=59
Reply from 62.253.72.187: bytes=32 time=15ms TTL=59
Reply from 62.253.72.187: bytes=32 time=12ms TTL=59
Reply from 62.253.72.187: bytes=32 time=12ms TTL=59
Reply from 62.253.72.187: bytes=32 time=11ms TTL=59
Reply from 62.253.72.187: bytes=32 time=12ms TTL=59
Reply from 62.253.72.187: bytes=32 time=11ms TTL=59
Reply from 62.253.72.187: bytes=32 time=14ms TTL=59
Reply from 62.253.72.187: bytes=32 time=12ms TTL=59
Reply from 62.253.72.187: bytes=32 time=12ms TTL=59
Reply from 62.253.72.187: bytes=32 time=12ms TTL=59
Reply from 62.253.72.187: bytes=32 time=12ms TTL=59
Reply from 62.253.72.187: bytes=32 time=12ms TTL=59
Reply from 62.253.72.187: bytes=32 time=14ms TTL=59
Reply from 62.253.72.187: bytes=32 time=15ms TTL=59
Reply from 62.253.72.187: bytes=32 time=11ms TTL=59
Reply from 62.253.72.187: bytes=32 time=15ms TTL=59
Reply from 62.253.72.187: bytes=32 time=12ms TTL=59
Reply from 62.253.72.187: bytes=32 time=12ms TTL=59
Reply from 62.253.72.187: bytes=32 time=14ms TTL=59
Reply from 62.253.72.187: bytes=32 time=36ms TTL=59
Reply from 62.253.72.187: bytes=32 time=16ms TTL=59
Reply from 62.253.72.187: bytes=32 time=22ms TTL=59
Reply from 62.253.72.187: bytes=32 time=13ms TTL=59
Reply from 62.253.72.187: bytes=32 time=12ms TTL=59
Reply from 62.253.72.187: bytes=32 time=13ms TTL=59
Reply from 62.253.72.187: bytes=32 time=12ms TTL=59
Reply from 62.253.72.187: bytes=32 time=15ms TTL=59
Reply from 62.253.72.187: bytes=32 time=12ms TTL=59
Reply from 62.253.72.187: bytes=32 time=12ms TTL=59
Reply from 62.253.72.187: bytes=32 time=12ms TTL=59
Reply from 62.253.72.187: bytes=32 time=14ms TTL=59
Reply from 62.253.72.187: bytes=32 time=12ms TTL=59
Reply from 62.253.72.187: bytes=32 time=11ms TTL=59
Reply from 62.253.72.187: bytes=32 time=172ms TTL=59
Reply from 62.253.72.187: bytes=32 time=47ms TTL=59

Reply from 62.253.72.187: bytes=32 time=12ms TTL=59
Reply from 62.253.72.187: bytes=32 time=197ms TTL=59
Reply from 62.253.72.187: bytes=32 time=25ms TTL=59

Reply from 62.253.72.187: bytes=32 time=12ms TTL=59
Reply from 62.253.72.187: bytes=32 time=15ms TTL=59
Reply from 62.253.72.187: bytes=32 time=13ms TTL=59
Reply from 62.253.72.187: bytes=32 time=12ms TTL=59
Reply from 62.253.72.187: bytes=32 time=13ms TTL=59
Reply from 62.253.72.187: bytes=32 time=12ms TTL=59
Reply from 62.253.72.187: bytes=32 time=12ms TTL=59
Reply from 62.253.72.187: bytes=32 time=19ms TTL=59
Reply from 62.253.72.187: bytes=32 time=11ms TTL=59
Reply from 62.253.72.187: bytes=32 time=11ms TTL=59
Reply from 62.253.72.187: bytes=32 time=15ms TTL=59
Reply from 62.253.72.187: bytes=32 time=11ms TTL=59
Reply from 62.253.72.187: bytes=32 time=12ms TTL=59
Reply from 62.253.72.187: bytes=32 time=11ms TTL=59
Reply from 62.253.72.187: bytes=32 time=12ms TTL=59
Reply from 62.253.72.187: bytes=32 time=12ms TTL=59
Reply from 62.253.72.187: bytes=32 time=14ms TTL=59
Reply from 62.253.72.187: bytes=32 time=11ms TTL=59
Reply from 62.253.72.187: bytes=32 time=12ms TTL=59
Reply from 62.253.72.187: bytes=32 time=11ms TTL=59
Reply from 62.253.72.187: bytes=32 time=11ms TTL=59
Reply from 62.253.72.187: bytes=32 time=114ms TTL=59

Ping statistics for 62.253.72.187:
Packets: Sent = 78, Received = 78, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 11ms, Maximum = 197ms, Average = 19ms

Anything above 15 I flagged up here...

Surely these spikes aren't normal?

Just to make sure I haven't made a boo boo.. I configured the graph using the WAN IP address of Virgin Media and not my local router address eg 192.168.x.x

Edited by Squibbles (Fri 16-Dec-16 15:00:38)

Standard User ian72
(eat-sleep-adslguide) Fri 16-Dec-16 14:57:08
Print Post

Re: Virgin Media BQM Graph - Lots of jitter? and 'Yellow'


[re: Squibbles] [link to this post]
 
That appears to be what is showing up in the monitor. Definitely not something right there - could be a problem in the Virgin network.


Register (or login) on our website and you will not see this ad.

Standard User Squibbles
(newbie) Fri 16-Dec-16 14:59:17
Print Post

Re: Virgin Media BQM Graph - Lots of jitter? and 'Yellow'


[re: ian72] [link to this post]
 
I have spoken to Virgin today and they guy (level 2 support) was most unhelpful!

Said 'everything is normal' and you get max speeds and we do not recognise the BQM and 'we use our own diagnostic tools' and literally made me so mad I slammed the phone down.

They refuse to acknowledge a problem and I have asked to speak to a manager.

Really don't know how to get this resolved..

Edited by Squibbles (Fri 16-Dec-16 15:01:14)

Standard User ian72
(eat-sleep-adslguide) Fri 16-Dec-16 15:06:01
Print Post

Re: Virgin Media BQM Graph - Lots of jitter? and 'Yellow'


[re: Squibbles] [link to this post]
 
In video terms you are seeing "jitter" - latency is fine but consistency of it is not so good. That can impact on live video/voice and also on gaming. But, I'm not surprised they are saying there is no problem - it is par for the course with big ISPs and unfortunately I have no direct experience with cable so unable to help further I'm afraid.

A definition of jitter:

Jitter is defined as a variation in the delay of received packets. The sending side transmits packets in a continuous stream and spaces them evenly apart. Because of network congestion, improper queuing, or configuration errors, the delay between packets can vary instead of remaining constant

Edited by ian72 (Fri 16-Dec-16 15:06:20)

Standard User Squibbles
(newbie) Fri 16-Dec-16 15:10:36
Print Post

Re: Virgin Media BQM Graph - Lots of jitter? and 'Yellow'


[re: ian72] [link to this post]
 
I am not sure if Roberto is able to add anything?

I am going to call VM again and ask to speak to a manager.
Standard User RobertoS
(elder) Fri 16-Dec-16 18:58:45
Print Post

Re: Virgin Media BQM Graph - Lots of jitter? and 'Yellow'


[re: Squibbles] [link to this post]
 
I've been away smile. Ian has done a great job. Re them not recognising the thinkbroadband BQM, that isn't surprising, but there's a fair chance an ADR panel would.

I don't recommend getting them to compare your BQM to mine in my sig, as they both say AA, which is a premium level ISP not mass market, but you might find some useful ones in the BT or Fibre forums here. You might like to compare my -t pings to yours though and let them see those:-

C:\Users\Bob>ping www.bbc.net.uk -t

Pinging www.bbc.net.uk [212.58.244.71] with 32 bytes of data:
Reply from 212.58.244.71: bytes=32 time=12ms TTL=56
Reply from 212.58.244.71: bytes=32 time=12ms TTL=56
Reply from 212.58.244.71: bytes=32 time=12ms TTL=56
Reply from 212.58.244.71: bytes=32 time=12ms TTL=56
Reply from 212.58.244.71: bytes=32 time=12ms TTL=56
Reply from 212.58.244.71: bytes=32 time=12ms TTL=56
Reply from 212.58.244.71: bytes=32 time=12ms TTL=56
Reply from 212.58.244.71: bytes=32 time=12ms TTL=56
Reply from 212.58.244.71: bytes=32 time=12ms TTL=56
Reply from 212.58.244.71: bytes=32 time=12ms TTL=56
Reply from 212.58.244.71: bytes=32 time=12ms TTL=56
Reply from 212.58.244.71: bytes=32 time=12ms TTL=56
Reply from 212.58.244.71: bytes=32 time=12ms TTL=56
Reply from 212.58.244.71: bytes=32 time=12ms TTL=56
Reply from 212.58.244.71: bytes=32 time=12ms TTL=56
Reply from 212.58.244.71: bytes=32 time=12ms TTL=56
Reply from 212.58.244.71: bytes=32 time=12ms TTL=56
Reply from 212.58.244.71: bytes=32 time=12ms TTL=56
Reply from 212.58.244.71: bytes=32 time=12ms TTL=56
Reply from 212.58.244.71: bytes=32 time=12ms TTL=56
Reply from 212.58.244.71: bytes=32 time=12ms TTL=56
Reply from 212.58.244.71: bytes=32 time=12ms TTL=56
Reply from 212.58.244.71: bytes=32 time=12ms TTL=56
Reply from 212.58.244.71: bytes=32 time=12ms TTL=56
Reply from 212.58.244.71: bytes=32 time=12ms TTL=56
Reply from 212.58.244.71: bytes=32 time=13ms TTL=56
Reply from 212.58.244.71: bytes=32 time=12ms TTL=56
Reply from 212.58.244.71: bytes=32 time=13ms TTL=56
Reply from 212.58.244.71: bytes=32 time=15ms TTL=56
Reply from 212.58.244.71: bytes=32 time=12ms TTL=56
Reply from 212.58.244.71: bytes=32 time=13ms TTL=56
Reply from 212.58.244.71: bytes=32 time=12ms TTL=56
Reply from 212.58.244.71: bytes=32 time=13ms TTL=56
Reply from 212.58.244.71: bytes=32 time=12ms TTL=56
Reply from 212.58.244.71: bytes=32 time=12ms TTL=56
Reply from 212.58.244.71: bytes=32 time=12ms TTL=56
Reply from 212.58.244.71: bytes=32 time=12ms TTL=56
Reply from 212.58.244.71: bytes=32 time=12ms TTL=56
Reply from 212.58.244.71: bytes=32 time=15ms TTL=56
Reply from 212.58.244.71: bytes=32 time=15ms TTL=56
Reply from 212.58.244.71: bytes=32 time=12ms TTL=56
Reply from 212.58.244.71: bytes=32 time=12ms TTL=56
Reply from 212.58.244.71: bytes=32 time=12ms TTL=56
Reply from 212.58.244.71: bytes=32 time=12ms TTL=56
Reply from 212.58.244.71: bytes=32 time=12ms TTL=56
Reply from 212.58.244.71: bytes=32 time=12ms TTL=56
Reply from 212.58.244.71: bytes=32 time=12ms TTL=56
Reply from 212.58.244.71: bytes=32 time=12ms TTL=56
Reply from 212.58.244.71: bytes=32 time=12ms TTL=56
Reply from 212.58.244.71: bytes=32 time=12ms TTL=56
Reply from 212.58.244.71: bytes=32 time=12ms TTL=56
Reply from 212.58.244.71: bytes=32 time=12ms TTL=56
Reply from 212.58.244.71: bytes=32 time=12ms TTL=56
Reply from 212.58.244.71: bytes=32 time=12ms TTL=56
Reply from 212.58.244.71: bytes=32 time=12ms TTL=56
Reply from 212.58.244.71: bytes=32 time=12ms TTL=56
Reply from 212.58.244.71: bytes=32 time=13ms TTL=56
Reply from 212.58.244.71: bytes=32 time=12ms TTL=56
Reply from 212.58.244.71: bytes=32 time=12ms TTL=56
Reply from 212.58.244.71: bytes=32 time=12ms TTL=56
Reply from 212.58.244.71: bytes=32 time=13ms TTL=56
Reply from 212.58.244.71: bytes=32 time=12ms TTL=56
Reply from 212.58.244.71: bytes=32 time=12ms TTL=56
Reply from 212.58.244.71: bytes=32 time=12ms TTL=56
Reply from 212.58.244.71: bytes=32 time=12ms TTL=56
Reply from 212.58.244.71: bytes=32 time=12ms TTL=56

Ping statistics for 212.58.244.71:
Packets: Sent = 66, Received = 66, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 12ms, Maximum = 15ms, Average = 12ms
Control-C
^C
C:\Users\Bob>ping www.google.co.uk -4 -t

Pinging www.google.co.uk [216.58.213.99] with 32 bytes of data:
Reply from 216.58.213.99: bytes=32 time=15ms TTL=57
Reply from 216.58.213.99: bytes=32 time=12ms TTL=57
Reply from 216.58.213.99: bytes=32 time=12ms TTL=57
Reply from 216.58.213.99: bytes=32 time=12ms TTL=57
Reply from 216.58.213.99: bytes=32 time=12ms TTL=57
Reply from 216.58.213.99: bytes=32 time=12ms TTL=57
Reply from 216.58.213.99: bytes=32 time=12ms TTL=57
Reply from 216.58.213.99: bytes=32 time=12ms TTL=57
Reply from 216.58.213.99: bytes=32 time=12ms TTL=57
Reply from 216.58.213.99: bytes=32 time=12ms TTL=57
Reply from 216.58.213.99: bytes=32 time=12ms TTL=57
Reply from 216.58.213.99: bytes=32 time=12ms TTL=57
Reply from 216.58.213.99: bytes=32 time=12ms TTL=57
Reply from 216.58.213.99: bytes=32 time=12ms TTL=57
Reply from 216.58.213.99: bytes=32 time=12ms TTL=57
Reply from 216.58.213.99: bytes=32 time=12ms TTL=57
Reply from 216.58.213.99: bytes=32 time=12ms TTL=57
Reply from 216.58.213.99: bytes=32 time=12ms TTL=57
Reply from 216.58.213.99: bytes=32 time=12ms TTL=57
Reply from 216.58.213.99: bytes=32 time=12ms TTL=57
Reply from 216.58.213.99: bytes=32 time=12ms TTL=57
Reply from 216.58.213.99: bytes=32 time=12ms TTL=57
Reply from 216.58.213.99: bytes=32 time=12ms TTL=57
Reply from 216.58.213.99: bytes=32 time=14ms TTL=57
Reply from 216.58.213.99: bytes=32 time=13ms TTL=57
Reply from 216.58.213.99: bytes=32 time=12ms TTL=57
Reply from 216.58.213.99: bytes=32 time=12ms TTL=57
Reply from 216.58.213.99: bytes=32 time=12ms TTL=57
Reply from 216.58.213.99: bytes=32 time=12ms TTL=57
Reply from 216.58.213.99: bytes=32 time=13ms TTL=57
Reply from 216.58.213.99: bytes=32 time=13ms TTL=57
Reply from 216.58.213.99: bytes=32 time=13ms TTL=57
Reply from 216.58.213.99: bytes=32 time=12ms TTL=57
Reply from 216.58.213.99: bytes=32 time=13ms TTL=57
Reply from 216.58.213.99: bytes=32 time=12ms TTL=57
Reply from 216.58.213.99: bytes=32 time=12ms TTL=57
Reply from 216.58.213.99: bytes=32 time=12ms TTL=57
Reply from 216.58.213.99: bytes=32 time=12ms TTL=57
Reply from 216.58.213.99: bytes=32 time=12ms TTL=57
Reply from 216.58.213.99: bytes=32 time=12ms TTL=57
Reply from 216.58.213.99: bytes=32 time=12ms TTL=57
Reply from 216.58.213.99: bytes=32 time=13ms TTL=57
Reply from 216.58.213.99: bytes=32 time=12ms TTL=57
Reply from 216.58.213.99: bytes=32 time=12ms TTL=57
Reply from 216.58.213.99: bytes=32 time=12ms TTL=57
Reply from 216.58.213.99: bytes=32 time=12ms TTL=57
Reply from 216.58.213.99: bytes=32 time=12ms TTL=57
Reply from 216.58.213.99: bytes=32 time=14ms TTL=57
Reply from 216.58.213.99: bytes=32 time=12ms TTL=57
Reply from 216.58.213.99: bytes=32 time=12ms TTL=57
Reply from 216.58.213.99: bytes=32 time=12ms TTL=57
Reply from 216.58.213.99: bytes=32 time=12ms TTL=57
Reply from 216.58.213.99: bytes=32 time=13ms TTL=57
Reply from 216.58.213.99: bytes=32 time=12ms TTL=57
Reply from 216.58.213.99: bytes=32 time=12ms TTL=57
Reply from 216.58.213.99: bytes=32 time=12ms TTL=57
Reply from 216.58.213.99: bytes=32 time=12ms TTL=57

Ping statistics for 216.58.213.99:
Packets: Sent = 57, Received = 57, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 12ms, Maximum = 15ms, Average = 12ms
Control-C
^C
C:\Users\Bob>

Kindness isn't going to cure the world of all its awfulness but it's a good place to begin. Daisy Ridley.
My broadband basic info/help site - www.robertos.me.uk. Domains, site and mail hosting - Tsohost.
Connection - AAISP Home::1 80/20. Sync 43998/16174bps frown @ 600m. BQMs - IPv4 & IPv6
Standard User Squibbles
(newbie) Fri 16-Dec-16 19:47:54
Print Post

Re: Virgin Media BQM Graph - Lots of jitter? and 'Yellow'


[re: RobertoS] [link to this post]
 
I just spoke to them and have switched my Superhub 3.0 to a SH2ac and see if this has an effect.

They have also said they cant see any network congestion or any other issues. The advisor stated that a 'ping' is a low quality traffic and if you send a 'continuous ping' you will get high numbers back the first time because it is trying to make a connection and then the numbers will fluctuate because you are continuously sending traffic.

I don't agree with this but didn't have any strong points or the knowledge to counter it back. He said there preferred method is to run a tracert and generally the problems will be associated with 'Pairing' or the handover after leaving the Virgin Network or with an issue on the cable and they can look at that.

He did however agree with me when I ran a tracert to the gaming server that I use that something doesn't look quite right and I have provided him with the tracert and he has agreed to raise it for a 're-routing'.

I am continuously monitoring the latency now on my line with the new device and see what the new equipment yields and am due to have a scheduled conversation with him on Monday.

Is ADR the ombudsmen service ? and what points can I use to counter the argument about the continuous ping?

Thank You

Edited by Squibbles (Fri 16-Dec-16 19:54:30)

Administrator MrSaffron
(staff) Sat 17-Dec-16 11:45:57
Print Post

Re: Virgin Media BQM Graph - Lots of jitter? and 'Yellow'


[re: Squibbles] [link to this post]
 
SuperHub 3 has known issues with its CPU getting busy and thus means latency is impacted, so different modem hardware may help.

Based on the support persons theory everyone connection should look like yours
http://www.thinkbroadband.com/ping/share/635ad23807c...

Is a good example of what you should get on a reasonable connection, this is a 1.5km long VDSL2 line, so less than ideal but good latency. The yellow matching up when I am sat down working, and the big yellow/blue spike was a big download/upload sequence in short when you'd expect latency to vary.

To counter you would use examples like above, because if the continuous ping behaviour was inherent in how ICMP and ping is handled then all connects would show the issue.

The author of the above post is a thinkbroadband staff member. It may not constitute an official statement on behalf of thinkbroadband.
Standard User Squibbles
(newbie) Sat 17-Dec-16 12:12:40
Print Post

Re: Virgin Media BQM Graph - Now improved a bit?


[re: MrSaffron] [link to this post]
 
Hello again,

Mr Saffron thank you for the response.

So yesterday I spent some time on the phone getting the SH2ac setup and have seen a vast improvement (but not sure if it can be improved further). For some reason my IP didn't change so I had to delete the old graph and start a new monitor which is below.

http://www.thinkbroadband.com/ping/share/4d2f58d8171...

There is the odd spike here and there and a 'blue streak'. For some reason the graph hasn't updated from 10am to 12pm .

Wondered what you guys make of the graph now?

Thank you
Pages in this thread: 1 | [2] | 3 | (show all)   Print Thread

Jump to