user_m145's profile

Frequent Visitor

 • 

16 Messages

Thursday, December 5th, 2024 11:16 AM

MDD message timeouts and packet loss, ongoing issue.

This is an ongoing issue since October, I'd strongly urge everyone to read through the post carefully to know what trouble shooting steps have already been taken. I'd also like to make it clear that I had no issues with my service prior to October. 

To summarize, this last October I began noticing issues with my upstream, the connection was unstable and showed signs of major packetloss. I took the usual troubleshooting steps like power cycling the modem and directly connecting to it, but to no avail. I also around this time contacted an xfinity agent through the app, wanting to know if they saw any issues from their end. Of the few agents I spoke with, one of them told me about some kind of maintenance going on that was causing the issue. This maintenance wasn't one of the usually scheduled ones, didn't appear on the app, and every other agent I spoke with said there wasn't any maintenance. Keep this in mind for later. I also made a post on these forums asking for assistance and posting my modem's logs. The event logs had a lot T3 timeouts as well as "Dynamic Range Window violations", it was also pointed out to me that my upstream power levels were out of spec and that I'd most likely need a technician to come out.

The first technician was very helpful, he checked all the lines both inside and outside, as well as all the fittings at the splitter. He explained things every step of the way and told us that it was most likely an issue with the line from our house to the tap. The technician ordered a crew to come out and put in a new line and said that the crews probably wouldn't connect the new line and that we'd need to have another technician come up to hook it up and check everything. A few weeks later the line crews came out and buried the new line, and apparently also connected it. This wasn't communicated to us however as they only told us our service would be out for a short time and asked before they left if we had service. Not knowing whether the new line was connected and still seeing issues we scheduled a second technician to come out.

The second technician was unfortunately far less helpful, he barely said a word and didn't really address any of our concerns. He did check the new line and confirmed it was connected, as well as checking the signal strength but didn't share if it was good or bad. He rechecked the fittings at the splitter and switched the modem to a different coaxial cable that ran to the splitter. Over all it seemed like he was rushing to get out of here, but one helpful thing he did mention was ongoing maintenance. He didn't specify anything about the maintenance other than a brief mention though. After his visit the T3 timeouts and "Dynamic Range Window violations" were no longer present and my power levels are within spec again, but I was still seeing issues with the upstream.

I should mention that throughout all of this, only the upstream had been effected. The downstream was completely stable and had no problems as far as I could tell. However within the last week or so I've begun noticing downstream issues, webpages loading slowly, high downstream packet loss, videos and streams buffering not playing correctly. This is all on top of my continuing upstream issues. All of my power levels seem to be in spec for both up and down, however I'm now receiving a ton of "MDD message timeouts" in the modem's event log. At this point I'm honestly not even sure what the issue could be on my end since we've checked and changed everything. There have been days since the previous technician visit where even the upstream is completely stable, but others where its not and now the downstream also seems to be acting up.

Earlier I mentioned being told about some kind of maintenance by both a chat agent and the second technician with no specifics, I highlighted this since I work nights and I assume that's when this maintenance is taking place as most of my connection issues seem to clear up by 11am in the morning. The issue I have though is this maintenance hasn't been communicated in any official way and I've even had xfinity agents flat out tell me there was no maintenance or that they don't know what I'm talking about. I obviously don't know for sure if this maintenance is the cause of my problems and it could very well be something else, but after having two technicians come out and check things I'm not sure what else it could be at least on my end. Below I'll post my modem power levels and logs, any help with this would be appreciated

 
Startup Procedure
Procedure Status Comment
Acquire Downstream Channel 537000000 Hz Locked
Connectivity State OK Operational
Boot State OK Operational
Security Enabled BPI+
 
Downstream Bonded Channels
Channel Lock Status Modulation Channel ID Frequency Power SNR Correctables Uncorrectables
1 Locked QAM256 28 537000000 Hz -0.4 dBmV 43.8 dB 0 0
2 Locked QAM256 13 447000000 Hz 0.4 dBmV 44.2 dB 0 0
3 Locked QAM256 14 453000000 Hz 0.3 dBmV 44.2 dB 0 0
4 Locked QAM256 15 459000000 Hz 0.1 dBmV 44.0 dB 0 0
5 Locked QAM256 16 465000000 Hz 0.0 dBmV 44.0 dB 0 0
6 Locked QAM256 17 471000000 Hz 0.1 dBmV 44.0 dB 0 0
7 Locked QAM256 18 477000000 Hz 0.2 dBmV 44.0 dB 0 0
8 Locked QAM256 19 483000000 Hz 0.2 dBmV 44.0 dB 0 0
9 Locked QAM256 20 489000000 Hz 0.2 dBmV 44.1 dB 0 0
10 Locked QAM256 21 495000000 Hz 0.3 dBmV 44.2 dB 0 0
11 Locked QAM256 22 501000000 Hz -0.1 dBmV 44.0 dB 0 0
12 Locked QAM256 23 507000000 Hz 0.3 dBmV 44.2 dB 0 0
13 Locked QAM256 24 513000000 Hz 0.0 dBmV 44.1 dB 0 0
14 Locked QAM256 25 519000000 Hz -0.1 dBmV 44.0 dB 0 0
15 Locked QAM256 26 525000000 Hz -0.3 dBmV 43.9 dB 0 0
16 Locked QAM256 27 531000000 Hz -0.4 dBmV 43.8 dB 0 0
17 Locked QAM256 29 543000000 Hz -0.3 dBmV 43.8 dB 0 0
18 Locked QAM256 30 549000000 Hz -0.2 dBmV 43.9 dB 0 0
19 Locked QAM256 31 555000000 Hz -0.2 dBmV 43.9 dB 0 0
20 Locked QAM256 32 561000000 Hz -0.1 dBmV 43.8 dB 0 0
21 Locked QAM256 33 567000000 Hz -0.3 dBmV 43.6 dB 0 0
22 Locked QAM256 34 573000000 Hz 0.1 dBmV 43.9 dB 0 0
23 Locked QAM256 35 579000000 Hz 0.1 dBmV 43.9 dB 0 0
24 Locked QAM256 36 585000000 Hz 0.0 dBmV 43.8 dB 0 0
25 Locked QAM256 37 591000000 Hz -0.2 dBmV 43.6 dB 0 0
26 Locked QAM256 38 597000000 Hz -0.2 dBmV 43.5 dB 0 0
27 Locked QAM256 39 603000000 Hz -0.5 dBmV 43.4 dB 0 0
28 Locked QAM256 40 609000000 Hz -0.5 dBmV 43.4 dB 0 0
29 Locked QAM256 41 615000000 Hz -0.5 dBmV 43.4 dB 0 0
30 Locked QAM256 42 621000000 Hz -0.7 dBmV 43.3 dB 0 0
31 Locked QAM256 43 627000000 Hz -0.7 dBmV 43.2 dB 0 0
32 Locked QAM256 44 633000000 Hz -0.7 dBmV 42.9 dB 0 0
 
Upstream Bonded Channels
Channel Lock Status US Channel Type Channel ID Symbol Rate Frequency Power
1 Locked ATDMA 17 5120 16400000 Hz 39.3 dBmV
2 Locked ATDMA 18 5120 22800000 Hz 39.5 dBmV
3 Locked ATDMA 19 5120 29200000 Hz 39.5 dBmV
4 Locked ATDMA 20 5120 35600000 Hz 39.5 dBmV
5 Not Locked Unknown 0 0 0 Hz 0.0 dBmV
6 Not Locked Unknown 0 0 0 Hz 0.0 dBmV
7 Not Locked Unknown 0 0 0 Hz 0.0 dBmV
8 Not Locked Unknown 0 0 0 Hz 0.0 dBmV
 
Downstream OFDM Channels
Channel Lock Status Profile ID Channel ID Frequency Power SNR / MER Active Subcarrier
Number Range
Unerrored
Codewords
Correctable
Codewords
Uncorrectable
Codewords
1 Locked 0 ,1 ,2 ,3 193 690000000 Hz -0.3 dBmV 42.6 dB 328 ~ 3767 1221269860 1106759838 2083
2 Locked 0 ,1 ,2 ,3 194 957000000 Hz -3.5 dBmV 41.0 dB 148 ~ 3947 1207577874 520732433 657217722
 
Upstream OFDMA Channels
Channel Lock Status Modulation / Profile ID Channel ID Frequency Power
1 Not Locked 0 0 0 Hz 0 dBmV
2 Not Locked 0 0 0 Hz 0 dBmV

 
Time Priority Description
Thu Dec 05 06:07:53 2024 (Notice (6)) CM-STATUS message sent. Event Type Code: 4; Chan ID: 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
Thu Dec 05 06:07:23 2024 (Notice (6)) CM-STATUS message sent. Event Type Code: 1; Chan ID: 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
Thu Dec 05 06:07:17 2024 (Warning (5)) MDD message timeout;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
Thu Dec 05 06:00:15 2024 (Notice (6)) CM-STATUS message sent. Event Type Code: 4; Chan ID: 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
Thu Dec 05 06:00:13 2024 (Warning (5)) MDD message timeout;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
Thu Dec 05 05:56:34 2024 (Notice (6)) CM-STATUS message sent. Event Type Code: 4; Chan ID: 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
Thu Dec 05 05:56:12 2024 (Warning (5)) MDD message timeout;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
Thu Dec 05 05:56:01 2024 (Notice (6)) CM-STATUS message sent. Event Type Code: 4; Chan ID: 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
Thu Dec 05 05:55:10 2024 (Warning (5)) MDD message timeout;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
Thu Dec 05 05:51:55 2024 (Notice (6)) CM-STATUS message sent. Event Type Code: 4; Chan ID: 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
Thu Dec 05 05:51:33 2024 (Notice (6)) CM-STATUS message sent. Event Type Code: 1; Chan ID: 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
Thu Dec 05 05:51:24 2024 (Warning (5)) MDD message timeout;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
Thu Dec 05 05:47:09 2024 (Notice (6)) CM-STATUS message sent. Event Type Code: 4; Chan ID: 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
Thu Dec 05 05:46:50 2024 (Warning (5)) MDD message timeout;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
Thu Dec 05 05:45:05 2024 (Notice (6)) CM-STATUS message sent. Event Type Code: 4; Chan ID: 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
Thu Dec 05 05:44:40 2024 (Notice (6)) CM-STATUS message sent. Event Type Code: 1; Chan ID: 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
Thu Dec 05 05:44:33 2024 (Warning (5)) MDD message timeout;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
Thu Dec 05 05:39:58 2024 (Notice (6)) CM-STATUS message sent. Event Type Code: 4; Chan ID: 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
Thu Dec 05 05:39:46 2024 (Warning (5)) MDD message timeout;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
Thu Dec 05 05:39:29 2024 (Notice (6)) CM-STATUS message sent. Event Type Code: 4; Chan ID: 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
Thu Dec 05 05:39:14 2024 (Notice (6)) CM-STATUS message sent. Event Type Code: 1; Chan ID: 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
Thu Dec 05 05:38:51 2024 (Notice (6)) CM-STATUS message sent. Event Type Code: 3; Chan ID: N/A; DSID: o; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
Thu Dec 05 05:38:44 2024 (Warning (5)) MDD message timeout;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
Thu Dec 05 05:37:25 2024 (Notice (6)) CM-STATUS message sent. Event Type Code: 4; Chan ID: 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
Thu Dec 05 05:37:03 2024 (Notice (6)) CM-STATUS message sent. Event Type Code: 1; Chan ID: 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
Thu Dec 05 05:36:58 2024 (Warning (5)) MDD message timeout;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
Thu Dec 05 05:36:53 2024 (Notice (6)) CM-STATUS message sent. Event Type Code: 3; Chan ID: N/A; DSID: o; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
Thu Dec 05 05:36:52 2024 (Notice (6)) CM-STATUS message sent. Event Type Code: 4; Chan ID: 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
Thu Dec 05 05:36:44 2024 (Warning (5)) MDD message timeout;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
Thu Dec 05 05:36:37 2024 (Notice (6)) CM-STATUS message sent. Event Type Code: 4; Chan ID: 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
Thu Dec 05 05:36:19 2024 (Notice (6)) CM-STATUS message sent. Event Type Code: 1; Chan ID: 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
Thu Dec 05 05:36:18 2024 (Warning (5)) MDD message timeout;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
Thu Dec 05 05:35:53 2024 (Notice (6)) CM-STATUS message sent. Event Type Code: 4; Chan ID: 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
Thu Dec 05 05:35:32 2024 (Warning (5)) MDD message timeout;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
Thu Dec 05 05:32:05 2024 (Notice (6)) CM-STATUS message sent. Event Type Code: 4; Chan ID: 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
Thu Dec 05 05:31:22 2024 (Warning (5)) MDD message timeout;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
Thu Dec 05 05:24:58 2024 (Notice (6)) CM-STATUS message sent. Event Type Code: 4; Chan ID: 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
Thu Dec 05 05:24:23 2024 (Warning (5)) MDD message timeout;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
Thu Dec 05 05:24:20 2024 (Notice (6)) CM-STATUS message sent. Event Type Code: 4; Chan ID: 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
Thu Dec 05 05:24:03 2024 (Warning (5)) MDD message timeout;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;

Official Employee

 • 

1.4K Messages

8 days ago

 

user_m145 Good morning! We appreciate you taking the time to share your experience, and reaching out to our Community Forums Team. Having reliable services are so important, especially when we rely on internet for so much of our daily routine now. I'd be happy happy to help you identify, what the next best step would be to resolve the upstream issue. Since it's been a couple of days, are you still experiencing this issue? 

 

forum icon

New to the Community?

Start Here