Visitor
•
2 Messages
MDD message timeout - Internet Drops Out All The Time
I have been dealing with random internet dropouts for the last 6 months. The internet just disconnects for 30 sec or so. It happens roughly every hour and is super frustrating.
I had several Xfinity technicians come to my house but none was able to fix the problem. Here is what the Xfinity technicians have done so far:
- Replaced various splitters and connectors
- Replaced entire cable from the street pole to the house
- Suggested to get a new modem, specifically suggested Netgear CM 1200 (previously had a Netgear CM 700)
- Replaced TV box (not sure why they did that)
I also tried several things myself:
- Connected laptop directly to modem via ethernet cable, which didn't fix the problem (conclusion: the router cannot be the issue)
- Connected modem directly with the main cable coming from the street pole (no splitters involved)
- Tried different modem locations at different power outlets
None of the above fixed the issue. At this point I'm convinced that the issue must be on the Xfinity side, i.e., the signal coming to our house. Suspiciously, the issue started when XFinity upgraded the internet speeds in my area. The last Xfinity technician (number 4 in the last 2 months) that came to my house mentioned that they changed from satellite to fiber in my area to increase speeds. The technician also promised that he would refer my case to the line techs and they would check the line and distribution node. But I haven't heard back from Xfinity and the issue obviously still persists.
The issue is super frustrating and I'm very disappointed with the lack of care, expertise, and quality of Xfinity. I've had Xfinity for many many years but at this point I'm really considering trying out AT&T. Anyways, maybe someone has a good suggestion what I could do.
Here is a recent log and connection status from my CM 1200 modem (every time "MDD message timeout" happens, the internet drops out):
Time |
Priority |
Description |
Tue Jan 24 22:22:10 2023 |
Notice (6) |
CM-STATUS message sent. Event Type Code: 4; Chan ID: 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 193; 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; |
Tue Jan 24 22:21:29 2023 |
Warning (5) |
MDD message timeout;CM-MAC=[];CMTS-MAC=[];CM-QOS=1.1;CM-VER=3.1; |
Tue Jan 24 20:48:09 2023 |
Notice (6) |
CM-STATUS message sent. Event Type Code: 4; Chan ID: 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 193; 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; |
Tue Jan 24 20:47:28 2023 |
Warning (5) |
MDD message timeout;CM-MAC=[];CMTS-MAC=[];CM-QOS=1.1;CM-VER=3.1; |
Tue Jan 24 20:26:58 2023 |
Notice (6) |
CM-STATUS message sent. Event Type Code: 4; Chan ID: 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 193; 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; |
Tue Jan 24 20:26:19 2023 |
Warning (5) |
MDD message timeout;CM-MAC=[];CMTS-MAC=[];CM-QOS=1.1;CM-VER=3.1; |
Tue Jan 24 18:33:21 2023 |
Notice (6) |
CM-STATUS message sent. Event Type Code: 4; Chan ID: 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 193; 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; |
Tue Jan 24 18:32:40 2023 |
Warning (5) |
MDD message timeout;CM-MAC=[];CMTS-MAC=[];CM-QOS=1.1;CM-VER=3.1; |
Tue Jan 24 15:45:28 2023 |
Notice (6) |
CM-STATUS message sent. Event Type Code: 4; Chan ID: 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 193; 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; |
Tue Jan 24 15:44:46 2023 |
Warning (5) |
MDD message timeout;CM-MAC=[];CMTS-MAC=[];CM-QOS=1.1;CM-VER=3.1; |
Tue Jan 24 15:24:08 2023 |
Notice (6) |
CM-STATUS message sent. Event Type Code: 4; Chan ID: 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 193; 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; |
Tue Jan 24 15:23:27 2023 |
Warning (5) |
MDD message timeout;CM-MAC=[];CMTS-MAC=[];CM-QOS=1.1;CM-VER=3.1; |
Tue Jan 24 14:54:06 2023 |
Notice (6) |
CM-STATUS message sent. Event Type Code: 4; Chan ID: 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 193; 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; |
Tue Jan 24 14:53:27 2023 |
Warning (5) |
MDD message timeout;CM-MAC=[];CMTS-MAC=[];CM-QOS=1.1;CM-VER=3.1; |
Tue Jan 24 14:44:59 2023 |
Notice (6) |
CM-STATUS message sent. Event Type Code: 4; Chan ID: 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=[];CMTS-MAC=v;CM-QOS=1.1;CM-VER=3.1; |
Tue Jan 24 14:44:18 2023 |
Warning (5) |
MDD message timeout;CM-MAC=[];CMTS-MAC=[];CM-QOS=1.1;CM-VER=3.1; |
Tue Jan 24 13:27:22 2023 |
Notice (6) |
CM-STATUS message sent. Event Type Code: 4; Chan ID: 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 193; 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; |
Tue Jan 24 13:26:41 2023 |
Warning (5) |
MDD message timeout;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1; |
Tue Jan 24 12:49:25 2023 |
Notice (6) |
CM-STATUS message sent. Event Type Code: 4; Chan ID: 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 193; 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; |
Tue Jan 24 12:48:46 2023 |
Warning (5) |
MDD message timeout;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1; |
Tue Jan 24 11:28:29 2023 |
Notice (6) |
CM-STATUS message sent. Event Type Code: 4; Chan ID: 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 193; 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; |
Tue Jan 24 11:27:48 2023 |
Warning (5) |
MDD message timeout;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1; |
Tue Jan 24 10:35:52 2023 |
Notice (6) |
CM-STATUS message sent. Event Type Code: 4; Chan ID: 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 193; 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; |
Tue Jan 24 10:35:11 2023 |
Warning (5) |
MDD message timeout;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1; |
Tue Jan 24 09:50:24 2023 |
Notice (6) |
CM-STATUS message sent. Event Type Code: 4; Chan ID: 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 193; 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; |
Tue Jan 24 09:49:43 2023 |
Warning (5) |
MDD message timeout;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1; |
Tue Jan 24 09:47:18 2023 |
Notice (6) |
CM-STATUS message sent. Event Type Code: 4; Chan ID: 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 193; 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; |
Tue Jan 24 09:46:39 2023 |
Warning (5) |
MDD message timeout;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1; |
Tue Jan 24 09:41:02 2023 |
Notice (6) |
CM-STATUS message sent. Event Type Code: 4; Chan ID: 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 193; 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; |
Tue Jan 24 09:40:23 2023 |
Warning (5) |
MDD message timeout;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1; |
Tue Jan 24 07:39:07 2023 |
Notice (6) |
CM-STATUS message sent. Event Type Code: 4; Chan ID: 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 193; 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; |
Tue Jan 24 07:38:26 2023 |
Warning (5) |
MDD message timeout;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1; |
Tue Jan 24 07:21:44 2023 |
Notice (6) |
CM-STATUS message sent. Event Type Code: 4; Chan ID: 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 193; 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; |
Tue Jan 24 07:21:05 2023 |
Warning (5) |
MDD message timeout;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1; |
Tue Jan 24 06:54:28 2023 |
Notice (6) |
CM-STATUS message sent. Event Type Code: 4; Chan ID: 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 193; 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; |
Tue Jan 24 06:53:47 2023 |
Warning (5) |
MDD message timeout;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1; |
Tue Jan 24 04:32:07 2023 |
Notice (6) |
CM-STATUS message sent. Event Type Code: 4; Chan ID: 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 193; 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; |
Tue Jan 24 04:31:25 2023 |
Warning (5) |
MDD message timeout;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1; |
Tue Jan 24 02:03:28 2023 |
Notice (6) |
CM-STATUS message sent. Event Type Code: 4; Chan ID: 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 193; 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; |
Tue Jan 24 02:02:47 2023 |
Warning (5) |
MDD message timeout;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1; |
Procedure |
Status |
Comment |
Acquire Downstream Channel |
591000000 Hz |
Locked |
Connectivity State |
OK |
Operational |
Boot State |
OK |
Operational |
Security |
Enabled |
BPI+ |
IP Provisioning Mode |
Honor MDD |
honorMdd(4) |
Downstream Bonded Channels
Channel |
Lock Status |
Modulation |
Channel ID |
Frequency |
Power |
SNR |
Correctables |
Uncorrectables |
1 |
Locked |
QAM256 |
28 |
591000000 Hz |
11.2 dBmV |
45.8 dB |
126 |
417 |
2 |
Locked |
QAM256 |
13 |
501000000 Hz |
11.4 dBmV |
45.3 dB |
1283 |
1870 |
3 |
Locked |
QAM256 |
14 |
507000000 Hz |
11.5 dBmV |
46 dB |
1200 |
3690 |
4 |
Locked |
QAM256 |
15 |
513000000 Hz |
11.5 dBmV |
46.3 dB |
1385 |
3882 |
5 |
Locked |
QAM256 |
16 |
519000000 Hz |
11.5 dBmV |
46.2 dB |
1334 |
3618 |
6 |
Locked |
QAM256 |
17 |
525000000 Hz |
11.4 dBmV |
45.7 dB |
58 |
351 |
7 |
Locked |
QAM256 |
18 |
531000000 Hz |
11.3 dBmV |
46.2 dB |
1517 |
3567 |
8 |
Locked |
QAM256 |
19 |
537000000 Hz |
11.4 dBmV |
46.2 dB |
1304 |
3430 |
9 |
Locked |
QAM256 |
20 |
543000000 Hz |
11.5 dBmV |
46.3 dB |
1261 |
3638 |
10 |
Locked |
QAM256 |
21 |
549000000 Hz |
11.3 dBmV |
46.2 dB |
1543 |
3842 |
11 |
Locked |
QAM256 |
22 |
555000000 Hz |
11.3 dBmV |
46 dB |
1289 |
3576 |
12 |
Locked |
QAM256 |
23 |
561000000 Hz |
11.4 dBmV |
46 dB |
1264 |
3367 |
13 |
Locked |
QAM256 |
24 |
567000000 Hz |
11.2 dBmV |
46 dB |
1602 |
4068 |
14 |
Locked |
QAM256 |
25 |
573000000 Hz |
11 dBmV |
45.8 dB |
1655 |
5289 |
15 |
Locked |
QAM256 |
26 |
579000000 Hz |
11.4 dBmV |
46 dB |
1450 |
3927 |
16 |
Locked |
QAM256 |
27 |
585000000 Hz |
11.3 dBmV |
45.9 dB |
1453 |
3902 |
17 |
Locked |
QAM256 |
29 |
597000000 Hz |
11.3 dBmV |
45.8 dB |
1551 |
4232 |
18 |
Locked |
QAM256 |
30 |
603000000 Hz |
11.2 dBmV |
45.7 dB |
1385 |
3979 |
19 |
Locked |
QAM256 |
31 |
609000000 Hz |
11.1 dBmV |
45.8 dB |
1560 |
3910 |
20 |
Locked |
QAM256 |
32 |
615000000 Hz |
11.2 dBmV |
45.8 dB |
1583 |
4518 |
21 |
Locked |
QAM256 |
33 |
621000000 Hz |
11.4 dBmV |
45.8 dB |
1607 |
5518 |
22 |
Locked |
QAM256 |
34 |
627000000 Hz |
11.3 dBmV |
45.6 dB |
1728 |
5693 |
23 |
Locked |
QAM256 |
35 |
633000000 Hz |
11.4 dBmV |
45.7 dB |
1464 |
3324 |
24 |
Locked |
QAM256 |
36 |
639000000 Hz |
11.7 dBmV |
45.7 dB |
1548 |
4985 |
25 |
Locked |
QAM256 |
37 |
645000000 Hz |
11.7 dBmV |
45.8 dB |
1682 |
5370 |
26 |
Locked |
QAM256 |
38 |
651000000 Hz |
11.8 dBmV |
45.9 dB |
1720 |
4462 |
27 |
Locked |
QAM256 |
39 |
657000000 Hz |
11.9 dBmV |
46 dB |
1470 |
3353 |
28 |
Locked |
QAM256 |
40 |
663000000 Hz |
12.2 dBmV |
46 dB |
1667 |
5835 |
29 |
Locked |
QAM256 |
41 |
669000000 Hz |
12.2 dBmV |
46.1 dB |
1615 |
4043 |
30 |
Locked |
QAM256 |
42 |
675000000 Hz |
12.2 dBmV |
45.2 dB |
1468 |
3645 |
31 |
Locked |
QAM256 |
43 |
681000000 Hz |
12.4 dBmV |
46.1 dB |
1450 |
3831 |
32 |
Locked |
QAM256 |
44 |
687000000 Hz |
12.6 dBmV |
46.1 dB |
1332 |
3483 |
Upstream Bonded Channels
Channel |
Lock Status |
US Channel Type |
Channel ID |
Symbol Rate |
Frequency |
Power |
1 |
Locked |
ATDMA |
17 |
5120 Ksym/sec |
16400000 Hz |
44.5 dBmV |
2 |
Locked |
ATDMA |
18 |
5120 Ksym/sec |
22800000 Hz |
43.8 dBmV |
3 |
Locked |
ATDMA |
19 |
5120 Ksym/sec |
29200000 Hz |
43 dBmV |
4 |
Locked |
ATDMA |
20 |
5120 Ksym/sec |
35600000 Hz |
42.5 dBmV |
5 |
Not Locked |
Unknown |
0 |
0 Ksym/sec |
0 Hz |
0.0 dBmV |
6 |
Not Locked |
Unknown |
0 |
0 Ksym/sec |
0 Hz |
0.0 dBmV |
7 |
Not Locked |
Unknown |
0 |
0 Ksym/sec |
0 Hz |
0.0 dBmV |
8 |
Not Locked |
Unknown |
0 |
0 Ksym/sec |
0 Hz |
0.0 dBmV |
Downstream OFDM Channels
Channel |
Lock Status |
Modulation / 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 |
957000000 Hz |
11.4 dBmV |
44.8 dB |
148 ~ 3947 |
1696812891 |
13934641 |
2307 |
2 |
Not Locked |
0 |
0 |
0 Hz |
0 dBmV |
0.0 dB |
0 ~ 4095 |
0 |
0 |
0 |
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 |
Also: I found several recent posts of people that have the same or similar issue. Here are some examples:
- https://www.reddit.com/r/Comcast_Xfinity/comments/zemwz2/mdd_message_timeout/
- https://forums.xfinity.com/conversations/your-home-network/semifrequent-mdd-message-timeout-which-leads-to-high-packet-loss-events-disconnects/6282e67a855f616353ae34a9
- https://forums.businesshelp.comcast.com/conversations/connectivity/multiple-drop-outs-daily/5fe0a648c5375f08cd99fe87
EG
Expert
•
107K Messages
2 years ago
Please redact all of the CM MAC and the CMTS MAC addresses in your error log entries for your privacy. They are considered to be personal information. The posting of personally identifiable information is a violation of their forum guidelines. The forum bot will not allow your post to be seen publically. It flagged your post as "Private".
1
0