User comments on ISPs
  >> Virgin Media (Cable)


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


  Print Thread
Standard User amiga_dude
(newbie) Fri 21-Jul-17 18:36:05
Print Post

Is ThinkBroad montor broken?


[link to this post]
 
Little bit baffled about this. I have broadband montor that showing really bad ping.

https://www.thinkbroadband.com/broadband/monitoring/...

(Note the red is where I disconnected, also very long one about 14:00-15:00 [ish] is when I went out turn off my network when I went out.)

So then I sent out ping on My Windows 10 out to internet.

ping bbc.co.uk

Pinging bbc.co.uk [212.58.246.78] with 32 bytes of data:
Reply from 212.58.246.78: bytes=32 time=32ms TTL=53
Reply from 212.58.246.78: bytes=32 time=31ms TTL=53
Reply from 212.58.246.78: bytes=32 time=30ms TTL=53
Reply from 212.58.246.78: bytes=32 time=29ms TTL=53

Ping statistics for 212.58.246.78:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 29ms, Maximum = 32ms, Average = 30ms

C:\Users\Hairy>ping google.com

Pinging google.com [216.58.204.78] with 32 bytes of data:
Reply from 216.58.204.78: bytes=32 time=20ms TTL=51
Reply from 216.58.204.78: bytes=32 time=21ms TTL=51
Reply from 216.58.204.78: bytes=32 time=19ms TTL=51
Reply from 216.58.204.78: bytes=32 time=18ms TTL=51

Ping statistics for 216.58.204.78:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 18ms, Maximum = 21ms, Average = 19ms

C:\Users\Hairy>ping hotmail.com

Pinging hotmail.com [157.56.198.220] with 32 bytes of data:
Reply from 157.56.198.220: bytes=32 time=21ms TTL=239
Reply from 157.56.198.220: bytes=32 time=24ms TTL=239
Reply from 157.56.198.220: bytes=32 time=22ms TTL=239
Reply from 157.56.198.220: bytes=32 time=22ms TTL=239

Ping statistics for 157.56.198.220:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 21ms, Maximum = 24ms, Average = 22ms

C:\Users\Hairy>


That look alright so then I thought, I remote Raspberry Pi computer at family house so I ssh in to it and got it to ping me back.

ping 81.96.5*.*
PING 81.96.5*.* (81.96.5*.*) 56(84) bytes of data.
64 bytes from 81.96.5*.*: icmp_seq=1 ttl=57 time=24.5 ms
64 bytes from 81.96.5*.*: icmp_seq=2 ttl=57 time=33.0 ms
64 bytes from 81.96.5*.*: icmp_seq=3 ttl=57 time=25.8 ms
64 bytes from 81.96.5*.*: icmp_seq=4 ttl=57 time=34.1 ms
64 bytes from 81.96.5*.*: icmp_seq=5 ttl=57 time=26.4 ms
64 bytes from 81.96.5*.*: icmp_seq=6 ttl=57 time=24.6 ms
64 bytes from 81.96.5*.*: icmp_seq=7 ttl=57 time=24.5 ms
64 bytes from 81.96.5*.*: icmp_seq=8 ttl=57 time=48.1 ms
64 bytes from 81.96.5*.*: icmp_seq=9 ttl=57 time=26.4 ms
64 bytes from 81.96.5*.*: icmp_seq=10 ttl=57 time=26.2 ms
64 bytes from 81.96.5*.*: icmp_seq=11 ttl=57 time=23.1 ms
64 bytes from 81.96.5*.*: icmp_seq=12 ttl=57 time=23.7 ms
64 bytes from 81.96.5*.*: icmp_seq=13 ttl=57 time=25.5 ms
64 bytes from 81.96.5*.*: icmp_seq=14 ttl=57 time=28.1 ms
64 bytes from 81.96.5*.*: icmp_seq=15 ttl=57 time=27.1 ms
64 bytes from 81.96.5*.*: icmp_seq=16 ttl=57 time=30.3 ms
64 bytes from 81.96.5*.*: icmp_seq=17 ttl=57 time=26.8 ms
64 bytes from 81.96.5*.*: icmp_seq=18 ttl=57 time=24.8 ms
64 bytes from 81.96.5*.*: icmp_seq=19 ttl=57 time=21.3 ms
64 bytes from 81.96.5*.*: icmp_seq=20 ttl=57 time=26.4 ms
64 bytes from 81.96.5*.*: icmp_seq=21 ttl=57 time=24.5 ms
64 bytes from 81.96.5*.*: icmp_seq=22 ttl=57 time=26.9 ms
64 bytes from 81.96.5*.*: icmp_seq=23 ttl=57 time=23.8 ms
64 bytes from 81.96.5*.*: icmp_seq=24 ttl=57 time=25.0 ms
64 bytes from 81.96.5*.*: icmp_seq=25 ttl=57 time=25.8 ms
64 bytes from 81.96.5*.*: icmp_seq=26 ttl=57 time=24.4 ms
64 bytes from 81.96.5*.*: icmp_seq=27 ttl=57 time=25.9 ms
64 bytes from 81.96.5*.*: icmp_seq=28 ttl=57 time=33.6 ms
64 bytes from 81.96.5*.*: icmp_seq=29 ttl=57 time=26.7 ms
64 bytes from 81.96.5*.*: icmp_seq=30 ttl=57 time=32.7 ms
^C
--- 81.96.5*.* ping statistics ---
30 packets transmitted, 30 received, 0% packet loss, time 29050ms
rtt min/avg/max/mdev = 21.322/27.379/48.182/4.953 ms


That dosn't match the report I am getting from thinkbroadband monitor.
Standard User jchamier
(eat-sleep-adslguide) Fri 21-Jul-17 18:49:17
Print Post

Re: Is ThinkBroad montor broken?


[re: amiga_dude] [link to this post]
 
In reply to a post by amiga_dude:
That dosn't match the report I am getting from thinkbroadband monitor.
Your average is not that bad (blue line) - its the maximum that looks bad in yellow. Cable/DOCSIS systems by their nature have occasional slower latency on some packets. Remember the BQM sends a thousand pings a second. Not the one a second that a normal ping command does.

Is the machine you are remote controlling to ping you also on a Virgin connection?

Use this site to confirm the IP you think is yours is the one you are connecting OUT from, it will be the big IP in the middle:
http://www.ipchicken.com

Use this site to ping you from 4 different places in the world, outside the UK:
https://www.site24x7.com/ping-test.html

See if any of that is similar to the Thinkbroadband monitor.

It is quite possible Virgin Media is filtering traffic from ThinkBroadband.

plusnet unlimited fibre 80/20 - 2 Jun 14 - Sync at 20/May/17: 59,802/11,536 - G.INP & 3.5db SNRm
18 years of UK broadband since 1999 ntl:cable modem trial - Asus RT-AC68U and HG612 - BQM

Edited by jchamier (Fri 21-Jul-17 18:50:39)

Standard User uno
(knowledge is power) Sat 22-Jul-17 00:04:49
Print Post

Re: Is ThinkBroad montor broken?


[re: jchamier] [link to this post]
 
In reply to a post by jchamier:
Remember the BQM sends a thousand pings a second. Not the one a second that a normal ping command does.


It's not that many. It is 86400 per day (one per second). The graph shows an aggregated amount of 100 seconds and this is why you see the bigger variation as it is looking at data from a much wider sample in both terms of min, avg and max.

Matt

uno Communications
t: 0333 773 7700
Official Maidenhead, Milton Keynes & Sheffield Speedtest.net Host


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

Standard User amiga_dude
(newbie) Sat 22-Jul-17 10:03:00
Print Post

Re: Is ThinkBroad montor broken?


[re: uno] [link to this post]
 
Everthing is back normal now. The expected behavior resumed at about 21:00. I wasn't saying BQM was wrong but I wasn't getting equivalent results back from my own tests. It just one obvious issues which could happen. Just rember what happend with NASA and Hubble, tester could be giving wrong results.

At least we all learned something of how BQM works.

PS Is there anychance of a video on BQM? On how works etc (boot up) all the geeky info:-
electricity consumption,
cpu,
memory,
network capacity,
Anything learned from runing it,
etc.

https://www.youtube.com/user/thinkbroadband
All video's are from mainly 8 years ago.
Standard User jchamier
(eat-sleep-adslguide) Sat 22-Jul-17 10:18:14
Print Post

Re: Is ThinkBroad montor broken?


[re: amiga_dude] [link to this post]
 
You could ask the people that make it:
http://www.firebrick.co.uk/products_6000.php

plusnet unlimited fibre 80/20 - 2 Jun 14 - Sync at 20/May/17: 59,802/11,536 - G.INP & 3.5db SNRm
18 years of UK broadband since 1999 ntl:cable modem trial - Asus RT-AC68U and HG612 - BQM
Standard User jchamier
(eat-sleep-adslguide) Sat 22-Jul-17 10:21:34
Print Post

Re: Is ThinkBroad montor broken?


[re: uno] [link to this post]
 
In reply to a post by uno:
It's not that many. It is 86400 per day (one per second). The graph shows an aggregated amount of 100 seconds and this is why you see the bigger variation as it is looking at data from a much wider sample in both terms of min, avg and max.

That Matt, that makes much more sense. No idea where I got that stupidly large number from.

I wonder how many total BQMs are configured - it could be a lot of traffic for TBB.

plusnet unlimited fibre 80/20 - 2 Jun 14 - Sync at 20/May/17: 59,802/11,536 - G.INP & 3.5db SNRm
18 years of UK broadband since 1999 ntl:cable modem trial - Asus RT-AC68U and HG612 - BQM
Administrator MrSaffron
(staff) Sat 22-Jul-17 10:29:46
Print Post

Re: Is ThinkBroad montor broken?


[re: amiga_dude] [link to this post]
 
The BQM has some many variations that if you say one thing about a graph in a video it is going to be wrong for many viewing it...

There are FAQ online with example screen shots.

The videos take too long to create, i.e. script, shoot, edit compared to the time we can spend analysing speed and coverage information from our systems.

As some pointed out DOCSIS tends to show slightly worse graphs due to the nature of how it works, plus for those with Superhub 3 there are issues with the processor used (Intel Puma bug), have not ran a news story on that as really no change, as fix is on the way just slowly. Utilisation in the local area and congestion in the Virgin core network can have a big effect on the BQM and where its clear there is a widespread issue we do call it out.

The author of the above post is a thinkbroadband staff member. It may not constitute an official statement on behalf of thinkbroadband.
Standard User uno
(knowledge is power) Sat 22-Jul-17 13:23:56
Print Post

Re: Is ThinkBroad montor broken?


[re: amiga_dude] [link to this post]
 
The manual can be found via Google too if you want a look.

Matt

uno Communications
t: 0333 773 7700
Official Maidenhead, Milton Keynes & Sheffield Speedtest.net Host
Standard User 23Prince
(fountain of knowledge) Sun 23-Jul-17 17:52:41
Print Post

Re: Is ThinkBroad montor broken?


[re: amiga_dude] [link to this post]
 
In reply to a post by amiga_dude:
Little bit baffled about this. I have broadband montor that showing really bad ping.

https://www.thinkbroadband.com/broadband/monitoring/...

(Note the red is where I disconnected, also very long one about 14:00-15:00 [ish] is when I went out turn off my network when I went out.)

So then I sent out ping on My Windows 10 out to internet.

ping bbc.co.uk

Pinging bbc.co.uk [212.58.246.78] with 32 bytes of data:
Reply from 212.58.246.78: bytes=32 time=32ms TTL=53
Reply from 212.58.246.78: bytes=32 time=31ms TTL=53
Reply from 212.58.246.78: bytes=32 time=30ms TTL=53
Reply from 212.58.246.78: bytes=32 time=29ms TTL=53

Ping statistics for 212.58.246.78:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 29ms, Maximum = 32ms, Average = 30ms

C:\Users\Hairy>ping google.com

Pinging google.com [216.58.204.78] with 32 bytes of data:
Reply from 216.58.204.78: bytes=32 time=20ms TTL=51
Reply from 216.58.204.78: bytes=32 time=21ms TTL=51
Reply from 216.58.204.78: bytes=32 time=19ms TTL=51
Reply from 216.58.204.78: bytes=32 time=18ms TTL=51

Ping statistics for 216.58.204.78:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 18ms, Maximum = 21ms, Average = 19ms

C:\Users\Hairy>ping hotmail.com

Pinging hotmail.com [157.56.198.220] with 32 bytes of data:
Reply from 157.56.198.220: bytes=32 time=21ms TTL=239
Reply from 157.56.198.220: bytes=32 time=24ms TTL=239
Reply from 157.56.198.220: bytes=32 time=22ms TTL=239
Reply from 157.56.198.220: bytes=32 time=22ms TTL=239

Ping statistics for 157.56.198.220:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 21ms, Maximum = 24ms, Average = 22ms

C:\Users\Hairy>


That look alright so then I thought, I remote Raspberry Pi computer at family house so I ssh in to it and got it to ping me back.

ping 81.96.5*.*
PING 81.96.5*.* (81.96.5*.*) 56(84) bytes of data.
64 bytes from 81.96.5*.*: icmp_seq=1 ttl=57 time=24.5 ms
64 bytes from 81.96.5*.*: icmp_seq=2 ttl=57 time=33.0 ms
64 bytes from 81.96.5*.*: icmp_seq=3 ttl=57 time=25.8 ms
64 bytes from 81.96.5*.*: icmp_seq=4 ttl=57 time=34.1 ms
64 bytes from 81.96.5*.*: icmp_seq=5 ttl=57 time=26.4 ms
64 bytes from 81.96.5*.*: icmp_seq=6 ttl=57 time=24.6 ms
64 bytes from 81.96.5*.*: icmp_seq=7 ttl=57 time=24.5 ms
64 bytes from 81.96.5*.*: icmp_seq=8 ttl=57 time=48.1 ms
64 bytes from 81.96.5*.*: icmp_seq=9 ttl=57 time=26.4 ms
64 bytes from 81.96.5*.*: icmp_seq=10 ttl=57 time=26.2 ms
64 bytes from 81.96.5*.*: icmp_seq=11 ttl=57 time=23.1 ms
64 bytes from 81.96.5*.*: icmp_seq=12 ttl=57 time=23.7 ms
64 bytes from 81.96.5*.*: icmp_seq=13 ttl=57 time=25.5 ms
64 bytes from 81.96.5*.*: icmp_seq=14 ttl=57 time=28.1 ms
64 bytes from 81.96.5*.*: icmp_seq=15 ttl=57 time=27.1 ms
64 bytes from 81.96.5*.*: icmp_seq=16 ttl=57 time=30.3 ms
64 bytes from 81.96.5*.*: icmp_seq=17 ttl=57 time=26.8 ms
64 bytes from 81.96.5*.*: icmp_seq=18 ttl=57 time=24.8 ms
64 bytes from 81.96.5*.*: icmp_seq=19 ttl=57 time=21.3 ms
64 bytes from 81.96.5*.*: icmp_seq=20 ttl=57 time=26.4 ms
64 bytes from 81.96.5*.*: icmp_seq=21 ttl=57 time=24.5 ms
64 bytes from 81.96.5*.*: icmp_seq=22 ttl=57 time=26.9 ms
64 bytes from 81.96.5*.*: icmp_seq=23 ttl=57 time=23.8 ms
64 bytes from 81.96.5*.*: icmp_seq=24 ttl=57 time=25.0 ms
64 bytes from 81.96.5*.*: icmp_seq=25 ttl=57 time=25.8 ms
64 bytes from 81.96.5*.*: icmp_seq=26 ttl=57 time=24.4 ms
64 bytes from 81.96.5*.*: icmp_seq=27 ttl=57 time=25.9 ms
64 bytes from 81.96.5*.*: icmp_seq=28 ttl=57 time=33.6 ms
64 bytes from 81.96.5*.*: icmp_seq=29 ttl=57 time=26.7 ms
64 bytes from 81.96.5*.*: icmp_seq=30 ttl=57 time=32.7 ms
^C
--- 81.96.5*.* ping statistics ---
30 packets transmitted, 30 received, 0% packet loss, time 29050ms
rtt min/avg/max/mdev = 21.322/27.379/48.182/4.953 ms


That dosn't match the report I am getting from thinkbroadband monitor.


Leave the router turned on 24/7 as it's meant to be? Problem solved?
  Print Thread

Jump to