Visitor
•
4 Messages
Suddenly high number of Corrected/Uncorrected packets MB8600
Hi - our internet has been rock solid the past two years until recently. Except for widespread outages I've never had so many intermittent disconnects. Can someone kindly review the below powers and SNRs and let me know if they are in spec?
Service runs from the outside junction box, inside, then one cable to the back of my cable modem. No repeaters or splitters inline.
| Channel | Lock Status | Modulation | Channel ID | Freq. (MHz) | Pwr (dBmV) | SNR (dB) | Corrected | Uncorrected |
| 1 | Locked | QAM256 | 17 | 489.0 | 8.5 | 42.5 | 2466539 | 5503673 |
| 2 | Locked | QAM256 | 1 | 387.0 | 8.8 | 42.6 | 0 | 0 |
| 3 | Locked | QAM256 | 2 | 393.0 | 8.9 | 42.8 | 11190 | 37881 |
| 4 | Locked | QAM256 | 3 | 399.0 | 8.9 | 42.9 | 84093 | 277911 |
| 5 | Locked | QAM256 | 4 | 405.0 | 8.8 | 42.8 | 476917 | 1457527 |
| 6 | Locked | QAM256 | 5 | 411.0 | 8.8 | 42.8 | 21872 | 56832 |
| 7 | Locked | QAM256 | 6 | 417.0 | 8.5 | 42.7 | 46490 | 165695 |
| 8 | Locked | QAM256 | 7 | 423.0 | 8.3 | 42.6 | 145697 | 494776 |
| 9 | Locked | QAM256 | 8 | 435.0 | 7.5 | 42.1 | 358236 | 1092635 |
| 10 | Locked | QAM256 | 9 | 441.0 | 6.5 | 41.5 | 179245 | 569893 |
| 11 | Locked | QAM256 | 10 | 447.0 | 7.9 | 42.3 | 325781 | 913392 |
| 12 | Locked | QAM256 | 11 | 453.0 | 8.3 | 42.5 | 120243 | 350624 |
| 13 | Locked | QAM256 | 12 | 459.0 | 8.3 | 42.5 | 91182 | 289987 |
| 14 | Locked | QAM256 | 13 | 465.0 | 8.4 | 42.4 | 285550 | 698306 |
| 15 | Locked | QAM256 | 14 | 471.0 | 8.4 | 42.4 | 518423 | 1414738 |
| 16 | Locked | QAM256 | 15 | 477.0 | 8.5 | 42.6 | 978014 | 2728084 |
| 17 | Locked | QAM256 | 16 | 483.0 | 8.4 | 42.5 | 2028223 | 5034723 |
| 18 | Locked | QAM256 | 18 | 495.0 | 8.4 | 42.6 | 2122053 | 5486065 |
| 19 | Locked | QAM256 | 19 | 507.0 | 8.4 | 42.6 | 570264 | 1574474 |
| 20 | Locked | QAM256 | 20 | 513.0 | 8.4 | 42.8 | 273579 | 830604 |
| 21 | Locked | QAM256 | 21 | 519.0 | 8.4 | 42.7 | 54680 | 157219 |
| 22 | Locked | QAM256 | 22 | 525.0 | 8.3 | 42.7 | 348 | 601 |
| 23 | Locked | QAM256 | 23 | 531.0 | 8.6 | 42.8 | 6 | 0 |
| 24 | Locked | QAM256 | 24 | 537.0 | 8.7 | 42.9 | 2 | 0 |
| 25 | Locked | QAM256 | 25 | 543.0 | 8.8 | 43.0 | 7 | 0 |
| 26 | Locked | QAM256 | 26 | 549.0 | 9.1 | 43.1 | 7 | 0 |
| 27 | Locked | QAM256 | 27 | 555.0 | 9.4 | 43.3 | 12 | 0 |
| 28 | Locked | QAM256 | 28 | 561.0 | 9.6 | 43.3 | 10 | 0 |
| 29 | Locked | OFDM PLC | 29 | 690.0 | 13.0 | 43.2 | 1556477710 | 0 |
| 30 | Locked | QAM256 | 30 | 567.0 | 10.0 | 43.2 | 11 | 0 |
| 31 | Locked | QAM256 | 31 | 573.0 | 10.0 | 43.1 | 2 | 0 |
| 32 | Locked | QAM256 | 32 | 579.0 | 10.4 | 43.5 | 9 | 0 |
| Channel | Lock Status | Channel Type | Channel ID | Symb. Rate (Ksym/sec) | Freq. (MHz) | Pwr (dBmV) |
| 1 | Locked | SC-QAM | 1 | 5120 | 16.3 | 38.8 |
| 2 | Locked | SC-QAM | 2 | 5120 | 22.8 | 38.5 |
| 3 | Locked | SC-QAM | 3 | 5120 | 29.2 | 38.8 |
| 4 | Locked | SC-QAM | 4 | 5120 | 35.6 | 38.8 |
| Date | Time | Priority | Description |
| Tue Nov 28 2023 | 11:10:51 | Warning (5) | MDD message timeout;CM-MAC=DD:EE:AA:DD:BB:EE;CMTS-MAC=DD:EE:AA:DD:BB:EE;CM-QOS=1.1;CM-VER=3.1; |
| Tue Nov 28 2023 | 11:11:03 | Notice (6) | CM-STATUS message sent. Event Type Code: 2; Chan ID: 20; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=DD:EE:AA:DD:BB:EE;CMTS-MAC=DD:EE:AA:DD:BB:EE;CM-QOS=1.1;CM-VER=3.1; |
| Tue Nov 28 2023 | 11:11:08 | Warning (5) | MDD message timeout;CM-MAC=DD:EE:AA:DD:BB:EE;CMTS-MAC=DD:EE:AA:DD:BB:EE;CM-QOS=1.1;CM-VER=3.1; |
| Tue Nov 28 2023 | 11:11:09 | Notice (6) | CM-STATUS message sent. Event Type Code: 5; Chan ID: 16 18 19 20; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=DD:EE:AA:DD:BB:EE;CMTS-MAC=DD:EE:AA:DD:BB:EE;CM-QOS=1.1;CM-VER=3.1; |
| Tue Nov 28 2023 | 11:11:13 | Notice (6) | CM-STATUS message sent. Event Type Code: 4; Chan ID: 16 19 20; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=DD:EE:AA:DD:BB:EE;CMTS-MAC=DD:EE:AA:DD:BB:EE;CM-QOS=1.1;CM-VER=3.1; |
| Tue Nov 28 2023 | 11:13:09 | Notice (6) | CM-STATUS message sent. Event Type Code: 2; Chan ID: 20; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=DD:EE:AA:DD:BB:EE;CMTS-MAC=DD:EE:AA:DD:BB:EE;CM-QOS=1.1;CM-VER=3.1; |
| Tue Nov 28 2023 | 11:13:09 | Warning (5) | MDD message timeout;CM-MAC=DD:EE:AA:DD:BB:EE;CMTS-MAC=DD:EE:AA:DD:BB:EE;CM-QOS=1.1;CM-VER=3.1; |
| Tue Nov 28 2023 | 11:13:34 | Notice (6) | CM-STATUS message sent. Event Type Code: 5; Chan ID: 16 18 19 20; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=DD:EE:AA:DD:BB:EE;CMTS-MAC=DD:EE:AA:DD:BB:EE;CM-QOS=1.1;CM-VER=3.1; |
| Tue Nov 28 2023 | 11:13:39 | Notice (6) | CM-STATUS message sent. Event Type Code: 4; Chan ID: 16 19 20; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=DD:EE:AA:DD:BB:EE;CMTS-MAC=DD:EE:AA:DD:BB:EE;CM-QOS=1.1;CM-VER=3.1; |
| Tue Nov 28 2023 | 11:14:38 | Notice (6) | CM-STATUS message sent. Event Type Code: 2; Chan ID: 19; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=DD:EE:AA:DD:BB:EE;CMTS-MAC=DD:EE:AA:DD:BB:EE;CM-QOS=1.1;CM-VER=3.1; |
| Tue Nov 28 2023 | 11:14:43 | Notice (6) | CM-STATUS message sent. Event Type Code: 5; Chan ID: 16 18 19 20; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=DD:EE:AA:DD:BB:EE;CMTS-MAC=DD:EE:AA:DD:BB:EE;CM-QOS=1.1;CM-VER=3.1; |
| Tue Nov 28 2023 | 11:14:52 | Warning (5) | MDD message timeout;CM-MAC=DD:EE:AA:DD:BB:EE;CMTS-MAC=DD:EE:AA:DD:BB:EE;CM-QOS=1.1;CM-VER=3.1; |
| Tue Nov 28 2023 | 11:14:54 | Notice (6) | CM-STATUS message sent. Event Type Code: 5; Chan ID: 16 18 19 20; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=DD:EE:AA:DD:BB:EE;CMTS-MAC=DD:EE:AA:DD:BB:EE;CM-QOS=1.1;CM-VER=3.1; |
| Tue Nov 28 2023 | 11:15:07 | Notice (6) | CM-STATUS message sent. Event Type Code: 4; Chan ID: 16 19 20; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=DD:EE:AA:DD:BB:EE;CMTS-MAC=DD:EE:AA:DD:BB:EE;CM-QOS=1.1;CM-VER=3.1; |
| Tue Nov 28 2023 | 11:15:38 | Warning (5) | MDD message timeout;CM-MAC=DD:EE:AA:DD:BB:EE;CMTS-MAC=DD:EE:AA:DD:BB:EE;CM-QOS=1.1;CM-VER=3.1; |
| Tue Nov 28 2023 | 11:15:42 | Notice (6) | CM-STATUS message sent. Event Type Code: 2; Chan ID: 19; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=DD:EE:AA:DD:BB:EE;CMTS-MAC=DD:EE:AA:DD:BB:EE;CM-QOS=1.1;CM-VER=3.1; |
| Tue Nov 28 2023 | 11:15:44 | Notice (6) | CM-STATUS message sent. Event Type Code: 5; Chan ID: 16 18 19 20; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=DD:EE:AA:DD:BB:EE;CMTS-MAC=DD:EE:AA:DD:BB:EE;CM-QOS=1.1;CM-VER=3.1; |
| Tue Nov 28 2023 | 11:15:59 | Notice (6) | CM-STATUS message sent. Event Type Code: 4; Chan ID: 16 19 20; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=DD:EE:AA:DD:BB:EE;CMTS-MAC=DD:EE:AA:DD:BB:EE;CM-QOS=1.1;CM-VER=3.1; |
| Tue Nov 28 2023 | 11:18:08 | Warning (5) | MDD message timeout;CM-MAC=DD:EE:AA:DD:BB:EE;CMTS-MAC=DD:EE:AA:DD:BB:EE;CM-QOS=1.1;CM-VER=3.1; |
| Tue Nov 28 2023 | 11:18:08 | Notice (6) | CM-STATUS message sent. Event Type Code: 5; Chan ID: 16 18 19 20; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=DD:EE:AA:DD:BB:EE;CMTS-MAC=DD:EE:AA:DD:BB:EE;CM-QOS=1.1;CM-VER=3.1; |
| Tue Nov 28 2023 | 11:18:12 | Warning (5) | MDD message timeout;CM-MAC=DD:EE:AA:DD:BB:EE;CMTS-MAC=DD:EE:AA:DD:BB:EE;CM-QOS=1.1;CM-VER=3.1; |
| Tue Nov 28 2023 | 11:18:23 | Notice (6) | CM-STATUS message sent. Event Type Code: 4; Chan ID: 16 18 19 20; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=DD:EE:AA:DD:BB:EE;CMTS-MAC=DD:EE:AA:DD:BB:EE;CM-QOS=1.1;CM-VER=3.1; |
| Tue Nov 28 2023 | 11:42:07 | Notice (6) | CM-STATUS message sent. Event Type Code: 5; Chan ID: 16 18 19 20; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=DD:EE:AA:DD:BB:EE;CMTS-MAC=DD:EE:AA:DD:BB:EE;CM-QOS=1.1;CM-VER=3.1; |
| Tue Nov 28 2023 | 11:42:26 | Warning (5) | MDD message timeout;CM-MAC=DD:EE:AA:DD:BB:EE;CMTS-MAC=DD:EE:AA:DD:BB:EE;CM-QOS=1.1;CM-VER=3.1; |
| Tue Nov 28 2023 | 11:42:54 | Notice (6) | CM-STATUS message sent. Event Type Code: 4; Chan ID: 16 18 19 20; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=DD:EE:AA:DD:BB:EE;CMTS-MAC=DD:EE:AA:DD:BB:EE;CM-QOS=1.1;CM-VER=3.1; |
| Tue Nov 28 2023 | 14:08:50 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=DD:EE:AA:DD:BB:EE;CMTS-MAC=DD:EE:AA:DD:BB:EE;CM-QOS=1.1;CM-VER=3.1; |
| Tue Nov 28 2023 | 15:47:23 | Notice (6) | CM-STATUS message sent. Event Type Code: 5; Chan ID: 15 16 18 19 20; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=DD:EE:AA:DD:BB:EE;CMTS-MAC=DD:EE:AA:DD:BB:EE;CM-QOS=1.1;CM-VER=3.1; |
| Tue Nov 28 2023 | 15:57:38 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=DD:EE:AA:DD:BB:EE;CMTS-MAC=DD:EE:AA:DD:BB:EE;CM-QOS=1.1;CM-VER=3.1; |
| Wed Nov 29 2023 | 9:01:46 | Warning (5) | MDD message timeout;CM-MAC=DD:EE:AA:DD:BB:EE;CMTS-MAC=DD:EE:AA:DD:BB:EE;CM-QOS=1.1;CM-VER=3.1; |
| Wed Nov 29 2023 | 9:02:09 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=DD:EE:AA:DD:BB:EE;CMTS-MAC=DD:EE:AA:DD:BB:EE;CM-QOS=1.1;CM-VER=3.1; |
| Wed Nov 29 2023 | 9:02:13 | Notice (6) | CM-STATUS message sent. Event Type Code: 4; Chan ID: 16 18 19 20; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=DD:EE:AA:DD:BB:EE;CMTS-MAC=DD:EE:AA:DD:BB:EE;CM-QOS=1.1;CM-VER=3.1; |
| Wed Nov 29 2023 | 12:01:51 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=DD:EE:AA:DD:BB:EE;CMTS-MAC=DD:EE:AA:DD:BB:EE;CM-QOS=1.1;CM-VER=3.1; |
| Wed Nov 29 2023 | 13:33:54 | Warning (5) | MDD message timeout;CM-MAC=DD:EE:AA:DD:BB:EE;CMTS-MAC=DD:EE:AA:DD:BB:EE;CM-QOS=1.1;CM-VER=3.1; |
| Wed Nov 29 2023 | 13:33:55 | Notice (6) | CM-STATUS message sent. Event Type Code: 4; Chan ID: 15 16 18 19 20; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=DD:EE:AA:DD:BB:EE;CMTS-MAC=DD:EE:AA:DD:BB:EE;CM-QOS=1.1;CM-VER=3.1; |
| Wed Nov 29 2023 | 13:33:56 | Warning (5) | MDD message timeout;CM-MAC=DD:EE:AA:DD:BB:EE;CMTS-MAC=DD:EE:AA:DD:BB:EE;CM-QOS=1.1;CM-VER=3.1; |
| Wed Nov 29 2023 | 13:34:09 | Notice (6) | CM-STATUS message sent. Event Type Code: 4; Chan ID: 14 15 16 18 19 20; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=DD:EE:AA:DD:BB:EE;CMTS-MAC=DD:EE:AA:DD:BB:EE;CM-QOS=1.1;CM-VER=3.1; |
| Wed Nov 29 2023 | 13:34:43 | Warning (5) | MDD message timeout;CM-MAC=DD:EE:AA:DD:BB:EE;CMTS-MAC=DD:EE:AA:DD:BB:EE;CM-QOS=1.1;CM-VER=3.1; |
| Wed Nov 29 2023 | 13:34:44 | Notice (6) | CM-STATUS message sent. Event Type Code: 2; Chan ID: 13; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=DD:EE:AA:DD:BB:EE;CMTS-MAC=DD:EE:AA:DD:BB:EE;CM-QOS=1.1;CM-VER=3.1; |
| Wed Nov 29 2023 | 13:34:45 | Warning (5) | MDD message timeout;CM-MAC=DD:EE:AA:DD:BB:EE;CMTS-MAC=DD:EE:AA:DD:BB:EE;CM-QOS=1.1;CM-VER=3.1; |
| Wed Nov 29 2023 | 13:34:49 | Notice (6) | CM-STATUS message sent. Event Type Code: 5; Chan ID: 13 15 16 18 19 20; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=DD:EE:AA:DD:BB:EE;CMTS-MAC=DD:EE:AA:DD:BB:EE;CM-QOS=1.1;CM-VER=3.1; |
| Wed Nov 29 2023 | 13:34:55 | Warning (5) | MDD message timeout;CM-MAC=DD:EE:AA:DD:BB:EE;CMTS-MAC=DD:EE:AA:DD:BB:EE;CM-QOS=1.1;CM-VER=3.1; |
| Wed Nov 29 2023 | 13:35:04 | Notice (6) | CM-STATUS message sent. Event Type Code: 4; Chan ID: 13 14 15 16 18 19 20; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=DD:EE:AA:DD:BB:EE;CMTS-MAC=DD:EE:AA:DD:BB:EE;CM-QOS=1.1;CM-VER=3.1; |
| Wed Nov 29 2023 | 13:35:07 | Warning (5) | MDD message timeout;CM-MAC=DD:EE:AA:DD:BB:EE;CMTS-MAC=DD:EE:AA:DD:BB:EE;CM-QOS=1.1;CM-VER=3.1; |
| Wed Nov 29 2023 | 13:35:23 | Notice (6) | CM-STATUS message sent. Event Type Code: 4; Chan ID: 13 14 15 16 18 19 20; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=DD:EE:AA:DD:BB:EE;CMTS-MAC=DD:EE:AA:DD:BB:EE;CM-QOS=1.1;CM-VER=3.1; |
| Wed Nov 29 2023 | 20:23:27 | Warning (5) | MDD message timeout;CM-MAC=DD:EE:AA:DD:BB:EE;CMTS-MAC=DD:EE:AA:DD:BB:EE;CM-QOS=1.1;CM-VER=3.1; |
| Wed Nov 29 2023 | 20:23:35 | Notice (6) | CM-STATUS message sent. Event Type Code: 4; Chan ID: 13 14 15 16 18 19 20; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=DD:EE:AA:DD:BB:EE;CMTS-MAC=DD:EE:AA:DD:BB:EE;CM-QOS=1.1;CM-VER=3.1; |
| Wed Nov 29 2023 | 20:24:22 | Warning (5) | MDD message timeout;CM-MAC=DD:EE:AA:DD:BB:EE;CMTS-MAC=DD:EE:AA:DD:BB:EE;CM-QOS=1.1;CM-VER=3.1; |
| Wed Nov 29 2023 | 20:24:23 | Notice (6) | CM-STATUS message sent. Event Type Code: 5; Chan ID: 13 15 16 18 19 20; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=DD:EE:AA:DD:BB:EE;CMTS-MAC=DD:EE:AA:DD:BB:EE;CM-QOS=1.1;CM-VER=3.1; |
| Wed Nov 29 2023 | 20:24:23 | Notice (6) | CM-STATUS message sent. Event Type Code: 1; Chan ID: 16; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=DD:EE:AA:DD:BB:EE;CMTS-MAC=DD:EE:AA:DD:BB:EE;CM-QOS=1.1;CM-VER=3.1; |
| Wed Nov 29 2023 | 20:24:31 | Notice (6) | CM-STATUS message sent. Event Type Code: 4; Chan ID: 13 14 15 16 18 19 20; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=DD:EE:AA:DD:BB:EE;CMTS-MAC=DD:EE:AA:DD:BB:EE;CM-QOS=1.1;CM-VER=3.1; |
| Wed Nov 29 2023 | 20:25:19 | Warning (5) | MDD message timeout;CM-MAC=DD:EE:AA:DD:BB:EE;CMTS-MAC=DD:EE:AA:DD:BB:EE;CM-QOS=1.1;CM-VER=3.1; |
| Wed Nov 29 2023 | 20:26:09 | Notice (6) | CM-STATUS message sent. Event Type Code: 5; Chan ID: 13 15 16 18 19 20; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=DD:EE:AA:DD:BB:EE;CMTS-MAC=DD:EE:AA:DD:BB:EE;CM-QOS=1.1;CM-VER=3.1; |
| Wed Nov 29 2023 | 20:26:14 | Notice (6) | CM-STATUS message sent. Event Type Code: 4; Chan ID: 13 14 15 16 18 19 20; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=DD:EE:AA:DD:BB:EE;CMTS-MAC=DD:EE:AA:DD:BB:EE;CM-QOS=1.1;CM-VER=3.1; |
| Wed Nov 29 2023 | 20:26:19 | Notice (6) | CM-STATUS message sent. Event Type Code: 5; Chan ID: 13 15 16 18 19 20; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=DD:EE:AA:DD:BB:EE;CMTS-MAC=DD:EE:AA:DD:BB:EE;CM-QOS=1.1;CM-VER=3.1; |
| Wed Nov 29 2023 | 20:26:21 | Warning (5) | MDD message timeout;CM-MAC=DD:EE:AA:DD:BB:EE;CMTS-MAC=DD:EE:AA:DD:BB:EE;CM-QOS=1.1;CM-VER=3.1; |
| Wed Nov 29 2023 | 20:26:54 | Notice (6) | CM-STATUS message sent. Event Type Code: 4; Chan ID: 13 14 15 16 18 19 20; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=DD:EE:AA:DD:BB:EE;CMTS-MAC=DD:EE:AA:DD:BB:EE;CM-QOS=1.1;CM-VER=3.1; |
| Wed Nov 29 2023 | 20:28:38 | Warning (5) | MDD message timeout;CM-MAC=DD:EE:AA:DD:BB:EE;CMTS-MAC=DD:EE:AA:DD:BB:EE;CM-QOS=1.1;CM-VER=3.1; |
| Wed Nov 29 2023 | 20:32:17 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=DD:EE:AA:DD:BB:EE;CMTS-MAC=DD:EE:AA:DD:BB:EE;CM-QOS=1.1;CM-VER=3.1; |
| Wed Nov 29 2023 | 20:39:03 | Warning (5) | MDD message timeout;CM-MAC=DD:EE:AA:DD:BB:EE;CMTS-MAC=DD:EE:AA:DD:BB:EE;CM-QOS=1.1;CM-VER=3.1; |
| Wed Nov 29 2023 | 20:39:11 | Notice (6) | CM-STATUS message sent. Event Type Code: 4; Chan ID: 13 14 15 16 18 19 20; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=DD:EE:AA:DD:BB:EE;CMTS-MAC=DD:EE:AA:DD:BB:EE;CM-QOS=1.1;CM-VER=3.1; |
| Wed Nov 29 2023 | 20:39:17 | Warning (5) | MDD message timeout;CM-MAC=DD:EE:AA:DD:BB:EE;CMTS-MAC=DD:EE:AA:DD:BB:EE;CM-QOS=1.1;CM-VER=3.1; |
| Wed Nov 29 2023 | 20:39:47 | Notice (6) | CM-STATUS message sent. Event Type Code: 4; Chan ID: 13 14 15 16 18 19 20; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=DD:EE:AA:DD:BB:EE;CMTS-MAC=DD:EE:AA:DD:BB:EE;CM-QOS=1.1;CM-VER=3.1; |
| Wed Nov 29 2023 | 20:41:28 | Notice (6) | CM-STATUS message sent. Event Type Code: 2; Chan ID: 16; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=DD:EE:AA:DD:BB:EE;CMTS-MAC=DD:EE:AA:DD:BB:EE;CM-QOS=1.1;CM-VER=3.1; |
| Wed Nov 29 2023 | 20:41:30 | Warning (5) | MDD message timeout;CM-MAC=DD:EE:AA:DD:BB:EE;CMTS-MAC=DD:EE:AA:DD:BB:EE;CM-QOS=1.1;CM-VER=3.1; |
| Wed Nov 29 2023 | 20:41:34 | Notice (6) | CM-STATUS message sent. Event Type Code: 5; Chan ID: 13 15 16 18 19 20; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=DD:EE:AA:DD:BB:EE;CMTS-MAC=DD:EE:AA:DD:BB:EE;CM-QOS=1.1;CM-VER=3.1; |
| Wed Nov 29 2023 | 20:41:40 | Notice (6) | CM-STATUS message sent. Event Type Code: 4; Chan ID: 13 14 15 16 18 19 20; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=DD:EE:AA:DD:BB:EE;CMTS-MAC=DD:EE:AA:DD:BB:EE;CM-QOS=1.1;CM-VER=3.1; |
| Wed Nov 29 2023 | 20:43:40 | Warning (5) | MDD message timeout;CM-MAC=DD:EE:AA:DD:BB:EE;CMTS-MAC=DD:EE:AA:DD:BB:EE;CM-QOS=1.1;CM-VER=3.1; |
| Wed Nov 29 2023 | 20:43:40 | Notice (6) | CM-STATUS message sent. Event Type Code: 4; Chan ID: 13 14 15 16 18 19 20; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=DD:EE:AA:DD:BB:EE;CMTS-MAC=DD:EE:AA:DD:BB:EE;CM-QOS=1.1;CM-VER=3.1; |
| Wed Nov 29 2023 | 20:43:48 | Warning (5) | MDD message timeout;CM-MAC=DD:EE:AA:DD:BB:EE;CMTS-MAC=DD:EE:AA:DD:BB:EE;CM-QOS=1.1;CM-VER=3.1; |
| Wed Nov 29 2023 | 20:43:53 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=DD:EE:AA:DD:BB:EE;CMTS-MAC=DD:EE:AA:DD:BB:EE;CM-QOS=1.1;CM-VER=3.1; |
| Wed Nov 29 2023 | 21:18:29 | Warning (5) | MDD message timeout;CM-MAC=DD:EE:AA:DD:BB:EE;CMTS-MAC=DD:EE:AA:DD:BB:EE;CM-QOS=1.1;CM-VER=3.1; |
| Wed Nov 29 2023 | 21:18:49 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=DD:EE:AA:DD:BB:EE;CMTS-MAC=DD:EE:AA:DD:BB:EE;CM-QOS=1.1;CM-VER=3.1; |
| Wed Nov 29 2023 | 21:18:56 | Notice (6) | CM-STATUS message sent. Event Type Code: 4; Chan ID: 13 14 15 16 18 19 20; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=DD:EE:AA:DD:BB:EE;CMTS-MAC=DD:EE:AA:DD:BB:EE;CM-QOS=1.1;CM-VER=3.1; |
| Thu Nov 30 2023 | 14:07:39 | Notice (6) | CM-STATUS message sent. Event Type Code: 20; Chan ID: 29; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=DD:EE:AA:DD:BB:EE;CMTS-MAC=DD:EE:AA:DD:BB:EE;CM-QOS=1.1;CM-VER=3.1; |
| Thu Nov 30 2023 | 14:12:07 | Notice (6) | CM-STATUS message sent. Event Type Code: 22; Chan ID: 29; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=DD:EE:AA:DD:BB:EE;CMTS-MAC=DD:EE:AA:DD:BB:EE;CM-QOS=1.1;CM-VER=3.1; |
| Fri Dec 1 2023 | 9:35:45 | Notice (6) | CM-STATUS message sent. Event Type Code: 20; Chan ID: 29; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=DD:EE:AA:DD:BB:EE;CMTS-MAC=DD:EE:AA:DD:BB:EE;CM-QOS=1.1;CM-VER=3.1; |
| Fri Dec 1 2023 | 9:38:28 | Notice (6) | CM-STATUS message sent. Event Type Code: 22; Chan ID: 29; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=DD:EE:AA:DD:BB:EE;CMTS-MAC=DD:EE:AA:DD:BB:EE;CM-QOS=1.1;CM-VER=3.1; |
| Fri Dec 1 2023 | 12:00:12 | Notice (6) | CM-STATUS message sent. Event Type Code: 5; Chan ID: 13 14 15 16 18 19 20; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=DD:EE:AA:DD:BB:EE;CMTS-MAC=DD:EE:AA:DD:BB:EE;CM-QOS=1.1;CM-VER=3.1; |
| Sun Dec 3 2023 | 22:39:24 | Warning (5) | MDD message timeout;CM-MAC=DD:EE:AA:DD:BB:EE;CMTS-MAC=DD:EE:AA:DD:BB:EE;CM-QOS=1.1;CM-VER=3.1; |
| Sun Dec 3 2023 | 22:39:26 | Notice (6) | CM-STATUS message sent. Event Type Code: 4; Chan ID: 8 13 14 15 16 18 19 20; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=DD:EE:AA:DD:BB:EE;CMTS-MAC=DD:EE:AA:DD:BB:EE;CM-QOS=1.1;CM-VER=3.1; |
| Sun Dec 3 2023 | 22:40:20 | Warning (5) | MDD message timeout;CM-MAC=DD:EE:AA:DD:BB:EE;CMTS-MAC=DD:EE:AA:DD:BB:EE;CM-QOS=1.1;CM-VER=3.1; |
| Sun Dec 3 2023 | 22:40:31 | Notice (6) | CM-STATUS message sent. Event Type Code: 4; Chan ID: 8 13 14 15 16 18 19 20; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=DD:EE:AA:DD:BB:EE;CMTS-MAC=DD:EE:AA:DD:BB:EE;CM-QOS=1.1;CM-VER=3.1; |
| Sun Dec 3 2023 | 22:41:01 | Warning (5) | MDD message timeout;CM-MAC=DD:EE:AA:DD:BB:EE;CMTS-MAC=DD:EE:AA:DD:BB:EE;CM-QOS=1.1;CM-VER=3.1; |
| Sun Dec 3 2023 | 22:41:25 | Notice (6) | CM-STATUS message sent. Event Type Code: 4; Chan ID: 8 13 14 15 16 18 19 20; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=DD:EE:AA:DD:BB:EE;CMTS-MAC=DD:EE:AA:DD:BB:EE;CM-QOS=1.1;CM-VER=3.1; |
| Sun Dec 3 2023 | 22:45:50 | Warning (5) | MDD message timeout;CM-MAC=DD:EE:AA:DD:BB:EE;CMTS-MAC=DD:EE:AA:DD:BB:EE;CM-QOS=1.1;CM-VER=3.1; |
| Sun Dec 3 2023 | 22:45:52 | Notice (6) | CM-STATUS message sent. Event Type Code: 5; Chan ID: 9 13 14 15 16 18 19 20; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=DD:EE:AA:DD:BB:EE;CMTS-MAC=DD:EE:AA:DD:BB:EE;CM-QOS=1.1;CM-VER=3.1; |
| Sun Dec 3 2023 | 22:46:00 | Warning (5) | MDD message timeout;CM-MAC=DD:EE:AA:DD:BB:EE;CMTS-MAC=DD:EE:AA:DD:BB:EE;CM-QOS=1.1;CM-VER=3.1; |
| Sun Dec 3 2023 | 22:46:02 | Notice (6) | CM-STATUS message sent. Event Type Code: 2; Chan ID: 9; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=DD:EE:AA:DD:BB:EE;CMTS-MAC=DD:EE:AA:DD:BB:EE;CM-QOS=1.1;CM-VER=3.1; |
| Sun Dec 3 2023 | 22:46:07 | Notice (6) | CM-STATUS message sent. Event Type Code: 5; Chan ID: 9 13 14 15 16 18 19 20; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=DD:EE:AA:DD:BB:EE;CMTS-MAC=DD:EE:AA:DD:BB:EE;CM-QOS=1.1;CM-VER=3.1; |
| Sun Dec 3 2023 | 22:46:08 | Notice (6) | CM-STATUS message sent. Event Type Code: 4; Chan ID: 8 9 11 13 14 15 16 18 19 20; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=DD:EE:AA:DD:BB:EE;CMTS-MAC=DD:EE:AA:DD:BB:EE;CM-QOS=1.1;CM-VER=3.1; |
| Sun Dec 3 2023 | 22:46:52 | Warning (5) | MDD message timeout;CM-MAC=DD:EE:AA:DD:BB:EE;CMTS-MAC=DD:EE:AA:DD:BB:EE;CM-QOS=1.1;CM-VER=3.1; |
| Sun Dec 3 2023 | 22:47:20 | Notice (6) | CM-STATUS message sent. Event Type Code: 4; Chan ID: 8 9 11 13 14 15 16 18 19 20; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=DD:EE:AA:DD:BB:EE;CMTS-MAC=DD:EE:AA:DD:BB:EE;CM-QOS=1.1;CM-VER=3.1; |
| Sun Dec 3 2023 | 23:31:48 | Warning (5) | MDD message timeout;CM-MAC=DD:EE:AA:DD:BB:EE;CMTS-MAC=DD:EE:AA:DD:BB:EE;CM-QOS=1.1;CM-VER=3.1; |
| Sun Dec 3 2023 | 23:31:49 | Notice (6) | CM-STATUS message sent. Event Type Code: 5; Chan ID: 9 11 13 14 15 16 18 19 20; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=DD:EE:AA:DD:BB:EE;CMTS-MAC=DD:EE:AA:DD:BB:EE;CM-QOS=1.1;CM-VER=3.1; |
| Sun Dec 3 2023 | 23:31:56 | Warning (5) | MDD message timeout;CM-MAC=DD:EE:AA:DD:BB:EE;CMTS-MAC=DD:EE:AA:DD:BB:EE;CM-QOS=1.1;CM-VER=3.1; |
| Sun Dec 3 2023 | 23:31:59 | Notice (6) | CM-STATUS message sent. Event Type Code: 5; Chan ID: 9 11 13 14 15 16 18 19 20; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=DD:EE:AA:DD:BB:EE;CMTS-MAC=DD:EE:AA:DD:BB:EE;CM-QOS=1.1;CM-VER=3.1; |
| Sun Dec 3 2023 | 23:32:18 | Notice (6) | CM-STATUS message sent. Event Type Code: 4; Chan ID: 8 9 10 11 13 14 15 16 18 19 20; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=DD:EE:AA:DD:BB:EE;CMTS-MAC=DD:EE:AA:DD:BB:EE;CM-QOS=1.1;CM-VER=3.1; |
| Sun Dec 3 2023 | 23:39:04 | Warning (5) | MDD message timeout;CM-MAC=DD:EE:AA:DD:BB:EE;CMTS-MAC=DD:EE:AA:DD:BB:EE;CM-QOS=1.1;CM-VER=3.1; |
| Sun Dec 3 2023 | 23:39:23 | Notice (6) | CM-STATUS message sent. Event Type Code: 4; Chan ID: 8 9 10 11 12 13 14 15 16 18 19 20; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=DD:EE:AA:DD:BB:EE;CMTS-MAC=DD:EE:AA:DD:BB:EE;CM-QOS=1.1;CM-VER=3.1; |
| Sun Dec 3 2023 | 23:43:31 | Notice (6) | CM-STATUS message sent. Event Type Code: 5; Chan ID: 9 11 13 14 15 16 18 19 20; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=DD:EE:AA:DD:BB:EE;CMTS-MAC=DD:EE:AA:DD:BB:EE;CM-QOS=1.1;CM-VER=3.1; |
XfinityEricB
Official Employee
•
3.2K Messages
2 years ago
Hello @user_ba8f09, and thank you for reaching out with your connection issue. I would be happy to take a direct look at your signals at this time, and see if I can find out what is causing the problem.
Can you send us a direct message with your full name, name of account holder (if different), and service address please?
To send a "Direct Message" to Xfinity Support:
Click "Sign In" if necessary
Click the "Direct Messaging" icon (speech bubble)
Click the "New message" (pencil and paper) icon
The "To:" line prompts you to "Type the name of a person". Instead, type "Xfinity Support" there
- As you are typing a drop-down list appears. Select "Xfinity Support" from that list
- An "Xfinity Support" graphic replaces the "To:" line
Type your message in the text area near the bottom of the window
Press Enter to send it
0
0
user_ba8f09
Visitor
•
4 Messages
2 years ago
It'd be more helpful to the community if you could respond publicly.
2
0