What’s going on with this BQM?

[Jon22]

Can someone help me figure out what’s going on with my BQM? Noticed since last Tuesday that some websites occasionally take a couple of clicks to load. They’d just hang and then click on the link again and it would load straight away. Thinking there might be some issue with the router, this led me to reinstalling the router software (once with Pfsense and again with Openwrt). The BQM has always been relatively flat, for a VM connection, since I joined last year. Since last night, I’ve had these blocks of yellow. They seem too flat and consistent to show congestion. Speeds are completely fine, near enough maxing out the line. I changed the WAN port to another one around 5:30pm ish. This seemed to drop the max latency for a bit, then it went back up. Ignore the red packet loss, that’s me doing things. I’ve done a reset using the button earlier on the hub.

Changed to router mode on the hub just before midnight. Disconnected the router and just left the connection idle with no devices connected for an hour. No change. I’m guessing it’s some issue between VM and Thinkbroadband. No idea what as if I run a traceroute, it looks normal.

My Broadband Ping

traceroute to pingbox1.thinkbroadband.com (80.249.99.164), 20 hops max, 46 byte packets
1 10.53.35.233 9.027 ms
2 82.2.246.81 10.747 ms
3 *
4 *
5 62.254.42.174 18.371 ms
6 *
7 84.116.135.50 15.721 ms
8 129.250.66.101 17.856 ms
9 129.250.3.214 17.983 ms
10 129.250.3.251 28.552 ms
11 192.80.16.146 15.428 ms
12 80.249.97.72 13.613 ms
13 80.249.97.90 14.463 ms
14 80.249.99.164 15.721 ms

A normal day for my connection:

My Broadband Ping

[legacy1]

I think VM can change more about how the upstream handles sending packets and thats what your seeing a change.

You could see what happens if get OBS and have a steady upload if that changes the look of BQM.

[Jon22]

Playing a game makes the graph “better”. Nowhere near as good as it was before whatever has changed. 

https://www.thinkbroadband.com/broadband/monitoring/quality/share/da7c3dab548184e1ff3d8f577cac2f53c0679d8a-13-04-2023

[Adduxi]

Interesting that Router mode and Modem mode show the exact same BQM trace, despite getting different WAN IP's.

Also your gaming periods seem very normal which just adds to the weirdness.  I'm assuming all is well with your network logs and power levels?

[Jon22]

Downstream bonded channels

Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID

1	339000000	5.1	40	QAM 256	26
2	139000000	7.8	42	QAM 256	1
3	147000000	7.6	42	QAM 256	2
4	155000000	7.5	42	QAM 256	3
5	163000000	7.3	41	QAM 256	4
6	171000000	7	41	QAM 256	5
7	179000000	7.2	41	QAM 256	6
8	187000000	7	41	QAM 256	7
9	195000000	7.2	41	QAM 256	8
10	203000000	6.9	41	QAM 256	9
11	211000000	7	41	QAM 256	10
12	219000000	6.7	41	QAM 256	11
13	227000000	6.6	41	QAM 256	12
14	235000000	6.3	41	QAM 256	13
15	243000000	6.2	41	QAM 256	14
16	251000000	6.2	41	QAM 256	15
17	259000000	6.1	41	QAM 256	16
18	267000000	6.1	41	QAM 256	17
19	275000000	6	41	QAM 256	18
20	283000000	6.1	41	QAM 256	19
21	291000000	6	41	QAM 256	20
22	299000000	6.1	41	QAM 256	21
23	307000000	5.8	41	QAM 256	22
24	315000000	5.7	41	QAM 256	23
25	323000000	5.3	41	QAM 256	24
26	331000000	5.4	41	QAM 256	25
27	347000000	5.2	41	QAM 256	27
28	355000000	4.9	41	QAM 256	28
29	363000000	5	41	QAM 256	29
30	371000000	5.1	41	QAM 256	30
31	379000000	5.2	41	QAM 256	31

Downstream bonded channels

Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors

1	Locked	40	2	0
2	Locked	42	5	0
3	Locked	42	6	0
4	Locked	42	11	0
5	Locked	41	5	0
6	Locked	41	7	0
7	Locked	41	1	0
8	Locked	41	3	0
9	Locked	41	2	0
10	Locked	41	2	0
11	Locked	41	2	0
12	Locked	41	3	0
13	Locked	41	1	0
14	Locked	41	17	0
15	Locked	41	95	0
16	Locked	41	3	0
17	Locked	41	1	0
18	Locked	41	52	0
19	Locked	41	0	0
20	Locked	41	36	0
21	Locked	41	3	0
22	Locked	41	3	0
23	Locked	41	4	0
24	Locked	41	25	0
25	Locked	41	17	0
26	Locked	41	3	0
27	Locked	41	1	0
28	Locked	41	2	0
29	Locked	41	1	0
30	Locked	41	2	0
31	Locked	41	2	0

Upstream bonded channels

Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID

0	49600000	46	5120	QAM 64	1
1	43100000	45.5	5120	QAM 64	2
2	36600000	45.5	5120	QAM 64	3
3	30100000	45	5120	QAM 64	4
4	23600000	44.8	5120	QAM 64	5

Upstream bonded channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts

0	ATDMA	0	0	0	0
1	ATDMA	0	0	0	0
2	ATDMA	0	0	0	0
3	ATDMA	0	0	0	0
4	ATDMA	0	0	0	0

Network Log

Time Priority Description

12-04-2023 00:52:26	warning	DBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
12-04-2023 00:52:26	notice	US profile assignment change. US Chan ID: 6; Previous Profile: 13; New Profile: 11 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
12-04-2023 00:52:23	notice	REGISTRATION COMPLETE - Waiting for Operational status
12-04-2023 00:52:17	warning	Dynamic Range Window violation
12-04-2023 00:52:17	warning	RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
12-04-2023 00:52:17	warning	RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
12-04-2023 00:52:17	warning	RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
12-04-2023 00:52:17	warning	REG-RSP-MP Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
12-04-2023 00:52:17	warning	Dynamic Range Window violation
12-04-2023 00:52:17	warning	Dynamic Range Window violation
12-04-2023 00:52:17	warning	RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
12-04-2023 00:52:17	warning	Dynamic Range Window violation
12-04-2023 00:52:17	warning	Dynamic Range Window violation
12-04-2023 00:52:17	warning	Dynamic Range Window violation
12-04-2023 00:52:17	warning	RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
12-04-2023 00:52:17	warning	RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
12-04-2023 00:52:12	notice	DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
12-04-2023 00:52:08	notice	TLV-11 - unrecognized OID;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
12-04-2023 00:52:06	warning	DHCP WARNING - Non-critical field invalid in response ;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
12-04-2023 00:52:04	notice	Honoring MDD; IP provisioning mode = IPv4
12-04-2023 00:51:55	critical	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
12-04-2023 00:51:38	critical	Cable Modem Reboot via RG reboot command
11-04-2023 23:57:49	critical	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
11-04-2023 23:57:36	critical	Cable Modem Reboot via RG reboot command
11-04-2023 17:40:08	critical	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
11-04-2023 17:39:52	critical	Cable Modem Reboot due to power button reset
11-04-2023 15:41:31	critical	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
11-04-2023 15:41:14	critical	Cable Modem Reboot via RG reboot command
11-04-2023 15:34:40	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
11-04-2023 15:34:39	critical	Ranging Request Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
11-04-2023 15:33:43	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
11-04-2023 15:33:40	critical	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;

[Jon22]

All the power levels look ok. Network log seems ok as well. Weirdly, the graph was back to normal between ~7:45-8:45am this morning. Then back to having these blocks of latency. 

[jpeg1]

---

@Adduxi wrote:

Interesting that Router mode and Modem mode show the exact same BQM trace, despite getting different WAN IP's.

Also your gaming periods seem very normal which just adds to the weirdness.  I'm assuming all is well with your network logs and power levels?

---

It looks very like your BQM is watching someone else's IP. 

[Jon22]

The BQM is monitoring the WAN IP that Openwrt is reporting, as well as other "What's my IP" sites 🙂

Couple of traceroutes for the IP addresses I can find for TBB's BQM.

Spoiler

Tracing route to pingbox1.thinkbroadband.com REMOVED
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms OpenWrt.lan [REMOVED
2 10 ms 9 ms 9 ms 10.53.35.233
3 9 ms 10 ms 9 ms wolv-core-2b-xe-1112-0.network.virginmedia.net [REMOVED
4 * * * Request timed out.
5 * * * Request timed out.
6 16 ms 17 ms 17 ms host-62-254-42.174.not-set-yet.virginmedia.net.42.254.62.in-addr.arpa [REMOVED
7 * * * Request timed out.
8 17 ms 17 ms 17 ms uk-lon01c-ri2-ae-6-0.aorta.net [REMOVED
9 21 ms 18 ms 17 ms ae-8.a02.londen12.uk.bb.gin.ntt.net [REMOVED]
10 17 ms 18 ms * ae-0.r20.londen12.uk.bb.gin.ntt.net REMOVED
11 * 20 ms 27 ms ae-13.a03.londen12.uk.bb.gin.ntt.net [REMOVED
12 17 ms 18 ms 17 ms REMOVED
13 17 ms 18 ms 19 ms te1-51-36.core-rs3.thdo.ncuk.net REMOVED
14 18 ms 19 ms 18 ms po5-32.core-rs4.thdo.ncuk.net 
15 18 ms 19 ms 17 ms pingbox1.thinkbroadband.com [

Spoiler

Tracing route to ip99-171.thdo.ncuk.net REMOVED
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms OpenWrt.lan [REMOVED
2 9 ms 9 ms 9 ms 10.53.35.233
3 9 ms 9 ms 10 ms wolv-core-2a-xe-1112-0.network.virginmedia.net [82.2.246.45]
4 * * * Request timed out.
5 19 ms 19 ms 19 ms 86.85-254-62.static.virginmediabusiness.co.uk [REMOVED
6 22 ms 21 ms 19 ms ae-8.a02.londen12.uk.bb.gin.ntt.net [
7 16 ms 40 ms 14 ms ae-0.r21.londen12.uk.bb.gin.ntt.net [
8 19 ms 23 ms 19 ms ae-1.a03.londen12.uk.bb.gin.ntt.net [
9 19 ms 20 ms 32 ms 192.80.16.146
10 20 ms 21 ms 19 ms te1-51-36.core-rs3.thdo.ncuk.net [
11 20 ms 20 ms 18 ms po5-32.core-rs4.thdo.ncuk.net [
12 20 ms 20 ms 19 ms ip99-171.thdo.ncuk.net [

[MOD EDIT: Personal and private information has been removed from this post. Please do not post personal or private information in your public posts. Please review the Forum Guidelines]

[IPFreely]

So moderators apparently now think IP addresses in a traceroute are personal / private information and have warned Jon for copy/pasting it.

So everyone else no IP addresses, at all, allowed.

Moderator didn't even manage to redact all the IP addresses. Laughable. 

[Jon22]

Haha, I hadn’t even noticed that. Traces didn’t even have the WAN IP in them.