Starting to see increased latency and noise, part 2.

[rs888]

Hi all.

Basically had the same issue back in July 2021. Gig1/Hub4 in modem mode at the moment.

Last years thread for reference: https://community.virginmedia.com/t5/Forum-Archive/Starting-to-see-increased-latency-and-noise/td-p/...

Only now it seems to be compounded by national upgrades on the lower tiers without upgrading the network in all areas. Typical VM MO.

BQM:

Logs 1:

Cable Modem StatusItem Status CommentsChannel Overview Downstream Upstream

Cable Modem Status	Online	DOCSIS 3.1
Primary downstream channel	Locked	SC-QAM
DOCSIS 3.0 channels	31	4
DOCSIS 3.1 channels	1	0

 

[rs888]

Logs 2:

3.0 Downstream channels
Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
25 331000000 6.699997 40.366287 QAM256 25
1 139000000 6.699997 40.946209 QAM256 1
2 147000000 6.000000 40.946209 QAM256 2
3 155000000 5.699997 40.946209 QAM256 3
4 163000000 5.900002 40.366287 QAM256 4
5 171000000 5.699997 40.946209 QAM256 5
6 179000000 5.599998 40.946209 QAM256 6
7 187000000 5.500000 40.946209 QAM256 7
8 195000000 5.400002 40.946209 QAM256 8
9 203000000 5.199997 40.366287 QAM256 9
10 211000000 5.000000 40.366287 QAM256 10
11 219000000 4.699997 40.366287 QAM256 11
12 227000000 4.400002 40.366287 QAM256 12
13 235000000 4.099998 40.366287 QAM256 13
14 243000000 4.599998 40.946209 QAM256 14
15 251000000 5.000000 40.946209 QAM256 15
16 259000000 5.500000 40.366287 QAM256 16
17 267000000 5.699997 40.366287 QAM256 17
18 275000000 5.800003 40.366287 QAM256 18
19 283000000 5.599998 40.946209 QAM256 19
20 291000000 5.699997 40.366287 QAM256 20
21 299000000 5.599998 40.366287 QAM256 21
22 307000000 6.000000 40.366287 QAM256 22
23 315000000 6.300003 40.366287 QAM256 23
24 323000000 6.800003 40.366287 QAM256 24
26 339000000 6.699997 40.366287 QAM256 26
27 347000000 6.500000 40.946209 QAM256 27
28 355000000 6.300003 40.366287 QAM256 28
29 363000000 6.099998 40.946209 QAM256 29
30 371000000 5.900002 40.366287 QAM256 30
31 379000000 5.900002 40.366287 QAM256 31


3.0 Downstream channels
Channel Lock Status RxMER (dB) Pre RS Errors Post RS Errors
25 Locked 40.366287 0 0
1 Locked 40.946209 0 0
2 Locked 40.946209 6 0
3 Locked 40.946209 0 0
4 Locked 40.366287 0 0
5 Locked 40.946209 0 0
6 Locked 40.946209 12 0
7 Locked 40.946209 1 0
8 Locked 40.946209 0 0
9 Locked 40.366287 0 0
10 Locked 40.366287 9 0
11 Locked 40.366287 0 0
12 Locked 40.366287 0 0
13 Locked 40.366287 0 0
14 Locked 40.946209 0 0
15 Locked 40.946209 0 0
16 Locked 40.366287 0 0
17 Locked 40.366287 994135 0
18 Locked 40.366287 0 0
19 Locked 40.946209 0 0
20 Locked 40.366287 0 0
21 Locked 40.366287 0 0
22 Locked 40.366287 0 0
23 Locked 40.366287 0 0
24 Locked 40.366287 0 0
26 Locked 40.366287 0 0
27 Locked 40.946209 0 0
28 Locked 40.366287 0 0
29 Locked 40.946209 0 0
30 Locked 40.366287 0 0
31 Locked 40.366287 0 0


3.1 Downstream channels
Channel Channel Width (MHz) FFT Type Number of Active Subcarriers Modulation (Active Profile) First Active Subcarrier (Hz)
159 96 4K 1880 QAM4096 759


3.1 Downstream channels
Channel ID Lock Status RxMER Data (dB) PLC Power (dBmV) Correcteds (Active Profile) Uncorrectables (Active Profile)
159 Locked 43 6.4 2584012675 0

[rs888]

Logs 3:

3.0 Upstream channels
Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
1 60300000 47.020599 5120 KSym/sec 64QAM 1
2 39400000 45.270599 5120 KSym/sec 64QAM 4
3 46200000 45.770599 5120 KSym/sec 64QAM 3
4 53700000 46.270599 5120 KSym/sec 64QAM 2


3.0 Upstream channels
Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts
1 US_TYPE_STDMA 0 0 0 0
2 US_TYPE_STDMA 0 0 0 0
3 US_TYPE_STDMA 0 0 0 0
4 US_TYPE_STDMA 0 0 2 0

Network Log
Time Priority Description
Fri Sep 9 18:15:01 2022 4 DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri Sep 9 18:15:01 2022 6 DHCP Renew - lease parameters tftp file-cmreg-vmdg640-bbt076-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat Sep 10 00:12:19 2022 6 CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue Sep 13 06:15:01 2022 4 DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue Sep 13 06:15:02 2022 6 DHCP Renew - lease parameters tftp file-cmreg-vmdg640-bbt076-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed Sep 14 23:37:11 2022 3 No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri Sep 16 18:15:02 2022 4 DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri Sep 16 18:15:02 2022 6 DHCP Renew - lease parameters tftp file-cmreg-vmdg640-bbt076-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue Sep 20 06:15:02 2022 4 DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue Sep 20 06:15:02 2022 6 DHCP Renew - lease parameters tftp file-cmreg-vmdg640-bbt076-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed Sep 21 21:19:34 2022 3 No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri Sep 23 14:39:30 2022 5 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri Sep 23 14:50:47 2022 5 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;
Fri Sep 23 14:53:16 2022 5 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri Sep 23 15:04:32 2022 5 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;
Sun Sep 25 10:34:17 2022 4 DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun Sep 25 10:34:18 2022 6 DHCP Renew - lease parameters tftp file-cmreg-vmdg640-bbt076-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun Sep 25 10:35:47 2022 3 No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed Sep 28 02:54:56 2022 4 DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed Sep 28 02:54:56 2022 6 DHCP Renew - lease parameters tftp file-cmreg-vmdg640-bbt076-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu Sep 29 08:31:25 2022 3 No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat Oct 1 14:54:56 2022 4 DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat Oct 1 14:54:56 2022 6 DHCP Renew - lease parameters tftp file-cmreg-vmdg640-bbt076-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun Oct 2 20:25:20 2022 3 No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed Oct 5 02:54:56 2022 4 DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed Oct 5 02:54:56 2022 6 DHCP Renew - lease parameters tftp file-cmreg-vmdg640-bbt076-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat Oct 8 14:54:56 2022 4 DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat Oct 8 14:54:56 2022 6 DHCP Renew - lease parameters tftp file-cmreg-vmdg640-bbt076-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed Oct 12 02:54:56 2022 4 DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed Oct 12 02:54:57 2022 6 DHCP Renew - lease parameters tftp file-cmreg-vmdg640-bbt076-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri Oct 14 03:09:57 2022 3 No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat Oct 15 14:54:57 2022 4 DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat Oct 15 14:54:57 2022 6 DHCP Renew - lease parameters tftp file-cmreg-vmdg640-bbt076-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon Oct 17 14:00:38 2022 3 No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed Oct 19 02:54:57 2022 4 DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed Oct 19 02:54:57 2022 6 DHCP Renew - lease parameters tftp file-cmreg-vmdg640-bbt076-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat Oct 22 14:54:57 2022 4 DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat Oct 22 14:54:57 2022 6 DHCP Renew - lease parameters tftp file-cmreg-vmdg640-bbt076-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;

[Chris_W1]

Hi rs888, thanks for the message and sorry to hear that you are having issues with the broadband.

Welcome back to the forums. 

I will send you a private message so that this can be looked into further. 

Kind regards, Chris. 

[legacy1]

Do you know if your connection was idle when getting the spikes?

[rs888]

As idle as it could be, just phones doing automated stuff and a single radio stream before 6pm. After 6pm that day no heavy transfers, just gaming and streaming.

The noise was in the streetcab last year, when the drop was moved to a different tap so did the noise from 275 to 267MHz which to me suggests a problem with the cab.

[rs888]

Well had a tech visit yesterday, he replaced my hub4 with another hub4.🙄

The noise issue seems to have gone away for now, he change something in the cab as well, so possible faulty hub.

Latency is still bad though.

[Matthew_ML]

Hey rs888, thank you for reaching out and I am sorry you are still having some connection issues.

I taken a look from my end and I can see there is an SNR outage currently in your local area which is lasting until the 21st November till 12:45.

This will cause performance issues like this unfortunately.  Thanks 

[rs888]

Thanks for the update Matt, there has not been any information regarding this SNR issue on the status page or phone service.

[Ayisha_B]

Hi 👋 @rs888,

It may not be on the Service Status as it is possible the outage is not impacting everyone in the area. Our engineers will be doing everything they can to have the issue resolved for you.

Thanks