Constant small packet loss dips in SS2

[alphaomega16]

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.

[Kath_P]

Thanks for coming back to us on this one alphaomega16.

Re-running checks here, everything is spot on. Power and signal levels on both the upstream are downstream are optimal, there is nothing to suggest utilisation or an area fault and all network tests are coming back good too. 

The only other option we can do now is look to book an engineer however if:

• ➡ The technician diagnoses the faults as not being caused by our network/equipment 
• ➡ The technician discovers that the fault or problem relates to your equipment
• ➡ The technician discovers that the fault or problem relates to any system that we are not responsible for

Then a call out charge of £25 will be added to your next bill. The technician would confirm during their visit if any of these instances apply.

Let me know if you're happy to proceed and we can then look to book the visit for you. 

Thanks, 

[alphaomega16]

• ➡ The technician discovers that the fault or problem relates to your equipment

How can it be my equipment?  TBB doesn't go past the modem, nothing connected to it should be able to cause this intermittent issue that keeps cropping up.

Already had someone out to no avail, id rather wait til contract is up and jump ship than risk getting billed £25 for an unresolvable issue.

[Steven_L]

Thanks for coming back to us alphaomega16. If you're not happy for another visit due to possible charges that could be available we won't go any further with arranging the visit.

Kind Regards,

Steven_L

[alphaomega16]

Restarted teh hub a few days ago but still same issue but I logged in to check info to see an issue with one of the upstream channels but ill post them all here.

3.0 Downstream channels

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

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

3.0 Downstream channels

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

1	Locked	38.605377	0	0
2	Locked	38.983261	0	0
3	Locked	38.983261	0	0
4	Locked	38.983261	0	0
5	Locked	40.946209	0	0
6	Locked	40.366287	0	0
7	Locked	40.366287	0	0
8	Locked	40.366287	0	0
9	Locked	40.366287	0	0
10	Locked	40.366287	0	0
11	Locked	40.946209	0	0
12	Locked	40.946209	0	0
13	Locked	40.366287	0	0
14	Locked	40.366287	0	0
15	Locked	38.983261	0	0
16	Locked	40.366287	0	0
17	Locked	40.366287	0	0
18	Locked	40.366287	0	0
20	Locked	40.946209	0	0
21	Locked	40.946209	0	0
22	Locked	40.366287	0	0
23	Locked	40.366287	0	0
24	Locked	40.366287	0	0
25	Locked	40.366287	0	0
26	Locked	40.366287	0	0
27	Locked	40.366287	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
32	Locked	38.983261	0	0

3.1 Downstream channels

Channel Channel Width (MHz) FFT Type Number of Active Subcarriers Modulation (Active Profile) First Active Subcarrier (Hz)

33

96

4K

1840

QAM4096

759

3.1 Downstream channels

Channel ID Lock Status RxMER Data (dB) PLC Power (dBmV) Correcteds (Active Profile) Uncorrectables (Active Profile)

33

Locked

39

-2.2

2013634996

1225

[alphaomega16]

• • Home
  • Connected devices
  • Modem mode
  • Advanced settings
    • Wireless
    • Security
    • DHCP
    • UPnP
    • Tools
      • Network status
      • Ping
      • Traceroute
      • MTU size
    • Light ring
  • Admin

  Network status

  Router status

  • Status
  • Downstream
  • Upstream
  • Configuration
  • Networklog

  Refresh data

  3.0 Upstream channels

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

  1	43100000	40.5	5120 KSym/sec	QAM64	2
  2	36600000	40.5	5120 KSym/sec	QAM64	3
  3	23600000	40	5120 KSym/sec	QAM16	5
  4	30100000	40	5120 KSym/sec	QAM64	4
  5	49600000	40.8	5120 KSym/sec	QAM64	1

  
  
  

  3.0 Upstream channels

  Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts

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

  
  
  

  3.1 Upstream channels

  Channel Channel Width (MHz) Power (dBmV) FFT Type Modulation

  6

  10.4

  44.9

  2K

  QAM32

  
  
  

  3.1 Upstream channels

  Channel Channel Type Number of Active Subcarriers First Active Subcarrier (Hz) T3 Timeouts T4 Timeouts

  6

  OFDMA

  208

  53.4

  0

  0

[alphaomega16]

Time Priority Description

Mon 06/01/2025 11:23:27	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;
Mon 06/01/2025 11:22:55	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 06/01/2025 10:37:48	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;
Mon 06/01/2025 10:32:51	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 06/01/2025 09:55:17	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;
Mon 06/01/2025 09:43:30	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 06/01/2025 08:13:11	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;
Mon 06/01/2025 08:03:12	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 06/01/2025 06:28: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;
Mon 06/01/2025 06:23:53	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 06/01/2025 05:48:15	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;
Mon 06/01/2025 05:33:57	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 06/01/2025 05:17:22	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;
Mon 06/01/2025 04:44:20	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 06/01/2025 01:59:32	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;
Mon 06/01/2025 01:58:16	3	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 06/01/2025 01:28:20	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;
Mon 06/01/2025 01:24:30	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 05/01/2025 23:51:39	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;
Sun 05/01/2025 23:48:57	4	DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun 05/01/2025 22:10:38	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;
Sun 05/01/2025 22:05:25	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 05/01/2025 20:32:19	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 05/01/2025 20:25:36	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;
Sun 05/01/2025 19:39:56	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 05/01/2025 19:35:42	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 05/01/2025 19:02:39	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 05/01/2025 18:46:18	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 05/01/2025 18:33:50	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;
Sun 05/01/2025 17:56:16	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 05/01/2025 17:36:44	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;
Sun 05/01/2025 17:06:21	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 05/01/2025 12:14:58	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;
Sun 05/01/2025 12:07:04	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 05/01/2025 11:18:43	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;
Sun 05/01/2025 11:17:29	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 05/01/2025 10:43:46	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 05/01/2025 10:27:38	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 05/01/2025 09:42:50	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;
Sun 05/01/2025 09:37:47	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 05/01/2025 09:00:46	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;
Sun 05/01/2025 08:58:57	3	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun 05/01/2025 07:58:24	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;
Sun 05/01/2025 06:20:06	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 05/01/2025 05:28:29	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 04/01/2025 17:54:57	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 04/01/2025 17:51:04	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 04/01/2025 11:13:25	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 04/01/2025 11:11:57	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 04/01/2025 10:24:45	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;

[fizz]

That downstream docsis 3.1 figures looks funny

[alphaomega16]

Wouldn't know about the downstream ones myself but I know all the uploads are supposed to be 64 and I believe last time I had this issue I was having upstream QAM differences as well, I think two were out of whack last year.

[alphaomega16]

Stupid no edit, WHY WAS EDIT TAKEN AWAY.

I wanted to add just because the pre and post errors are 0 doesn't mean there are not any, an update years ago stop them showing up.

[jpeg1]

How can it be my equipment?  TBB doesn't go past the modem, nothing connected to it should be able to cause this intermittent issue that keeps cropping up.

---

That's not right, is it?  Anything you do that puts traffic on your WAN connection will affect the TBB response.

For example, if you do a speed test you will see a corresponding latency spike on the BQM. It will not usually cause a packet loss though unless something else coincides with it.

What does your BQM look like now.  Can you post a live link?