Visitor
•
4 Messages
Linemen working and then terrible download speeds and dropped packets
I am an IT professional and I do not have time for the IVR steps that I have already completed. A bunch of linemen were out about a week ago and since they have departed I have had dropped packets, connectivity so bad that the modem determines it cannot keep a connection and goes through the process of trying to relock the channels and when there is connectivity the download is maybe 1/8th of normal. I do not want to take time off for something that has been caused by linemen. I just want you to get whatever was done back to how it was. I will say it was unusual that the group of linemen and trucks did not have any company on them. The linemen going up and down the street were in shorts and t-shirts and were not using any safety equipment. They also had a trailer of coaxial cable with them.
Here are the sanitised logs:
|
Time |
Priority |
Description |
|
Sat Jun 28 10:18:19 2025 |
Warning (5) |
MDD message timeout; CM-MAC=[YOUR_MODEM_MAC]; CMTS-MAC=[Edited: "Personal Information"]; CM-QOS=1.1; CM-VER=3.1; |
|
Sat Jun 28 10:18:19 2025 |
Notice (6) |
CM-STATUS message sent. Event Type Code: 5; Chan ID: 34 35 36 37; |
|
Sat Jun 28 10:18:12 2025 |
Notice (6) |
CM-STATUS message sent. Event Type Code: 4; Chan ID: 28 34 35 36 37 38 39 40 41 42 43 44 193; |
|
Sat Jun 28 10:18:11 2025 |
Warning (5) |
MDD message timeout; CM-MAC=[YOUR_MODEM_MAC]; CMTS-MAC=[Edited: "Personal Information"]; CM-QOS=1.1; CM-VER=3.1; |
|
Sat Jun 28 10:18:09 2025 |
Notice (6) |
CM-STATUS message sent. Event Type Code: 4; Chan ID: 28 34 35 36 37 38 39 40 41 42 43 44 193; |
|
Sat Jun 28 10:17:59 2025 |
Warning (5) |
MDD message timeout; CM-MAC=[YOUR_MODEM_MAC]; CMTS-MAC=[Edited: "Personal Information"]; CM-QOS=1.1; CM-VER=3.1; |
|
Sat Jun 28 10:17:37 2025 |
Notice (6) |
CM-STATUS message sent. Event Type Code: 5; Chan ID: 34 35 36 37; |
|
Sat Jun 28 10:17:32 2025 |
Notice (6) |
CM-STATUS message sent. Event Type Code: 4; Chan ID: 28 34 35 36 37 38 39 40 41 42 43 44 193; |
|
Sat Jun 28 10:17:29 2025 |
Notice (6) |
CM-STATUS message sent. Event Type Code: 2; Chan ID: 35; |
|
Sat Jun 28 10:17:28 2025 |
Critical (3) |
Started Unicast Maintenance Ranging - No Response received - T3 time-out; |
|
Sat Jun 28 10:17:27 2025 |
Warning (5) |
MDD message timeout; CM-MAC=[YOUR_MODEM_MAC]; CMTS-MAC=[Edited: "Personal Information"]; CM-QOS=1.1; CM-VER=3.1; |
|
Sat Jun 28 10:17:01 2025 |
Notice (6) |
CM-STATUS message sent. Event Type Code: 5; Chan ID: 34 35 36 37; |
|
Sat Jun 28 10:17:01 2025 |
Notice (6) |
CM-STATUS message sent. Event Type Code: 4; Chan ID: 34 36 37; |
|
Sat Jun 28 10:16:53 2025 |
Warning (5) |
MDD message timeout; CM-MAC=[YOUR_MODEM_MAC]; CMTS-MAC=[Edited: "Personal Information"]; CM-QOS=1.1; CM-VER=3.1; |
|
Sat Jun 28 10:16:47 2025 |
Notice (6) |
CM-STATUS message sent. Event Type Code: 1; Chan ID: 34; |
|
Sat Jun 28 10:16:45 2025 |
Warning (5) |
MDD message timeout; CM-MAC=[YOUR_MODEM_MAC]; CMTS-MAC=[Edited: "Personal Information"]; CM-QOS=1.1; CM-VER=3.1; |
|
Sat Jun 28 10:16:11 2025 |
Notice (6) |
CM-STATUS message sent. Event Type Code: 5; Chan ID: 34 35 36 37; |
|
Sat Jun 28 10:16:11 2025 |
Notice (6) |
CM-STATUS message sent. Event Type Code: 4; Chan ID: 34 35 36 37; |
|
Sat Jun 28 10:16:02 2025 |
Warning (5) |
MDD message timeout; CM-MAC=[YOUR_MODEM_MAC]; CMTS-MAC=[Edited: "Personal Information"]; CM-QOS=1.1; CM-VER=3.1; |
|
Sat Jun 28 10:15:48 2025 |
Notice (6) |
CM-STATUS message sent. Event Type Code: 4; Chan ID: 34 35 36 37; |
|
Sat Jun 28 10:15:23 2025 |
Warning (5) |
MDD message timeout; CM-MAC=[YOUR_MODEM_MAC]; CMTS-MAC=[Edited: "Personal Information"]; CM-QOS=1.1; CM-VER=3.1; |
|
Sat Jun 28 10:15:07 2025 |
Notice (6) |
CM-STATUS message sent. Event Type Code: 4; Chan ID: 34 35 36 37; |
|
Sat Jun 28 10:14:59 2025 |
Warning (5) |
MDD message timeout; CM-MAC=[YOUR_MODEM_MAC]; CMTS-MAC=[Edited: "Personal Information"]; CM-QOS=1.1; CM-VER=3.1; |
|
Sat Jun 28 10:14:33 2025 |
Notice (6) |
CM-STATUS message sent. Event Type Code: 5; Chan ID: 34 35 36 37; |
|
Sat Jun 28 10:14:32 2025 |
Notice (6) |
CM-STATUS message sent. Event Type Code: 4; Chan ID: 34 35 36 37; |
|
Sat Jun 28 10:14:27 2025 |
Notice (6) |
CM-STATUS message sent. Event Type Code: 2; Chan ID: 34 35; |
|
Sat Jun 28 10:14:26 2025 |
Notice (6) |
CM-STATUS message sent. Event Type Code: 4; Chan ID: 36 37; |
|
Sat Jun 28 10:14:25 2025 |
Notice (6) |
CM-STATUS message sent. Event Type Code: 1; Chan ID: 34 35; |
|
Sat Jun 28 10:14:23 2025 |
Warning (5) |
MDD message timeout; CM-MAC=[YOUR_MODEM_MAC]; CMTS-MAC=[Edited: "Personal Information"]; CM-QOS=1.1; CM-VER=3.1; |
|
Sat Jun 28 10:13:42 2025 |
Notice (6) |
CM-STATUS message sent. Event Type Code: 4; Chan ID: 34 35 36 37; |
|
Sat Jun 28 10:13:34 2025 |
Warning (5) |
MDD message timeout; CM-MAC=[YOUR_MODEM_MAC]; CMTS-MAC=[Edited: "Personal Information"]; CM-QOS=1.1; CM-VER=3.1; |
|
Sat Jun 28 10:13:34 2025 |
Notice (6) |
CM-STATUS message sent. Event Type Code: 4; Chan ID: 34 35 36 37; |
|
Sat Jun 28 10:13:22 2025 |
Notice (6) |
CM-STATUS message sent. Event Type Code: 5; Chan ID: 34 35 36 37; |
|
Sat Jun 28 10:13:19 2025 |
Warning (5) |
MDD message timeout; CM-MAC=[YOUR_MODEM_MAC]; CMTS-MAC=[Edited: "Personal Information"]; CM-QOS=1.1; CM-VER=3.1; |
|
Sat Jun 28 10:13:15 2025 |
Notice (6) |
CM-STATUS message sent. Event Type Code: 2; Chan ID: 34 35; |
|
Sat Jun 28 10:13:14 2025 |
Notice (6) |
CM-STATUS message sent. Event Type Code: 4; Chan ID: 36 37; |
|
Sat Jun 28 10:13:11 2025 |
Warning (5) |
MDD message timeout; CM-MAC=[YOUR_MODEM_MAC]; CMTS-MAC=[Edited: "Personal Information"]; CM-QOS=1.1; CM-VER=3.1; |
|
Sat Jun 28 10:12:55 2025 |
Notice (6) |
CM-STATUS message sent. Event Type Code: 2; Chan ID: 34; |
|
Sat Jun 28 10:12:51 2025 |
Notice (6) |
CM-STATUS message sent. Event Type Code: 5; Chan ID: 35 36 37; |
|
Sat Jun 28 10:12:47 2025 |
Warning (5) |
MDD message timeout; CM-MAC=[YOUR_MODEM_MAC]; CMTS-MAC=[Edited: "Personal Information"]; CM-QOS=1.1; CM-VER=3.1; |
FutureICE
Visitor
•
4 Messages
7 days ago
Please sort out your lines. This does not need me to waste my time and be present. Also an adjustment for every day I do not receive the speeds I pay for would be appreciated.
0
0
EG
Expert
•
111.5K Messages
7 days ago
@FutureICE
The logs have not been "sanitised". Please redact all of the CM MAC and the CMTS MAC addresses from 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 publicly. It flagged your post as "Private".
2
0
FutureICE
Visitor
•
4 Messages
6 days ago
Update: I decided to walk the xfinity line and found that they not only need to send out linemen to repair a section, they also need to send out arborists to remove growth that is impeding on the lines along the road. One of the lines is sagging very very badly.
0
0
XfinityArmand
Official Employee
•
2.2K Messages
5 days ago
Thank you so much for taking the time to reach out to Xfinity Support @FutureICE! We are so glad to hear from you and want to assist in any way that we can with your service. No worries! You have reached out to the best team to help get things ironed out for you. Please feel free to shoot us a private message with your details, whenever you are ready, so that we can get started.
To send a "direct message" / "private message" message to Xfinity Support:
• Click "Sign In" if necessary
• Click the "Direct Message" icon or https://forums.xfinity.com/direct-messaging
• 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