Constant ping jitter, high MS and unstable connection

[wordup]

I've always had a somewhat dubious connection provided by you but in the past couple of months the frequency and intensity of ping jitter has gone through the roof, making it borderline unusable for a lot of important things I use it for in "peak" hours. This is getting to the stage where we've already inquired about alternative providers, and if this can't be solved then I'll be moving forward with it ASAP. Have months of graphs on this, can provide more on request

Live Graph:

https://www.thinkbroadband.com/broadband/monitoring/quality/share/a22811a5279790752e5fe8422773317d9b791390

Snapshot of Yesterday:

https://www.thinkbroadband.com/broadband/monitoring/quality/share/9130433dc92158300e4a161ff0aabd7b9458f9ed-11-12-2024

"Peak" hour experience (Sunday):

https://www.thinkbroadband.com/broadband/monitoring/quality/share/a22811a5279790752e5fe8422773317d9b791390

[wordup]

Apologies, this is the link for Sunday, doubled up on the live graph by mistake:

https://www.thinkbroadband.com/broadband/monitoring/quality/share/4dcc26187066a8d2fe22f5586bfce5b8184e0edd-08-12-2024

[Client62]

I just looked at the live BQM.  

What happened between 1am and 8:30am this morning, why is the BQM all red ?

[wordup]

Genuinely couldn't tell you, the connection is still active (though still up/down in stability), though in some cases it reaches a point where it fully disconnects during a spike and comes back a little while later, unsure if that would cause it to fully sever the BQM packets from being sent. There's a few more instances of it happening in the past week.

For reference the connection went from *relatively* stable around 12-1pm as shown, and at 1-1:15pm yesterday it went haywire for the remainder of the day, stopping only around 2am. Symptoms are extremely unstable rocketing MS usually between 5-2000 for 1-2 seconds, then back down, repeating every 5 seconds or so. No registered packet loss from the software I'm live monitoring it on my end with though, purely latency.

[Client62]

The BQM being all red is very important, that needs to be understood.

It has a couple of explanations ...

1) Either your VM Hub was turned off during that period.

2) Or the BQM does not point to the Public IP of your VM Hub connection,
    it points to a device that has been off-line from 1am.

[jpeg1]

Yes the BQM is now looking at a different WAN IP.  But that's not relevant to the ongoing problem which on first look appears to be due to local oversubscription.

To eliminate your own connection we need to see the Hub data. 

[wordup]

If it's the network log error checks, the following is in the router:

13/12/2024 12:21:56	notice	DHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt062-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
13/12/2024 12:21:56	Error	DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
11/12/2024 15:55:10	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
10/12/2024 00:21:55	notice	DHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt062-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
10/12/2024 00:21:55	Error	DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
08/12/2024 21:05:33	critical	TLV-11 - Failed to set duplicate elements;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
08/12/2024 00:36:4	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
06/12/2024 12:21:55	notice	DHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt062-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
06/12/2024 12:21:55	Error	DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
05/12/2024 00:35:56	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
03/12/2024 00:21:55	notice	DHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt062-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
03/12/2024 00:21:54	Error	DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
30/11/2024 02:55:3	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
29/11/2024 12:21:56	notice	DHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt062-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
29/11/2024 12:21:56	Error	DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
26/11/2024 07:07:38	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
26/11/2024 00:21:50	notice	DHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt062-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
26/11/2024 00:21:50	Error	DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
22/11/2024 17:33:49	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

[jpeg1]

We need the downstream and upstream data.