For the past week ive been getting persistent little spikes in packet loss and I am noticing it ingame.Is there currently an issue in my area, no point in calling up as I never get anywhere and now the tech support has business hours so if my internet went completely off after 5pm there is nobody to call.

Just wanted to update, looking a LOT better now in regards to the constant red dips at top and upstream channels for the moment are all on QAM64 which I have not seen in quite a while.All it took was someone to make someone look at something other than my end.EDITNot sure why but these new forums can't click for bigger image any more and can't drag image to open in new window.

Can't edit additional post but this is today

Yes, VM are making it hard for customers to complain. It costs them money to listen to our problems.Log onto your Hub. Copy and paste here (as text not screenshots) all the upstream and downstream data and the network log.

Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID253310000003.940.9QAM2562511390000004.839QAM256121470000005.139QAM256231550000005.539QAM256341630000005.238.6QAM256451710000004.740.4QAM256561790000004.640.4QAM256671870000004.840.9QAM256781950000004.540.4QAM256892030000004.140.9QAM2569102110000004.338.6QAM25610112190000004.540.4QAM25611122270000005.140.4QAM2561213235000000540.4QAM25613142430000005.140.9QAM25614152510000005.239QAM25615162590000005.640.4QAM25616172670000004.839QAM25617182750000003.740.4QAM25618192830000003.740.4QAM25619202910000004.540.4QAM25620212990000004.840.9QAM25621223070000004.240.4QAM25622233150000003.840.4QAM25623243230000003.640.4QAM25624263390000003.640.4QAM25626273470000003.440.4QAM25627283550000003.840.4QAM25628293630000003.940.4QAM25629303710000003.639QAM25630313790000002.940.4QAM256313.0 Upstream channelsChannel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID13660000040.85120 KSym/secQAM64323010000040.35120 KSym/secQAM64432360000040.35120 KSym/secQAM645443100000415120 KSym/secQAM642549600000415120 KSym/secQAM641

The 1970 entry is when I power cycled the superhub to see if that sorted anythingNetwork LogTime Priority DescriptionSun 24/03/202408:40:166US profile assignment change. US Chan ID: 6; Previous Profile: 12; New Profile: 11.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;Sun 24/03/202404:29:216CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;Sat 23/03/202418:15:046US profile assignment change. US Chan ID: 6; Previous Profile: 11; New Profile: 12.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;Sat 23/03/202418:11:453No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;Sat 23/03/202415:10:056US profile assignment change. US Chan ID: 6; Previous Profile: 11; New Profile: 12.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;Sat 23/03/202414:59:326CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;Sat 23/03/202400:04:376US profile assignment change. US Chan ID: 6; Previous Profile: 12; New Profile: 11.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;Sat 23/03/202400:01:273No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;Fri 22/03/202411:30:216US profile assignment change. US Chan ID: 6; Previous Profile: 11; New Profile: 12.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;Fri 22/03/202400:46:566CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;Thu 21/03/202421:29:246US profile assignment change. US Chan ID: 6; Previous Profile: 12; New Profile: 11.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;Thu 21/03/202420:48:113No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;Thu 21/03/202412:01:316US profile assignment change. US Chan ID: 6; Previous Profile: 12; New Profile: 11.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;Thu 21/03/202411:53:415MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;Thu 01/01/197000:01:223No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;Thu 01/01/197000:01:213Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;Thu 21/03/202409:18:106US profile assignment change. US Chan ID: 6; Previous Profile: 11; New Profile: 12.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;Thu 21/03/202408:46:523No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;Wed 20/03/202419:24:366US profile assignment change. US Chan ID: 6; Previous Profile: 12; New Profile: 11.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;Wed 20/03/202419:14:084DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;Wed 20/03/202418:34:316US profile assignment change. US Chan ID: 6; Previous Profile: 12; New Profile: 11.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;Wed 20/03/202416:22:406CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;Wed 20/03/202401:07:433No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;Tue 19/03/202423:45:456CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;Tue 19/03/202421:06:593No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;Tue 19/03/202420:25:236US profile assignment change. US Chan ID: 6; Previous Profile: 12; New Profile: 11.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;Tue 19/03/202416:05:183No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;Tue 19/03/202412:57:336CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;Tue 19/03/202400:19:023No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;Mon 18/03/202421:11:146CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;Mon 18/03/202420:04:283No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;Mon 18/03/202402:54:236CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;Sun 17/03/202419:31:013No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;Sun 17/03/202407:14:084DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;Sun 17/03/202400:19:336CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;Sat 16/03/202415:34:303No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;Sat 16/03/202400:22:096CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;Thu 14/03/202410:41:343No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;Thu 14/03/202401:50:396CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;Wed 13/03/202419:14:084DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;Wed 13/03/202412:07:353No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;Mon 11/03/202406:32:436CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;Sun 10/03/202416:26:193No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;Sun 10/03/202407:14:084DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;Sat 09/03/202417:51:463No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;Sat 09/03/202417:10:276CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;Sat 09/03/202407:12:493No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;Sat 09/03/202405:04:086CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;Sat 09/03/202400:15:093No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;Fri 08/03/202422:26:446US profile assignment change. US Chan ID: 6; Previous Profile: 12; New Profile: 11.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;

Constant small packet loss dips in SS2 | Virgin Media Community

79 Replies

Replies have been turned off for this discussion

alphaomega16
Up to speed
1 year ago
Can't edit additional post but this is today
jpeg1
Alessandro Volta
1 year ago
Yes, VM are making it hard for customers to complain. It costs them money to listen to our problems.
Log onto your Hub. Copy and paste here (as text not screenshots) all the upstream and downstream data and the network log.

alphaomega16

Up to speed

1 year ago

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

25	331000000	3.9	40.9	QAM256	25
1	139000000	4.8	39	QAM256	1
2	147000000	5.1	39	QAM256	2
3	155000000	5.5	39	QAM256	3
4	163000000	5.2	38.6	QAM256	4
5	171000000	4.7	40.4	QAM256	5
6	179000000	4.6	40.4	QAM256	6
7	187000000	4.8	40.9	QAM256	7
8	195000000	4.5	40.4	QAM256	8
9	203000000	4.1	40.9	QAM256	9
10	211000000	4.3	38.6	QAM256	10
11	219000000	4.5	40.4	QAM256	11
12	227000000	5.1	40.4	QAM256	12
13	235000000	5	40.4	QAM256	13
14	243000000	5.1	40.9	QAM256	14
15	251000000	5.2	39	QAM256	15
16	259000000	5.6	40.4	QAM256	16
17	267000000	4.8	39	QAM256	17
18	275000000	3.7	40.4	QAM256	18
19	283000000	3.7	40.4	QAM256	19
20	291000000	4.5	40.4	QAM256	20
21	299000000	4.8	40.9	QAM256	21
22	307000000	4.2	40.4	QAM256	22
23	315000000	3.8	40.4	QAM256	23
24	323000000	3.6	40.4	QAM256	24
26	339000000	3.6	40.4	QAM256	26
27	347000000	3.4	40.4	QAM256	27
28	355000000	3.8	40.4	QAM256	28
29	363000000	3.9	40.4	QAM256	29
30	371000000	3.6	39	QAM256	30
31	379000000	2.9	40.4	QAM256	31

3.0 Upstream channels

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

1	36600000	40.8	5120 KSym/sec	QAM64	3
2	30100000	40.3	5120 KSym/sec	QAM64	4
3	23600000	40.3	5120 KSym/sec	QAM64	5
4	43100000	41	5120 KSym/sec	QAM64	2
5	49600000	41	5120 KSym/sec	QAM64	1

alphaomega16

Up to speed

1 year ago

The 1970 entry is when I power cycled the superhub to see if that sorted anything

Network Log

Time Priority Description

Sun 24/03/2024 08:40:16	6	US profile assignment change. US Chan ID: 6; Previous Profile: 12; New Profile: 11.;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
Sun 24/03/2024 04:29:21	6	CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
Sat 23/03/2024 18:15:04	6	US profile assignment change. US Chan ID: 6; Previous Profile: 11; New Profile: 12.;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
Sat 23/03/2024 18:11:45	3	No Ranging Response received - T3 time-out;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
Sat 23/03/2024 15:10:05	6	US profile assignment change. US Chan ID: 6; Previous Profile: 11; New Profile: 12.;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
Sat 23/03/2024 14:59:32	6	CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
Sat 23/03/2024 00:04:37	6	US profile assignment change. US Chan ID: 6; Previous Profile: 12; New Profile: 11.;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
Sat 23/03/2024 00:01:27	3	No Ranging Response received - T3 time-out;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
Fri 22/03/2024 11:30:21	6	US profile assignment change. US Chan ID: 6; Previous Profile: 11; New Profile: 12.;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
Fri 22/03/2024 00:46:56	6	CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
Thu 21/03/2024 21:29:24	6	US profile assignment change. US Chan ID: 6; Previous Profile: 12; New Profile: 11.;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
Thu 21/03/2024 20:48:11	3	No Ranging Response received - T3 time-out;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
Thu 21/03/2024 12:01:31	6	US profile assignment change. US Chan ID: 6; Previous Profile: 12; New Profile: 11.;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
Thu 21/03/2024 11:53:41	5	MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
Thu 01/01/1970 00:01:22	3	No Ranging Response received - T3 time-out;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
Thu 01/01/1970 00:01:21	3	Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
Thu 21/03/2024 09:18:10	6	US profile assignment change. US Chan ID: 6; Previous Profile: 11; New Profile: 12.;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
Thu 21/03/2024 08:46:52	3	No Ranging Response received - T3 time-out;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
Wed 20/03/2024 19:24:36	6	US profile assignment change. US Chan ID: 6; Previous Profile: 12; New Profile: 11.;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
Wed 20/03/2024 19:14:08	4	DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
Wed 20/03/2024 18:34:31	6	US profile assignment change. US Chan ID: 6; Previous Profile: 12; New Profile: 11.;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
Wed 20/03/2024 16:22:40	6	CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1.;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
Wed 20/03/2024 01:07:43	3	No Ranging Response received - T3 time-out;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
Tue 19/03/2024 23:45:45	6	CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1.;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
Tue 19/03/2024 21:06:59	3	No Ranging Response received - T3 time-out;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
Tue 19/03/2024 20:25:23	6	US profile assignment change. US Chan ID: 6; Previous Profile: 12; New Profile: 11.;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
Tue 19/03/2024 16:05:18	3	No Ranging Response received - T3 time-out;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
Tue 19/03/2024 12:57:33	6	CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1.;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
Tue 19/03/2024 00:19:02	3	No Ranging Response received - T3 time-out;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
Mon 18/03/2024 21:11:14	6	CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
Mon 18/03/2024 20:04:28	3	No Ranging Response received - T3 time-out;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
Mon 18/03/2024 02:54:23	6	CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
Sun 17/03/2024 19:31:01	3	No Ranging Response received - T3 time-out;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
Sun 17/03/2024 07:14:08	4	DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
Sun 17/03/2024 00:19:33	6	CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
Sat 16/03/2024 15:34:30	3	No Ranging Response received - T3 time-out;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
Sat 16/03/2024 00:22:09	6	CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
Thu 14/03/2024 10:41:34	3	No Ranging Response received - T3 time-out;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
Thu 14/03/2024 01:50:39	6	CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
Wed 13/03/2024 19:14:08	4	DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
Wed 13/03/2024 12:07:35	3	No Ranging Response received - T3 time-out;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
Mon 11/03/2024 06:32:43	6	CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
Sun 10/03/2024 16:26:19	3	No Ranging Response received - T3 time-out;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
Sun 10/03/2024 07:14:08	4	DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
Sat 09/03/2024 17:51:46	3	No Ranging Response received - T3 time-out;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
Sat 09/03/2024 17:10:27	6	CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
Sat 09/03/2024 07:12:49	3	No Ranging Response received - T3 time-out;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
Sat 09/03/2024 05:04:08	6	CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
Sat 09/03/2024 00:15:09	3	No Ranging Response received - T3 time-out;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
Fri 08/03/2024 22:26:44	6	US profile assignment change. US Chan ID: 6; Previous Profile: 12; New Profile: 11.;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;

Ashleigh_C
Forum Team (Retired)
1 year ago
Hi there alphaomega16

Thank you so much for your post and welcome back to the forums, it's great to have you here.

I am so sorry that you have faced this issue with your service and thank you for sharing the BQM and Hub status. I have checked on our side and cannot see any issues that could be causing this.

How have things been looking since your last post?

alphaomega16
Up to speed
1 year ago
Seems to have cleared up today, for how long I don't know.
alphaomega16
Up to speed
1 year ago
Not sure what happened overnight with the doorstep jump and drop and then after, hoping that was the end of it.
- Carley_S
  Forum Team (Retired)
  1 year ago
  Sorry to hear there was a drop in service that night alphaomega16
  
  Checking the systems at our side, there is nothing currently that I can see that is causing any issues. Hubs specs all look good and nothing flagged in the area.
  
  This packet loss might have been a hub update during the night, but please do keep us posted should you see anything else concerning on your BQM and we can investigate further.
alphaomega16
Up to speed
1 year ago
Its happening again
- RT123
  Up to speed
  1 year ago
  Hi,
  
  Could you please share the router logs again?
alphaomega16
Up to speed
1 year ago
alphaomega16
Up to speed
1 year ago
It wont let me post the logs, im pressing reply but nothing is happening when I paste the info, when I do get it to post please keep in mind that a hub update stopped any errors showing in upload/download window on logs.

alphaomega16

Up to speed

1 year ago

3.0 Downstream channels

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

25	331000000	3.8	39	QAM256	25
1	139000000	4.7	38.6	QAM256	1
2	147000000	5.1	38.6	QAM256	2
3	155000000	5.4	38.6	QAM256	3
4	163000000	5.1	38.6	QAM256	4
5	171000000	4.6	38.6	QAM256	5
6	179000000	4.5	38.6	QAM256	6
7	187000000	4.7	39	QAM256	7
8	195000000	4.4	39	QAM256	8
9	203000000	4.1	39	QAM256	9
10	211000000	4.3	39	QAM256	10
11	219000000	4.5	38.6	QAM256	11
12	227000000	5.1	39	QAM256	12
13	235000000	5.1	39	QAM256	13
14	243000000	4.9	38.6	QAM256	14
15	251000000	5.1	38.6	QAM256	15
16	259000000	5.4	38.6	QAM256	16
17	267000000	4.7	39	QAM256	17
18	275000000	3.6	38.6	QAM256	18
19	283000000	3.7	39	QAM256	19
20	291000000	4.4	39	QAM256	20
21	299000000	4.6	39	QAM256	21
22	307000000	4.2	39	QAM256	22
23	315000000	3.8	39	QAM256	23
24	323000000	3.5	39	QAM256	24
26	339000000	3.5	39	QAM256	26
27	347000000	3.3	39	QAM256	27
28	355000000	3.7	39	QAM256	28
29	363000000	3.8	38.6	QAM256	29
30	371000000	3.4	38.6	QAM256	30
31	379000000	2.9	39	QAM256	31

3.0 Downstream channels

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

25	Locked	38.983261
1	Locked	38.605377
2	Locked	38.605377
3	Locked	38.605377
4	Locked	38.605377
5	Locked	38.605377
6	Locked	38.605377
7	Locked	38.983261
8	Locked	38.983261
9	Locked	38.983261
10	Locked	38.983261
11	Locked	38.605377
12	Locked	38.983261
13	Locked	38.983261
14	Locked	38.605377
15	Locked	38.605377
16	Locked	38.605377
17	Locked	38.983261
18	Locked	38.605377
19	Locked	38.983261
20	Locked	38.983261
21	Locked	38.983261
22	Locked	38.983261
23	Locked	38.983261
24	Locked	38.983261
26	Locked	38.983261
27	Locked	38.983261
28	Locked	38.983261
29	Locked	38.605377
30	Locked	38.605377
31	Locked	38.983261

Forum Discussion

Constant small packet loss dips in SS2

79 Replies

3.0 Upstream channels

The 1970 entry is when I power cycled the superhub to see if that sorted anything

Network Log

3.0 Downstream channels

3.0 Downstream channels

Related Content

Constant drop outs and total packet loss

Constant calls from 0800 052 8675

Packet loss issue?

Packet Loss

Constant us profile assignment change