Issues With Speed and Packet Loss

Let me preface this by saying that an Xfinity tech came out to my address, checked my equipment, and verified it was fine. He identified an issue with signal from the circuit, replaced the coaxial connectors, and it was fine. For a week.

I've been having speed issues for the last month, on and off. Instead of gigabit speeds, it will frequently drop to 50 mb/s or less (with a bare minimum of 5% packet loss).

The Xfinity automated troubleshooter finds no issue with my service because my modem is connected, and tells me to kick rocks. If I schedule a callback, the Helpdesk Agent runs through the generic troubleshooting steps, finds no issue, and tells me to kick rocks and talk to my modem manufacturer. The last one I spoke to actually told me to reset my mobile phone to resolve the issue, and then hung up on me when I told them that was ridiculous and I would not be doing that (if you can believe it).

I've factory reset my MB8600 and re-set it up, which made no difference. The same with my Asus RT-AX68U.

After running a tracert and noticing drops and latency outside my home network, I decided to check my Modem's log and connection status. I'm seeing a large amount of MDD Message timeout warnings which line up with the packet loss I see, and a massive number of uncorrected code words on all Downstream channels. I've attached the logs and the connection info below.

To my eye, it looks like an issue upstream on the circuit, but I wanted other eyes on it and maybe to speak to someone at Xfinity that isn't reading a script and refusing to deviate from it. Any help would be appreciated.

22:19:45 Mon Nov 27 2023	Notice (6)	CM-STATUS message sent. Event Type Code: 2; Chan ID: 31 32; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-QOS=1.1;CM-VER=3.1;
22:19:53 Mon Nov 27 2023	Notice (6)	CM-STATUS message sent. Event Type Code: 5; Chan ID: 1 2 3 4 5 6 7 8 9 10 11 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;-QOS=1.1;CM-VER=
22:20:00 Mon Nov 27 2023	Notice (6)	CM-STATUS message sent. Event Type Code: 4; Chan ID: 4 8 9 11 14 15 16 17 18 19 20 22 23 24 25 26 27 28 29 30; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-QOS=1.1;CM-VER=3.1;
22:20:01 Mon Nov 27 2023	Warning (5)	MDD message timeout;CM-QOS=1.1;CM-VER=3.1;
22:20:05 Mon Nov 27 2023	Notice (6)	CM-STATUS message sent. Event Type Code: 1; Chan ID: 29 31 32; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-QOS=1.1;CM-VER=3.1;
22:20:18 Mon Nov 27 2023	Notice (6)	CM-STATUS message sent. Event Type Code: 4; Chan ID: 4 8 9 11 14 15 16 17 18 19 20 22 23 24 25 26 27 28 29 30; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-QOS=1.1;CM-VER=3.1;
22:20:21 Mon Nov 27 2023	Warning (5)	MDD message timeout;CM-QOS=1.1;CM-VER=3.1;
22:20:23 Mon Nov 27 2023	Notice (6)	CM-STATUS message sent. Event Type Code: 1; Chan ID: 27 31 32; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-QOS=1.1;CM-VER=3.1;
22:20:39 Mon Nov 27 2023	Notice (6)	CM-STATUS message sent. Event Type Code: 4; Chan ID: 4 8 9 11 14 15 16 17 18 19 20 22 23 24 25 26 27 28 29 30; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-QOS=1.1;CM-VER=3.1;
22:20:59 Mon Nov 27 2023	Warning (5)	MDD message timeout;CM-QOS=1.1;CM-VER=3.1;
22:21:10 Mon Nov 27 2023	Notice (6)	CM-STATUS message sent. Event Type Code: 4; Chan ID: 4 8 9 11 14 15 16 17 18 19 20 22 23 24 25 26 27 28 29 30; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-QOS=1.1;CM-VER=3.1;
22:21:14 Mon Nov 27 2023	Notice (6)	CM-STATUS message sent. Event Type Code: 1; Chan ID: 31 32; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-QOS=1.1;CM-VER=3.1;
22:21:17 Mon Nov 27 2023	Warning (5)	MDD message timeout;CM-QOS=1.1;CM-VER=3.1;
22:21:30 Mon Nov 27 2023	Notice (6)	CM-STATUS message sent. Event Type Code: 4; Chan ID: 4 8 9 11 14 15 16 17 18 19 20 22 23 24 25 26 27 28 29 30; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-QOS=1.1;CM-VER=3.1;
22:21:30 Mon Nov 27 2023	Notice (6)	CM-STATUS message sent. Event Type Code: 1; Chan ID: 31 32; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-QOS=1.1;CM-VER=3.1;
22:21:41 Mon Nov 27 2023	Warning (5)	MDD message timeout;CM-QOS=1.1;CM-VER=3.1;
22:21:45 Mon Nov 27 2023	Notice (6)	CM-STATUS message sent. Event Type Code: 2; Chan ID: 31 32; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-QOS=1.1;CM-VER=3.1;
22:21:48 Mon Nov 27 2023	Notice (6)	CM-STATUS message sent. Event Type Code: 2; Chan ID: 31; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-QOS=1.1;CM-VER=3.1;
22:21:49 Mon Nov 27 2023	Notice (6)	CM-STATUS message sent. Event Type Code: 1; Chan ID: 31 32; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-QOS=1.1;CM-VER=3.1;
22:21:49 Mon Nov 27 2023	Notice (6)	CM-STATUS message sent. Event Type Code: 2; Chan ID: 31 32; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-QOS=1.1;CM-VER=3.1;
22:21:51 Mon Nov 27 2023	Notice (6)	CM-STATUS message sent. Event Type Code: 5; Chan ID: 1 2 3 4 5 6 7 8 9 10 11 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-QOS=1.1;CM-VER=
22:21:51 Mon Nov 27 2023	Notice (6)	CM-STATUS message sent. Event Type Code: 4; Chan ID: 4 8 9 11 14 15 16 17 18 19 20 22 23 24 25 26 27 28 29 30; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-QOS=1.1;CM-VER=3.1;
22:21:59 Mon Nov 27 2023	Warning (5)	MDD message timeout;CM-QOS=1.1;CM-VER=3.1;
22:22:05 Mon Nov 27 2023	Notice (6)	CM-STATUS message sent. Event Type Code: 1; Chan ID: 31 32; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-QOS=1.1;CM-VER=3.1;
22:22:19 Mon Nov 27 2023	Warning (5)	MDD message timeout;CM-QOS=1.1;CM-VER=3.1;
22:22:23 Mon Nov 27 2023	Notice (6)	CM-STATUS message sent. Event Type Code: 4; Chan ID: 4 8 9 11 14 15 16 17 18 19 20 22 23 24 25 26 27 28 29 30; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-QOS=1.1;CM-VER=3.1;
22:22:28 Mon Nov 27 2023	Notice (6)	CM-STATUS message sent. Event Type Code: 1; Chan ID: 31 32; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-QOS=1.1;CM-VER=3.1;
22:23:01 Mon Nov 27 2023	Warning (5)	MDD message timeout;CM-QOS=1.1;CM-VER=3.1;
22:23:06 Mon Nov 27 2023	Notice (6)	CM-STATUS message sent. Event Type Code: 1; Chan ID: 31 32; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-QOS=1.1;CM-VER=3.1;
22:23:11 Mon Nov 27 2023	Warning (5)	MDD message timeout;CM-QOS=1.1;CM-VER=3.1;
22:23:33 Mon Nov 27 2023	Notice (6)	CM-STATUS message sent. Event Type Code: 4; Chan ID: 4 8 9 11 14 15 16 17 18 19 20 22 23 24 25 26 27 28 29 30; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-QOS=1.1;CM-VER=3.1;
22:23:33 Mon Nov 27 2023	Notice (6)	CM-STATUS message sent. Event Type Code: 1; Chan ID: 31 32; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-QOS=1.1;CM-VER=3.1;
22:23:45 Mon Nov 27 2023	Warning (5)	MDD message timeout;CM-QOS=1.1;CM-VER=3.1;
22:24:01 Mon Nov 27 2023	Notice (6)	CM-STATUS message sent. Event Type Code: 1; Chan ID: 31 32; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-QOS=1.1;CM-VER=3.1;
22:24:03 Mon Nov 27 2023	Notice (6)	CM-STATUS message sent. Event Type Code: 4; Chan ID: 4 8 9 11 14 15 16 17 18 19 20 22 23 24 25 26 27 28 29 30; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-QOS=1.1;CM-VER=3.1;
22:24:16 Mon Nov 27 2023	Warning (5)	MDD message timeout;CM-QOS=1.1;CM-VER=3.1;
22:24:22 Mon Nov 27 2023	Notice (6)	CM-STATUS message sent. Event Type Code: 4; Chan ID: 4 8 9 11 14 15 16 17 18 19 20 22 23 24 25 26 27 28 29 30; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-QOS=1.1;CM-VER=3.1;
22:24:28 Mon Nov 27 2023	Notice (6)	CM-STATUS message sent. Event Type Code: 1; Chan ID: 31 32; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-QOS=1.1;CM-VER=3.1;
22:25:00 Mon Nov 27 2023	Warning (5)	MDD message timeout;CM-QOS=1.1;CM-VER=3.1;
22:25:03 Mon Nov 27 2023	Notice (6)	CM-STATUS message sent. Event Type Code: 4; Chan ID: 4 8 9 11 14 15 16 17 18 19 20 22 23 24 25 26 27 28 29 30; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-QOS=1.1;CM-VER=3.1;
22:25:10 Mon Nov 27 2023	Notice (6)	CM-STATUS message sent. Event Type Code: 1; Chan ID: 31 32; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-QOS=1.1;CM-VER=3.1;
22:25:22 Mon Nov 27 2023	Warning (5)	MDD message timeout;CM-QOS=1.1;CM-VER=3.1;
22:25:29 Mon Nov 27 2023	Notice (6)	CM-STATUS message sent. Event Type Code: 4; Chan ID: 4 8 9 11 14 15 16 17 18 19 20 22 23 24 25 26 27 28 29 30; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-QOS=1.1;CM-VER=3.1;
22:25:32 Mon Nov 27 2023	Warning (5)	MDD message timeout;CM-QOS=1.1;CM-VER=3.1;
22:25:38 Mon Nov 27 2023	Notice (6)	CM-STATUS message sent. Event Type Code: 1; Chan ID: 31 32; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-QOS=1.1;CM-VER=3.1;
22:25:45 Mon Nov 27 2023	Notice (6)	CM-STATUS message sent. Event Type Code: 4; Chan ID: 4 8 9 11 14 15 16 17 18 19 20 22 23 24 25 26 27 28 29 30; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-QOS=1.1;CM-VER=3.1;
22:25:46 Mon Nov 27 2023	Warning (5)	MDD message timeout;CM-QOS=1.1;CM-VER=3.1;
22:25:57 Mon Nov 27 2023	Notice (6)	CM-STATUS message sent. Event Type Code: 1; Chan ID: 27 31 32; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-QOS=1.1;CM-VER=3.1;
22:26:14 Mon Nov 27 2023	Warning (5)	MDD message timeout;CM-QOS=1.1;CM-VER=3.1;
22:26:16 Mon Nov 27 2023	Notice (6)	CM-STATUS message sent. Event Type Code: 1; Chan ID: 31 32; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-QOS=1.1;CM-VER=3.1;
22:26:24 Mon Nov 27 2023	Warning (5)	MDD message timeout;CM-QOS=1.1;CM-VER=3.1;
22:26:26 Mon Nov 27 2023	Notice (6)	CM-STATUS message sent. Event Type Code: 4; Chan ID: 4 8 9 11 14 15 16 17 18 19 20 22 23 24 25 26 27 28 29 30; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-QOS=1.1;CM-VER=3.1;
22:26:30 Mon Nov 27 2023	Warning (5)	MDD message timeout;CM-QOS=1.1;CM-VER=3.1;
22:26:31 Mon Nov 27 2023	Notice (6)	CM-STATUS message sent. Event Type Code: 2; Chan ID: 29 31 32; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-QOS=1.1;CM-VER=3.1;
22:26:31 Mon Nov 27 2023	Notice (6)	CM-STATUS message sent. Event Type Code: 1; Chan ID: 29 30 31 32; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-QOS=1.1;CM-VER=3.1;
22:26:34 Mon Nov 27 2023	Warning (5)	MDD message timeout;CM-QOS=1.1;CM-VER=3.1;
22:26:35 Mon Nov 27 2023	Notice (6)	CM-STATUS message sent. Event Type Code: 2; Chan ID: 29 31 32; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-QOS=1.1;CM-VER=3.1;
22:26:41 Mon Nov 27 2023	Notice (6)	CM-STATUS message sent. Event Type Code: 1; Chan ID: 29 31 32; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-QOS=1.1;CM-VER=3.1;
22:26:42 Mon Nov 27 2023	Warning (5)	MDD message timeout;CM-QOS=1.1;CM-VER=3.1;
22:26:43 Mon Nov 27 2023	Notice (6)	CM-STATUS message sent. Event Type Code: 2; Chan ID: 28 29 31 32; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-QOS=1.1;CM-VER=3.1;
22:26:52 Mon Nov 27 2023	Warning (5)	MDD message timeout;CM-QOS=1.1;CM-VER=3.1;
22:26:55 Mon Nov 27 2023	Notice (6)	CM-STATUS message sent. Event Type Code: 4; Chan ID: 4 8 9 11 14 15 16 17 18 19 20 22 23 24 25 26 27 28 29 30; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-QOS=1.1;CM-VER=3.1;
22:27:02 Mon Nov 27 2023	Notice (6)	CM-STATUS message sent. Event Type Code: 5; Chan ID: 1 2 3 4 5 6 7 8 9 10 11 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-QOS=1.1;CM-VER=
22:27:04 Mon Nov 27 2023	Warning (5)	MDD message timeout;CM-QOS=1.1;CM-VER=3.1;
22:27:07 Mon Nov 27 2023	Notice (6)	CM-STATUS message sent. Event Type Code: 2; Chan ID: 31 32; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-QOS=1.1;CM-VER=3.1;
22:27:08 Mon Nov 27 2023	Warning (5)	MDD message timeout;CM-QOS=1.1;CM-VER=3.1;
22:27:08 Mon Nov 27 2023	Notice (6)	CM-STATUS message sent. Event Type Code: 1; Chan ID: 31 32; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-QOS=1.1;CM-VER=3.1;
22:27:40 Mon Nov 27 2023	Warning (5)	MDD message timeout;CM-QOS=1.1;CM-VER=3.1;
22:27:52 Mon Nov 27 2023	Notice (6)	CM-STATUS message sent. Event Type Code: 4; Chan ID: 27 29; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-QOS=1.1;CM-VER=3.1;
22:27:56 Mon Nov 27 2023	Warning (5)	MDD message timeout;CM-QOS=1.1;CM-VER=3.1;
22:28:02 Mon Nov 27 2023	Notice (6)	CM-STATUS message sent. Event Type Code: 4; Chan ID: 27 29; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-QOS=1.1;CM-VER=3.1;
22:28:14 Mon Nov 27 2023	Warning (5)	MDD message timeout;CM-QOS=1.1;CM-VER=3.1;
22:28:37 Mon Nov 27 2023	Notice (6)	CM-STATUS message sent. Event Type Code: 4; Chan ID: 27 29; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-QOS=1.1;CM-VER=3.1;
22:28:56 Mon Nov 27 2023	Warning (5)	MDD message timeout;CM-QOS=1.1;CM-VER=3.1;
22:29:04 Mon Nov 27 2023	Notice (6)	CM-STATUS message sent. Event Type Code: 4; Chan ID: 27 29 30; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-QOS=1.1;CM-VER=3.1;
22:29:06 Mon Nov 27 2023	Warning (5)	MDD message timeout;CM-QOS=1.1;CM-VER=3.1;
22:29:19 Mon Nov 27 2023	Notice (6)	CM-STATUS message sent. Event Type Code: 4; Chan ID: 27 29 30; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-QOS=1.1;CM-VER=3.1;
22:29:32 Mon Nov 27 2023	Warning (5)	MDD message timeout;CM-QOS=1.1;CM-VER=3.1;
22:29:49 Mon Nov 27 2023	Notice (6)	CM-STATUS message sent. Event Type Code: 4; Chan ID: 27 29 30; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-QOS=1.1;CM-VER=3.1;
22:29:52 Mon Nov 27 2023	Warning (5)	MDD message timeout;CM-QOS=1.1;CM-VER=3.1;
22:29:55 Mon Nov 27 2023	Notice (6)	CM-STATUS message sent. Event Type Code: 4; Chan ID: 27 29 30; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-QOS=1.1;CM-VER=3.1;
22:30:04 Mon Nov 27 2023	Warning (5)	MDD message timeout;CM-QOS=1.1;CM-VER=3.1;
22:30:21 Mon Nov 27 2023	Notice (6)	CM-STATUS message sent. Event Type Code: 4; Chan ID: 27 29 30; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-QOS=1.1;CM-VER=3.1;
22:30:28 Mon Nov 27 2023	Warning (5)	MDD message timeout;CM-QOS=1.1;CM-VER=3.1;
22:30:31 Mon Nov 27 2023	Notice (6)	CM-STATUS message sent. Event Type Code: 4; Chan ID: 27 29 30; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-QOS=1.1;CM-VER=3.1;
22:30:46 Mon Nov 27 2023	Warning (5)	MDD message timeout;CM-QOS=1.1;CM-VER=3.1;
22:30:46 Mon Nov 27 2023	Notice (6)	CM-STATUS message sent. Event Type Code: 4; Chan ID: 27 28 29 30; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-QOS=1.1;CM-VER=3.1;
22:30:50 Mon Nov 27 2023	Warning (5)	MDD message timeout;CM-QOS=1.1;CM-VER=3.1;
22:30:54 Mon Nov 27 2023	Notice (6)	CM-STATUS message sent. Event Type Code: 4; Chan ID: 27 28 29 30; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-QOS=1.1;CM-VER=3.1;
22:31:08 Mon Nov 27 2023	Warning (5)	MDD message timeout;CM-QOS=1.1;CM-VER=3.1;
22:31:13 Mon Nov 27 2023	Notice (6)	CM-STATUS message sent. Event Type Code: 2; Chan ID: 29; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-QOS=1.1;CM-VER=3.1;
22:31:22 Mon Nov 27 2023	Notice (6)	CM-STATUS message sent. Event Type Code: 4; Chan ID: 27 28; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-QOS=1.1;CM-VER=3.1;
22:31:24 Mon Nov 27 2023	Warning (5)	MDD message timeout;CM-QOS=1.1;CM-VER=3.1;
22:31:25 Mon Nov 27 2023	Notice (6)	CM-STATUS message sent. Event Type Code: 2; Chan ID: 29; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-QOS=1.1;CM-VER=3.1;
22:31:32 Mon Nov 27 2023	Notice (6)	CM-STATUS message sent. Event Type Code: 1; Chan ID: 29; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-QOS=1.1;CM-VER=3.1;
22:31:36 Mon Nov 27 2023	Warning (5)	MDD message timeout;CM-QOS=1.1;CM-VER=3.1;
22:31:39 Mon Nov 27 2023	Notice (6)	CM-STATUS message sent. Event Type Code: 2; Chan ID: 29; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-QOS=1.1;CM-VER=3.1;
22:31:39 Mon Nov 27 2023	Notice (6)	CM-STATUS message sent. Event Type Code: 1; Chan ID: 29; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-QOS=1.1;CM-VER=3.1;
22:31:46 Mon Nov 27 2023	Notice (6)	CM-STATUS message sent. Event Type Code: 4; Chan ID: 27 28 29 30; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-QOS=1.1;CM-VER=3.1;
22:31:52 Mon Nov 27 2023	Warning (5)	MDD message timeout;CM-QOS=1.1;CM-VER=3.1;

Startup Step	Status	Comment
Acquire Downstream Channel	519000000 Hz	Locked
Upstream Connection	OK	Operational
Boot State	OK	Operational
Configuration File	OK
Security	Enabled	BPI+

Connection Status

System Up Time	0 days 00h:54m:15s
Network Access	Allowed

Downstream Bonded Channels

Channel	Lock Status	Modulation	Channel ID	Freq. (MHz)	Pwr (dBmV)	SNR (dB)	Corrected	Uncorrected
1	Locked	QAM256	12	519.0	-7.4	40.0	44	134
2	Locked	QAM256	1	453.0	-1.4	43.3	5124	18315
3	Locked	QAM256	2	459.0	-0.3	44.1	4816	17792
4	Locked	QAM256	3	465.0	-0.8	43.9	5102	18206
5	Locked	QAM256	4	471.0	-1.1	43.8	5005	16219
6	Locked	QAM256	5	477.0	-2.5	42.9	5300	17519
7	Locked	QAM256	6	483.0	-3.8	42.3	35552	44736
8	Locked	QAM256	7	489.0	-1.6	43.6	4632	15976
9	Locked	QAM256	8	495.0	-2.1	43.3	2393	10816
10	Locked	QAM256	9	501.0	-3.7	42.5	5508	25874
11	Locked	QAM256	10	507.0	-4.7	41.9	5726	14412
12	Locked	QAM256	11	513.0	-6.6	40.7	2138	9654
13	Locked	QAM256	13	525.0	-8.0	39.7	9050	17466
14	Locked	QAM256	14	531.0	-10.1	37.6	3570	15913
15	Locked	QAM256	15	537.0	-12.9	35.2	5961	15798
16	Locked	QAM256	16	543.0	-14.9	33.3	2542	10842
17	Locked	QAM256	17	549.0	-18.7	29.3	23250	8136
18	Locked	QAM256	18	555.0	-16.8	31.5	1750	7624
19	Locked	QAM256	19	561.0	-15.5	32.8	8688	30964
20	Locked	QAM256	20	567.0	-15.0	33.4	34385	61975
21	Locked	QAM256	21	573.0	-14.4	34.0	30446	48491
22	Locked	QAM256	22	579.0	-18.9	29.1	22765	7140
23	Locked	QAM256	23	585.0	-16.9	30.8	759	3057
24	Locked	QAM256	24	591.0	-16.4	31.0	1395	5967
25	Locked	QAM256	25	597.0	-14.9	31.4	3746	7762
26	Locked	QAM256	26	603.0	-17.3	27.4	1593402	7875
27	Locked	QAM256	27	609.0	-21.8	26.3	83255038	51129424
28	Locked	QAM256	28	615.0	-20.9	27.2	15639628	3335211
29	Locked	QAM256	29	621.0	-18.7	28.9	3347116	11414003
30	Locked	QAM256	30	627.0	-15.5	31.4	3287907	5981617

Upstream Bonded Channels

Channel	Lock Status	Channel Type	Channel ID	Symb. Rate (Ksym/sec)	Freq. (MHz)	Pwr (dBmV)
1	Locked	SC-QAM	1	5120	16.4	43.0
2	Locked	SC-QAM	2	5120	22.8	43.3
3	Locked	SC-QAM	3	5120	29.2	46.0
4	Locked	SC-QAM	4	5120	35.6	48.3

Responses

Accepted Solution

EG

Expert

•

110.3K Messages

1 year ago

The downstream power begins to go out of spec starting around channel 13, and it goes way out of spec on the higher-frequency channels. The SNR's are out of spec on the higher channels as well. It appears that you have a condition on your line somewhere that is known as excessive "Tilt". That is where the higher frequencies roll-off much more than they should. It is typically compensated for. Something is awry with the line(s) somewhere. There are a few causes. You may need a tech out to investigate this one but here is some stuff that you can try;

In an effort to try to obtain better connectivity, check to see if there are any excess/unneeded coax cable splitters in the line leading to the modem that can be eliminated/re-configured. Any splitters that remain should be high quality and cable rated for 5-1002 MHz, bi-directional, and no gold colored garbage from Home Depot, Target, Wal-Mart, etc. Splitters should be swapped with known to be good / new ones to test.

Also check the coax cable for any damage such as cuts, nicks, abrasions, kinks, sharp bends, etc.

If there aren't any unneeded splitters that can be eliminated and if your coax wiring setup can't be reconfigured so that there is a single two-way splitter connected directly off of the drop from the street / pole with one port feeding the modem and the other port feeding the rest of the house/equipment with additional splits as needed and you've checked all the wiring and fittings for integrity and tightness and refresh them by taking them apart then check for and clean off any corrosion / oxidation on the center wire and put them back together again, then perhaps it's best to book a tech visit to investigate and correct.

Good luck with it !

(edited)

Accepted Solution

nimmock

3 Messages

1 year ago

Appreciate your input you two! They sent a tech out today who found an issue with the box outside, and after replacing a bunch of old cables we're all back in business!

XfinityVianney

Official Employee

•

2.2K Messages

Hi, @nimmock. It's great to hear the tech got you all squared away. We have some awesome folks in the field, and we can always count on them to do a great job. I want to also thank our expert @EG for jumping in, and @BruceW for their input. We have a great community here, and we are glad to have folks are willing to lend a hand. If you need anything else @nimmock, you know where to find us.

I am an Official Xfinity Employee.
Official Employees are from multiple teams within Xfinity: CARE, Product, Leadership.
We ask that you post publicly so people with similar questions may benefit from the conversation.
Was your question answered? Please, mark a reply as the Accepted Answer. tick

1 year ago

nimmock

3 Messages

1 year ago

Just so you can see what I'm working with here, this is what I get to enjoy:

BruceW

Gold Problem Solver

•

26.4K Messages

1 year ago

... gigabit speeds ... I've factory reset my MB8600 ...

Perhaps not the source of the problem, but note that the MB8600 is not approved for use with Gigabit service. Comcast rates the MB8600 for use with plan speeds "Up to 949 Mbps". Using devices on speed tiers for which they are not approved tends to produce unexpected results. Consider picking up one of the devices on https://www.xfinity.com/support/devices/ that is approved for Gigabit service, or dropping back to a lower tier.

Besides that, the connection stats are terrible. All the channels have too many errors for less than an hour of operation, the downstream power levels above 513 MHz are too low, and two of the upstream channels are borderline (too high). They're so bad even a Comcast tech should be able to see that there is a problem.

Network connection problems that affect both Ethernet and Wifi devices are often due to poor coax connections or damaged coax cable, usually in or near your home. Running the cable through a surge protector, a defective splitter, or too many splitters can cause signal problems as well. If there is an amplifier in the line make sure it's getting power.

If you want to troubleshoot this yourself, please see Internet Troubleshooting Tips. If you can't find the problem or you'd rather have Comcast take care of it and an employee does not respond to your message here, call them at the phone number on your bill or 1-800-Comcast, or use one of the options on https://www.xfinity.com/support/contact-us/. It's not likely they can fix the problem remotely. If not, insist they send a tech out to identify the cause and correct it.

If the tech finds bad coax, splitters, amplifiers, or connections in your home (even if Comcast originally supplied them) you'll probably have to pay for the visit (approx $100) unless you have their Service Protection Plan ( https://www.xfinity.com/support/articles/service-protection-plan, closed to customers that don't already have it). If the trouble is due to a faulty Comcast rental device or anything outside your home you shouldn't be charged.

Please be aware that there are 2 kinds of responses in this Forum: Replies and Comments. When you Comment on a post by scrolling down to "Comment on this post here...", I am notified of your response. But if you select Reply, I am NOT notified and may not be aware of your response.

EG

Expert

•

110.3K Messages

1 year ago

@nimmock

Glad that you got it squared away ! Happy surfing !

(edited)

Your Home Network

nimmock

Issues With Speed and Packet Loss

EG

nimmock

XfinityVianney

nimmock

BruceW

Please be aware that there are 2 kinds of responses in this Forum: Replies and Comments. When you Comment on a post by scrolling down to "Comment on this post here...", I am notified of your response. But if you select Reply, I am NOT notified and may not be aware of your response.

EG

New to the Community?