Thu Jul 03 16:19:52 2025 |
Notice (6) |
Honoring MDD; IP provisioning mode = IPv6 |
Thu Jul 03 16:20:05 2025 |
Critical (3) |
Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=00:40...................................:00;CM-QOS=1.1;CM-VER=3.0; |
Thu Jul 03 16:20:14 2025 |
Critical (3) |
No Ranging Response received - T3 time-out;CM-MAC=00:40.........................................:00;CM-QOS=1.1;CM-VER=3.0; |
Thu Jul 03 16:20:35 2025 |
Critical (3) |
Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=00:40:.........................................::00;CM-QOS=1.1;CM-VER=3.0; |
Thu Jul 03 16:20:58 2025 |
Critical (3) |
No Ranging Response received - T3 time-out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=00:90.........................................:QOS=1.0;CM-VER=3.0; |
Thu Jul 03 16:21:11 2025 |
Notice (6) |
Received REG-RSP while in REG-HOLD1 state;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=00:90.........................................:-QOS=1.0;CM-VER=3.0; |
Thu Jul 03 16:25:59 2025 |
Critical (3) |
No Ranging Response received - T3 time-out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=00:90.........................................:QOS=1.0;CM-VER=3.0; |
Thu Jul 03 16:26:05 2025 |
Notice (6) |
Honoring MDD; IP provisioning mode = IPv6 |
Thu Jul 03 16:27:05 2025 |
Critical (3) |
Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40.............................:;CMTS-MAC=00:90:.......................:-QOS=1.1;CM-VER=3.0; |
Thu Jul 03 16:28:10 2025 |
Critical (3) |
Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=00:40.......................;CMTS-MAC=00:90:..................................-QOS=1.1;CM-VER=3.0; |
Thu Jul 03 16:28:28 2025 |
Critical (3) |
No Ranging Response received - T3 time-out;CM-MAC=00:40.......................;CMTS-MAC=00:90:.............;CM-QOS=1.0;CM-VER=3.0; |
Thu Jul 03 16:28:47 2025 |
Notice (6) |
Honoring MDD; IP provisioning mode = IPv6 |
Thu Jul 03 16:29:23 2025 |
Critical (3) |
No Ranging Response received - T3 time-out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=00:90:...............;CM-QOS=1.1;CM-VER=3.0; |
Thu Jul 03 16:29:30 2025 |
Critical (3) |
Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=00:40:................;CMTS-MAC=00:90.......................;CM-QOS=1.1;CM-VER=3.0; |
Thu Jul 03 16:29:43 2025 |
Critical (3) |
No Ranging Response received - T3 time-out;CM-MAC=00:40:3.....................;CMTS-MAC=00:90...................CM-QOS=1.0;CM-VER=3.0; |
Thu Jul 03 16:29:59 2025 |
Notice (6) |
Received REG-RSP while in REG-HOLD1 state;CM-MAC=00:40...................;CMTS-MAC=00:90:...................CM-QOS=1.0;CM-VER=3.0; |
Thu Jul 03 16:30:00 2025 |
Critical (3) |
No Ranging Response received - T3 time-out;CM-MAC=00:40..................;CMTS-MAC=00:90................CM-QOS=1.0;CM-VER=3.0; |
Thu Jul 03 16:30:05 2025 |
Notice (6) |
Received REG-RSP while in REG-HOLD1 state;CM-MAC=00:40:3..................;CMTS-MAC=00:90:................;CM-QOS=1.0;CM-VER=3.0; |
Thu Jul 03 16:32:03 2025 |
Critical (3) |
No Ranging Response received - T3 time-out;CM-MAC=00:40:3..................;CMTS-MAC=00:9........................;CM-QOS=1.0;CM-VER=3.0; |
Thu Jul 03 16:32:07 2025 |
Notice (6) |
Honoring MDD; IP provisioning mode = IPv6 |
Thu Jul 03 17:13:33 2025 |
Critical (3) |
Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:................;CMTS-MAC=00:9......................;CM-QOS=1.1;CM-VER=3.0; |
Thu Jul 03 17:14:38 2025 |
Critical (3) |
Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=00:40.............;CMTS-MAC=00:90:f.................;CM-QOS=1.1;CM-VER=3.0; |
Thu Jul 03 17:15:01 2025 |
Critical (3) |
No Ranging Response received - T3 time-out;CM-MAC=00:40:.................;CMTS-MAC=00:90....................CM-QOS=1.0;CM-VER=3.0; |
Thu Jul 03 17:15:23 2025 |
Critical (3) |
Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:.......................;CMTS-MAC=00:90:.......................CM-QOS=1.0;CM-VER=3.0; |
Thu Jul 03 17:15:26 2025 |
Notice (6) |
Honoring MDD; IP provisioning mode = IPv6 |
Tue Jul 08 08:08:41 2025 |
Critical (3) |
Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:.......................;CMTS-MAC=00:90.......................-QOS=1.1;CM-VER=3.0; |
Tue Jul 08 08:08:41 2025 |
Critical (3) |
Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=00:40:.......................;CMTS-MAC=00:90:.......................;CM-QOS=1.1;CM-VER=3.0; |
Tue Jul 08 08:08:45 2025 |
Critical (3) |
Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:36:65:a0:82;CMTS-MAC=00:90.......................;CM-QOS=1.1;CM-VER=3.0; |
Tue Jul 08 08:09:51 2025 |
Critical (3) |
Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=00:40:.......................;CMTS-MAC=00:.......................-QOS=1.1;CM-VER=3.0; |
Tue Jul 08 08:10:13 2025 |
Critical (3) |
No Ranging Response received - T3 time-out;CM-MAC=00:40:.......................-MAC=00:90:f.......................;CM-QOS=1.0;CM-VER=3.0; |
Tue Jul 08 08:10:39 2025 |
Critical (3) |
Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:.......................;CMTS-MAC=00:90:.......................;CM-QOS=1.0;CM-VER=3.0; |
Tue Jul 08 08:10:42 2025 |
Notice (6) |
Honoring MDD; IP provisioning mode = IPv6 |
EG
Expert
•
111.5K Messages
6 hours ago
The upstream power is still too high as it was last year. This needs to be addressed !
If there is nothing more that you can do to improve the connection quality, then you'll need to get the techs involved again until it gets fixed properly.
Bear in mind that if the premises facing techs can not find or fix a problem at your home, it is they who are responsible for escalating it up to their line / network / maintenance dept. techs. The problem may lie beyond your home in the local neighborhood infrastructure somewhere but it is their S.O.P. to start at the home. And if the problem is found to be on their side of the demarcation point, there will not be any charge.
Good luck !
0
0