Internet keeps dropping & xfinity has no idea how to fix this

Hi Xfinity Community,

My internet has been dropping occasionally for the last year or so and its gotten massively worse in the last 2 weeks - dropping almost every hour. Talking to Xfinity online results in them asking me to reboot my modem and eventually they send a tech out who didn't find any problem with the cabling. They escalated to their "networking department" hoping that there might be something wrong in the line on my street. They still haven't been able to fix the problem. I'm turning to this community in the hopes that I can figure out what information I can get that might pinpoint the problem. My setup:

1. Main line splits into 3 -- one to family room, one to master bedroom and one to office where the main internet router is connected.

2. The splitter has been changed into a new one by the xfinity tech

3. The last tech put a special kind of splitter on my router to boost upstream power. He called out that the upstream power levels aren't great but the fix he put in didn't work.

4. I have a Motorola MB8611 router which shows me the upstream and downstream connections. It is *always* the upstream connection that breaks when the internet goes down.

I have taken screenshots showing the upstream channel status on the mb8611 router. I've attached 3 screenshots - one with the internet working and 2 where it isnt (with 2 channels and 0 channels locked).

I am hoping someone on these forums can help. If not, I will have to convince an xfinity tech to camp out at my house to see the internet drop.

Internet Working Screenshot: All channels locked

Internet not working - 2 channels locked

Internet not working - no channels locked

Responses

U

user_289889

Visitor

•

12 Messages

3 years ago

I feel your pain, I had no issues for a long time, then when my neighbors had an issue and the techs ran a new line for them, I began having outages. Since techs have replaces the line from the street to my house 2x now, I got a brand new modem/router from Xfinity after that, and then I had a brand new line installed IN my house from the junction to the modem, and we still have issues.

I am in IT and have a server at our office that I ping my home modem on 2 minute intervals to keep track of my outages.

What I find interesting is the outages are mostly 8-10 minutes, about the same time it takes for the modem/router to restart, even though visually the modem shows no signs of doing so.

Saturday 2022-04-30
2022-04-30 08:56 am to 09:04 am
Friday 2022-04-29
2022-04-29 04:08 pm to 04:24 pm
2022-04-29 02:20 pm to 02:22 pm
2022-04-29 01:58 pm to 02:00 pm
2022-04-29 01:38 pm to 01:46 pm
2022-04-29 10:48 am to 10:56 am
2022-04-29 10:14 am to 10:20 am
2022-04-29 07:12 am to 07:24 am
Thursday 2022-04-28
2022-04-28 11:26 pm to 11:36 pm
2022-04-28 07:30 pm to 07:38 pm
2022-04-28 06:20 pm to 06:36 pm
2022-04-28 05:58 pm to 06:08 pm
2022-04-28 03:28 pm to 03:36 pm
2022-04-28 02:58 pm to 03:08 pm
2022-04-28 02:00 pm to 02:16 pm
2022-04-28 12:52 pm to 01:12 pm
2022-04-28 10:32 am to 10:40 am
Wednesday 2022-04-27
2022-04-27 06:34 pm to 06:44 pm
2022-04-27 03:42 pm to 03:44 pm
2022-04-27 03:24 pm to 03:40 pm
2022-04-27 02:52 pm to 03:00 pm
Tuesday 2022-04-26
2022-04-26 05:28 pm to 05:38 pm
2022-04-26 02:40 pm to 02:52 pm
2022-04-26 01:02 pm to 01:10 pm
Monday 2022-04-25
2022-04-25 03:12 pm to 06:56 pm
Sunday 2022-04-24
Saturday 2022-04-23
Friday 2022-04-22
2022-04-22 05:42 pm to 05:50 pm
2022-04-22 02:32 pm to 02:48 pm
Thursday 2022-04-21
2022-04-21 01:50 pm to 02:04 pm
2022-04-21 01:24 pm to 01:32 pm
2022-04-21 12:30 pm to 12:32 pm
2022-04-21 10:12 am to 10:14 am
2022-04-21 04:08 am to 04:22 am
2022-04-21 01:08 am to 01:18 am
2022-04-21 12:48 am to 12:56 am
2022-04-21 12:26 am to 12:32 am
Wednesday 2022-04-20
2022-04-20 06:38 pm to 06:46 pm
2022-04-20 06:22 pm to 06:36 pm
2022-04-20 06:12 pm to 06:18 pm
2022-04-20 06:02 pm to 06:10 pm
2022-04-20 04:06 pm to 04:26 pm
2022-04-20 03:38 pm to 03:52 pm
2022-04-20 03:20 pm to 03:28 pm
2022-04-20 03:10 pm to 03:14 pm
2022-04-20 02:56 pm to 03:02 pm
Tuesday 2022-04-19
2022-04-19 08:52 am to 08:54 am
2022-04-19 08:08 am to 08:36 am
2022-04-19 08:02 am to 08:06 am
Monday 2022-04-18
2022-04-18 08:20 pm to 08:28 pm
2022-04-18 08:02 pm to 08:08 pm
2022-04-18 07:44 pm to 07:50 pm
2022-04-18 07:26 pm to 07:34 pm
2022-04-18 07:12 pm to 07:24 pm
2022-04-18 06:24 pm to 06:32 pm
2022-04-18 11:34 am to 11:36 am
2022-04-18 08:28 am to 08:36 am
2022-04-18 08:16 am to 08:22 am
2022-04-18 08:06 am to 08:14 am
2022-04-18 04:34 am to 04:42 am
Sunday 2022-04-17
2022-04-17 09:50 pm to 09:58 pm
2022-04-17 08:50 pm to 08:56 pm
2022-04-17 08:34 pm to 08:42 pm
2022-04-17 07:52 pm to 08:00 pm
2022-04-17 04:08 pm to 04:16 pm
2022-04-17 10:38 am to 10:44 am
2022-04-17 10:22 am to 10:26 am
Saturday 2022-04-16
2022-04-16 07:42 pm to 07:52 pm
2022-04-16 01:26 pm to 01:28 pm
2022-04-16 12:54 pm to 01:02 pm
Friday 2022-04-15
2022-04-15 07:48 pm to 08:04 pm
2022-04-15 05:30 pm to 05:40 pm
2022-04-15 11:38 am to 11:46 am
2022-04-15 10:50 am to 10:56 am
2022-04-15 09:46 am to 09:56 am
2022-04-15 04:08 am to 04:16 am
Thursday 2022-04-14
2022-04-14 06:30 pm to 06:40 pm
2022-04-14 05:08 pm to 05:12 pm
2022-04-14 10:30 am to 10:38 am
2022-04-14 09:08 am to 09:18 am
2022-04-14 08:38 am to 08:46 am
2022-04-14 08:28 am to 08:36 am
2022-04-14 07:48 am to 07:54 am
2022-04-14 07:08 am to 07:10 am
2022-04-14 07:06 am to 07:08 am
Wednesday 2022-04-13
2022-04-13 10:22 pm to 10:32 pm
2022-04-13 08:04 pm to 08:12 pm
2022-04-13 11:44 am to 11:46 am
2022-04-13 10:29 am to 10:30 am
2022-04-13 07:24 am to 07:25 am
Tuesday 2022-04-12
2022-04-12 08:18 pm to 08:28 pm
2022-04-12 03:18 pm to 03:26 pm
2022-04-12 09:46 am to 09:56 am
2022-04-12 08:06 am to 08:12 am
Monday 2022-04-11
2022-04-11 08:40 pm to 08:50 pm
2022-04-11 07:22 pm to 07:30 pm
2022-04-11 05:28 pm to 05:36 pm
2022-04-11 12:28 pm to 12:36 pm
2022-04-11 09:23 am to 09:31 am
2022-04-11 09:09 am to 09:15 am
2022-04-11 08:59 am to 09:05 am
2022-04-11 08:47 am to 08:51 am
2022-04-11 08:39 am to 08:45 am
2022-04-11 08:01 am to 08:19 am
2022-04-11 06:33 am to 06:43 am

(edited)

1

0

XfinityEva

Official Employee

•

1.6K Messages

@user_289889

@user_toby2020

Thank you for the updates on the work and recurring issues. We would like to make sure these are addressed and that we follow up to make sure these are fully resolved for you. If you aren't already, we would like to help through direct message here. Please send us your full name and service address to get started.

Click "Sign In" if necessary

Click the "Direct Messaging" icon or https://comca.st/3kajO4e
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

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

3 years ago

0

justsam

Contributor

•

81 Messages

3 years ago

The guide for your TV requires internet which it gets via MOCA. Problem is Xfinity's, keep after them!

0

user_toby2020

Contributor

•

13 Messages

3 years ago

Another tech came out today - this tech claimed that the xfinity line running in the same conduit as the ATT one is the problem. He routed the xfinity line outside the conduit down the side of my roof. He was very skeptical that there's any problem with the main line and was reluctant to open a network ticket. I convinced him to do it but I'm not sure he did.

The internet didn't drop until 8:30pm this evening. After that, it dropped 3 times in the space of 45 minutes.

Also - the xfinity modem no longer allows local access so I cant even monitor upstream power levels. Atleast with my mb8611 i could see what the power levels were spiking to.

My hope drops every day. I dont think xfinity has the skills or the processes in place to resolve this issue. The techs who come onsite, this online support forum and the network guys don't talk to each and even appear to be hostile (2 techs who came outright rejected the online support claims and didn't care what they said about the T3/T4 drops). I had to show the tech who came onsite about the upstream power spikes and he reluctantly admitted that they seemed way out of range. I even showed him my communication with the online support forum and he said they dont know what they are talking about.

The techs are incentivized to close the ticket as long as the service is up and running - which it is - at that particular point in time. The fact that xfinity tech has to come out again and again has literally no impact on anyone other than me. The tech is rewarded for closing out the ticket after which it is someone else's problem.

More than ever, I realize the importance of competition. I would have dropped Xfinity a year ago but the only alternative is ATT and their 50Mbps connection on a phone line, I have no choice.

(edited)

0

user_toby2020

Contributor

•

13 Messages

3 years ago

Internet dropped 12 times today. Another tech scheduled to come out tomorrow. I dont think xfinity knows whats going on and they keep hoping the next tech will resolve it.

0

justsam

Contributor

•

81 Messages

3 years ago

Xfinity trouble shooting logic boggles my mind! They have replaced everything at your house from interface to coax, and now router that gives you no access to critical information. Yet they keep sending someone out to the premises doing things that make no sense.

The telco and the coax from Xfinity can be in the same conduit and is done all the time. Telco uses a balanced transmission line so radiates little interference, and Xfinity which uses unbalanced transmission line is using a quad shield coax, or at least should be. Bottom line, little chance of interference.

I would put your modem back so you at least have a chance by seeing modem transmission levels. Until a knowledgeable tech camps on that line with a spectrum analyzer to see what is going on you will not resolve it, or better yet actually uses some of the inherent troubleshooting tools in DOCSIS 3.1.

Sounds like ATT will not work for you. I use Verizon LTE when Xfinity fails and I also have a back up ATT DSL, which is much too slow. Any 5G in your area? If so, that can give you a viable alternative.

1

0

U

user_289889

Visitor

•

12 Messages

@justsam This is where my situation is even worse, cell service at our house is non-existent, and I have a cell booster that transmits over internet, or else I have to go out to the street to make a phone call.

New techs and serviceman came out today and seemed to have a better grasp on a larger problem, so hopefully this gets resolved now.

3 years ago

0

Jlavaseur

Problem Solver

•

948 Messages

3 years ago

Well my take on this, after all the different techs, replacing the line etc, I am inclined to think it’s not a Comcast issue at all, I would widen my scope of troubleshooting to include possibly negative interaction between your existing hardware, I would start with a barebones setup, like a computer and just the modem, no router etc, no tv etc just to test, it’s just temporary, analysis the results, eliminating variables is key to when I troubleshoot, I have fixed many issues that someone might think is Comcast’s fault, when it was actually something else…

6

0

U

user_289889

Visitor

•

12 Messages

@jlavaseur Did all that already during the last few weeks, problem never goes away, and gotten worse since we started getting rain lately.

Tech came out this morning, along with a service/linemen? and determined it's definitely equipment in the community, either some amplifier or broken line, he's going around the community checking things.

3 years ago

0

Jlavaseur

Problem Solver

•

948 Messages

Interesting you mention rain, some other posters had problems worsen with rain and wind, it turned out some squirrels ate some of the coax insulation causing havoc…

3 years ago

0

user_toby2020

Contributor

•

13 Messages

The tech who came to my place yesterday appeared to be a lot more knowledgeable. Once he heard about my issues, he called another tech to come to help him. They saw the noise on the line, looked up the high number of T3 drops and atleast acknowledged that there's clearly a problem. They went up the pole and found a filter on the line (presumably to prevent noise from my line to get into the main drop) but confirmed that filter is ok. They redid the connections in the comcast box and then changed out the 2 splitters inside my house.

I haven't had a drop since last evening to this morning so I am hopeful that the combination of all these changes have helped. If it does, I plan to swap out their modem with my motorola mb8611.

3 years ago

U

user_289889

Visitor

•

12 Messages

They worked for a good 2-3 hours going up and down the street. I lost sight of them, but then internet went out for almost an hour then came back up. They returned, and did some work in the unit in the corner of my yard (all underground in the development), and it came back up after that, and has been solid since.

I don't know what they actually replaced but it obviously was something down the line, and hopefully is the true solution.

3 years ago

0

justsam

Contributor

•

81 Messages

Great! Since it was down for an hour, it sounds like they may have found and replaced failed network hardware! Good luck!

3 years ago

0

U

user_67ff72

Visitor

•

3 Messages

3 years ago

I have the MB8611 as well and starting 11AM PST this morning (6/16/22) it went offline and when it came back up, i was seeing 60% packet loss. I was told by support that the MB8611 isn't fast enough to support 600Mbit service - which doesn't agree with their site recommendations. Just an hour ago, according to speedtest (direct ethernet to the modem via a switch), I was seeing 290Mb down and so much packet loss 0 mbit up.

As of now, i'm seeing 600+ Mbit/s down and 0.22 mbit up with speed test - so something is still wrong.

MB8611 status:

Startup Sequence

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

Connection Status

System Up Time	0 days 05h:57m:16s
Network Access	Allowed

Downstream Bonded Channels

Channel	Lock Status	Modulation	Channel ID	Freq. (MHz)	Pwr (dBmV)	SNR (dB)	Corrected	Uncorrected
1	Locked	QAM256	24	531.0	2.9	40.1	218	0
2	Locked	QAM256	4	405.0	4.2	41.5	13	0
3	Locked	QAM256	5	411.0	4.1	41.4	16	0
4	Locked	QAM256	6	417.0	4.1	41.4	12	0
5	Locked	QAM256	7	423.0	4.5	41.4	10	0
6	Locked	QAM256	8	429.0	4.6	41.4	9	0
7	Locked	QAM256	9	435.0	4.5	40.6	21	0
8	Locked	QAM256	10	441.0	4.4	41.2	21	0
9	Locked	QAM256	11	447.0	4.6	41.2	25	0
10	Locked	QAM256	12	453.0	4.7	40.5	33	0
11	Locked	QAM256	13	459.0	4.3	40.9	38	0
12	Locked	QAM256	14	465.0	4.3	40.8	44	0
13	Locked	QAM256	15	471.0	4.4	40.7	44	0
14	Locked	QAM256	16	477.0	4.3	40.5	45	0
15	Locked	QAM256	17	483.0	3.9	41.0	51	0
16	Locked	QAM256	18	489.0	4.2	40.7	51	0
17	Locked	QAM256	19	495.0	4.1	40.6	77	0
18	Locked	QAM256	20	507.0	4.1	40.5	103	0
19	Locked	QAM256	21	513.0	4.4	40.3	102	0
20	Locked	QAM256	22	519.0	4.0	40.2	114	0
21	Locked	QAM256	23	525.0	3.4	39.9	129	0
22	Locked	QAM256	25	537.0	2.8	40.1	280	0
23	Locked	QAM256	26	543.0	2.6	40.1	225	0
24	Locked	QAM256	27	549.0	2.6	39.8	220	0
25	Locked	QAM256	28	555.0	2.9	40.0	232	0
26	Locked	QAM256	29	561.0	3.1	39.8	280	0
27	Locked	QAM256	30	567.0	2.8	40.0	323	0
28	Locked	QAM256	31	573.0	2.8	39.4	333	0
29	Locked	QAM256	32	579.0	2.7	39.9	450	0
30	Locked	QAM256	33	585.0	2.5	40.0	390	0
31	Locked	QAM256	34	591.0	2.4	39.7	418	0
32	Locked	OFDM PLC	48	850.0	-3.8	36.5	287445334	520

Upstream Bonded Channels

Channel	Lock Status	Channel Type	Channel ID	Symb. Rate (Ksym/sec)	Freq. (MHz)	Pwr (dBmV)
1	Locked	SC-QAM	1	2560	10.4	46.0
2	Locked	SC-QAM	2	5120	16.4	46.0
3	Locked	SC-QAM	3	5120	22.8	46.3
4	Locked	SC-QAM	4	5120	29.2	46.3
5	Locked	SC-QAM	5	5120	35.6	47.0
6	Locked	SC-QAM	11	2560	40.4	49.0

3

0

U

user_67ff72

Visitor

•

3 Messages

Xfinity is trying to avoid a truck roll ($$$) and left a robocall at 4:17pm 6/17 saying they fixed something and to cancel the technician call if it's working.

This is what events continue to show on the MB8611. I'm informed that type code 16 and 24 indicate OFDM FEC above spec according to https://forums.cox.com/forum_home/internet_forum/f/internet-forum/29005/list-of-all-cm-status-event-type-codes-with-explanations

I don't know what the baseline rate is for these events, so this may be "ok".

16

DS OFDM profile failure

FEC errors were over limit on one of the assigned downstream OFDM profiles of a channel

24

OFDM profile recovery

FEC recovery on OFDM profile

and while downstream bandwidth is high, upstream bandwidth is, while improved over yesterday, still less than 4Mbit/sec. https://www.speedtest.net/result/d/439636023

previously was getting 24Mbit/sec upstream. What should be expected? This is a 600 Mbit service.

14:40:57 Thu Jun 16 2022		Notice (6)		CM-STATUS message sent. Event Type Code: 16; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
	14:41:37 Thu Jun 16 2022		Notice (6)		CM-STATUS message sent. Event Type Code: 24; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 3.;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
	19:44:06 Thu Jun 16 2022		Notice (6)		CM-STATUS message sent. Event Type Code: 16; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
	19:44:31 Thu Jun 16 2022		Notice (6)		CM-STATUS message sent. Event Type Code: 24; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 3.;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
	20:49:41 Thu Jun 16 2022		Notice (6)		CM-STATUS message sent. Event Type Code: 16; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
	20:50:10 Thu Jun 16 2022		Notice (6)		CM-STATUS message sent. Event Type Code: 24; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 3.;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
	23:30:53 Thu Jun 16 2022		Notice (6)		CM-STATUS message sent. Event Type Code: 16; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
	23:31:19 Thu Jun 16 2022		Notice (6)		CM-STATUS message sent. Event Type Code: 24; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 3.;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
	02:03:40 Fri Jun 17 2022		Notice (6)		CM-STATUS message sent. Event Type Code: 16; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
	02:04:06 Fri Jun 17 2022		Notice (6)		CM-STATUS message sent. Event Type Code: 24; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 3.;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
	03:11:50 Fri Jun 17 2022		Notice (6)		CM-STATUS message sent. Event Type Code: 16; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
	03:12:16 Fri Jun 17 2022		Notice (6)		CM-STATUS message sent. Event Type Code: 24; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 3.;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
	03:44:06 Fri Jun 17 2022		Notice (6)		CM-STATUS message sent. Event Type Code: 16; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
	03:44:30 Fri Jun 17 2022		Notice (6)		CM-STATUS message sent. Event Type Code: 24; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 3.;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
	05:44:05 Fri Jun 17 2022		Notice (6)		CM-STATUS message sent. Event Type Code: 16; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
	05:44:35 Fri Jun 17 2022		Notice (6)		CM-STATUS message sent. Event Type Code: 24; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 3.;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
	07:14:04 Fri Jun 17 2022		Notice (6)		CM-STATUS message sent. Event Type Code: 16; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
	07:14:34 Fri Jun 17 2022		Notice (6)		CM-STATUS message sent. Event Type Code: 24; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 3.;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
	08:28:10 Fri Jun 17 2022		Notice (6)		CM-STATUS message sent. Event Type Code: 16; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
	08:28:31 Fri Jun 17 2022		Notice (6)		CM-STATUS message sent. Event Type Code: 24; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 3.;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
	11:44:06 Fri Jun 17 2022		Notice (6)		CM-STATUS message sent. Event Type Code: 16; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
	11:44:34 Fri Jun 17 2022		Notice (6)		CM-STATUS message sent. Event Type Code: 24; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 3.;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
	13:25:31 Fri Jun 17 2022		Notice (6)		CM-STATUS message sent. Event Type Code: 16; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
	13:26:00 Fri Jun 17 2022		Notice (6)		CM-STATUS message sent. Event Type Code: 24; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 3.;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
	14:10:43 Fri Jun 17 2022		Notice (6)		CM-STATUS message sent. Event Type Code: 16; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
	14:11:10 Fri Jun 17 2022		Notice (6)		CM-STATUS message sent. Event Type Code: 24; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 3.;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
	16:49:32 Fri Jun 17 2022		Notice (6)		CM-STATUS message sent. Event Type Code: 16; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
	16:49:56 Fri Jun 17 2022		Notice (6)		CM-STATUS message sent. Event Type Code: 24; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 3.;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
	16:59:06 Fri Jun 17 2022		Notice (6)		CM-STATUS message sent. Event Type Code: 16; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
	16:59:37 Fri Jun 17 2022		Notice (6)		CM-STATUS message sent. Event Type Code: 24; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 3.;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
	17:31:58 Fri Jun 17 2022		Notice (6)		CM-STATUS message sent. Event Type Code: 16; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
	17:32:26 Fri Jun 17 2022		Notice (6)		CM-STATUS message sent. Event Type Code: 24; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 3.;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;

(edited)

3 years ago

0

U

user_67ff72

Visitor

•

3 Messages

as far as downstream OFDM, high correctables seem to be expected with docsis 3.1 as per https://volpefirm.com/technology-questions-answered-snr-ofdma-and-more/ 37:18 Why do we get significant correctable errors on DOCSIS 3.1?

i'm guessing the now lower upstream bandwidth must have been a provisioning change on the xfinity side allocating less talk time for the shared upstream?

3 years ago

0

EG

Expert

•

110.2K Messages

@user_67ff72

FWIW. You'll need to 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".

I am not a Comcast Employee.
I am a Customer Expert volunteering my time to help other customers here in the Forums.
We ask that you post publicly so people with similar questions may benefit from the conversation.

Was your question answered? Please mark an Accepted Answer! tick

3 years ago

0

Your Home Network

user_toby2020

Internet keeps dropping & xfinity has no idea how to fix this

user_289889

XfinityEva

@user_289889

@user_toby2020

justsam

user_toby2020

user_toby2020

justsam

user_289889

Jlavaseur

user_289889

Jlavaseur

user_toby2020

user_289889

justsam

user_67ff72

user_67ff72

user_67ff72

EG

New to the Community?