TaperCrimp's profile

Visitor

 • 

13 Messages

Tuesday, August 3rd, 2021 1:35 PM

Closed

Frequent 5-10 Minute Internet Outages: Ongoing Problem

Hello,

I've got a Netgear CM2000, but this problem was also ongoing with my last modem. I'm currently subscribed to the 1200 Mbps plan. I'll encounter multiple outages 5-10 minutes a day where the Internet connection completely drops. During that time, the downstream light on the modem will begin blinking as if it's trying to get a lock. The logs also show a timeout for the OFDM channel. The modem seems to restart itself after 5 minutes and generally comes back online, but it'll occasionally take 2-3 tries which equates to a 10-15 minute outage. 

I've had Xfinity techs out twice at this point. The first tech checked a bunch of signals and decided everything was good. The next tech said the line to the house was bad, had it replaced, and then eventually had the whole underground line replaced that goes to the next hop, i.e. 2 houses up the street. He verified this is not an issue with my home wiring or cable modem. I started checking with my neighbors, and all of them are having the exact same issue. Exchanging text messages with the neighbors confirms that when one of us has an Internet drop-out, everyone at the end of the street has one that lasts 5-15 minutes. At this point I'm suspecting that the issue is somewhere further up the street.

The majority of the logs are similar to this:

Sat Jul 31 09:41:06 2021	(Warning (5))	Dynamic Range Window violation
Sat Jul 31 09:41:06 2021	(Warning (5))	RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=YY:YY:YY:YY:YY:YY;CM-QOS=1.1;CM-VER=3.1;
Sat Jul 31 09:41:02 2021	(Critical (3))	No Ranging Response received - T3 time-out;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=YY:YY:YY:YY:YY:YY;CM-QOS=1.1;CM-VER=3.1;
Sat Jul 31 09:40:54 2021	(Critical (3))	SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=YY:YY:YY:YY:YY:YY;CM-QOS=1.1;CM-VER=3.1;
Sat Jul 31 09:40:54 2021	(Notice (6))	DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=YY:YY:YY:YY:YY:YY;CM-QOS=1.1;CM-VER=3.1;
Sat Jul 31 09:40:53 2021	(Notice (6))	TLV-11 - unrecognized OID;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=YY:YY:YY:YY:YY:YY;CM-QOS=1.1;CM-VER=3.1;
Sat Jul 31 09:40:45 2021	(Notice (6))	Honoring MDD; IP provisioning mode = IPv6
Sat Jul 31 09:40:36 2021	(Critical (3))	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
Sat Jul 31 09:37:45 2021	(Critical (3))	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=YY:YY:YY:YY:YY:YY;CM-QOS=1.1;CM-VER=3.1;
Sat Jul 31 09:37:45 2021	(Critical (3))	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=YY:YY:YY:YY:YY:YY;CM-QOS=1.1;CM-VER=3.1;
Sat Jul 31 09:37:22 2021	(Critical (3))	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=YY:YY:YY:YY:YY:YY;CM-QOS=1.1;CM-VER=3.1;

Modem levels are listed here:

Procedure Status Comment
Acquire Downstream Channel 645000000 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 25 645000000 Hz 12.0 dBmV 42.4 dB 0 0
2 Locked QAM256 10 531000000 Hz 11.8 dBmV 43.0 dB 0 0
3 Locked QAM256 11 537000000 Hz 11.9 dBmV 43.1 dB 0 0
4 Locked QAM256 12 543000000 Hz 12.0 dBmV 43.1 dB 0 0
5 Locked QAM256 13 549000000 Hz 12.3 dBmV 43.2 dB 0 0
6 Locked QAM256 14 555000000 Hz 12.1 dBmV 43.1 dB 0 0
7 Locked QAM256 15 579000000 Hz 11.6 dBmV 42.8 dB 0 0
8 Locked QAM256 16 585000000 Hz 11.8 dBmV 42.8 dB 0 0
9 Locked QAM256 17 591000000 Hz 12.2 dBmV 42.8 dB 0 0
10 Locked QAM256 18 597000000 Hz 12.3 dBmV 42.9 dB 0 0
11 Locked QAM256 19 603000000 Hz 12.1 dBmV 42.8 dB 0 0
12 Locked QAM256 20 609000000 Hz 12.0 dBmV 42.7 dB 0 0
13 Locked QAM256 21 615000000 Hz 12.1 dBmV 42.6 dB 0 0
14 Locked QAM256 22 621000000 Hz 12.3 dBmV 42.7 dB 0 0
15 Locked QAM256 23 627000000 Hz 12.4 dBmV 42.6 dB 0 0
16 Locked QAM256 24 633000000 Hz 12.1 dBmV 42.5 dB 0 0
17 Locked QAM256 26 651000000 Hz 12.1 dBmV 42.4 dB 0 0
18 Locked QAM256 27 657000000 Hz 12.5 dBmV 42.5 dB 0 0
19 Locked QAM256 28 663000000 Hz 12.6 dBmV 42.5 dB 0 0
20 Locked QAM256 29 669000000 Hz 12.5 dBmV 42.6 dB 0 0
21 Locked QAM256 30 675000000 Hz 12.2 dBmV 41.6 dB 0 0
22 Locked QAM256 31 681000000 Hz 12.0 dBmV 42.4 dB 0 0
23 Locked QAM256 32 687000000 Hz 12.2 dBmV 42.4 dB 0 0
24 Locked QAM256 33 693000000 Hz 12.6 dBmV 42.6 dB 0 0
25 Locked QAM256 34 699000000 Hz 13.1 dBmV 42.7 dB 0 0
26 Locked QAM256 35 705000000 Hz 13.2 dBmV 42.7 dB 0 0
27 Locked QAM256 36 711000000 Hz 13.0 dBmV 42.6 dB 0 0
28 Locked QAM256 37 717000000 Hz 13.0 dBmV 42.4 dB 0 0
29 Locked QAM256 38 723000000 Hz 13.1 dBmV 42.5 dB 0 0
30 Locked QAM256 39 729000000 Hz 13.3 dBmV 42.5 dB 0 0
31 Locked QAM256 40 735000000 Hz 13.4 dBmV 42.5 dB 0 0
32 Not Locked Unknown 0 0 Hz 0.0 dBmV 0.0 dB 0 0
 
Upstream Bonded Channels
Channel Lock Status US Channel Type Channel ID Symbol Rate Frequency Power
1 Locked ATDMA 1 5120 35600000 Hz 35.3 dBmV
2 Locked ATDMA 2 5120 29200000 Hz 35.5 dBmV
3 Locked ATDMA 3 5120 22800000 Hz 35.0 dBmV
4 Locked ATDMA 4 5120 16400000 Hz 34.8 dBmV
5 Locked ATDMA 9 2560 40400000 Hz 35.3 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
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 41 762000000 Hz 13.8 dBmV 42.1 dB 1108 ~ 2987 5762104 4943253 0
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

As mentioned above, this would appear to be more of a systemic issue upstream from our street. Unfortunately I'm not sure who else has opened tickets. We've got a group text going where one person will ask "Is anyone else down?" and sure enough everyone else is down too. FYI I'd just rest the modem, but the "uncorrectables" will frequently increasing during the timeout issue.

What can we do to get this resolved? This issue makes it almost impossible to work remotely. 

Visitor

 • 

1 Message

3 years ago

Experiencing the exact same issue as you for months now. Support is 0 help. Technician came out and replaced cables and connections near the modem but issue still occurring. Called support maybe 12 times now. 

97219 area?

Visitor

 • 

13 Messages

@Adkihn

Other side of the country unfortunately. They replaced the line to my house, and then ran a brand new one underground to the next hop a few houses down. I'm assuming it's like anything else: the more data you squeeze out of a line, the more sensitive it is to any fluctuations. I'm almost positive this started when it went from 1000 Mbps to 1200 Mbps. I definitely did not have this problem when I was on the old plan that I believe was around 600 Mbps. 

It was just the other day that I realized it was happening to most of my neighbors upstream from me too. Exact same time for everyone, which tells me there's an interruption or issue further up the chain. I don't think there's much of a reason to keep checking my cable modem or line to the house when it's happening to multiple houses on the same cable run. 

Hopefully someone from Xfinity responds since this is a massive pain and I don't have many other options for service. 

Visitor

 • 

13 Messages

3 years ago

...and once again it's out with the following error:

Wed Aug 04 18:32:08 2021	(Notice (6))	DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=YY:YY:YY:YY:YY:YY;CM-QOS=1.1;CM-VER=3.1;
Wed Aug 04 18:32:07 2021	(Notice (6))	TLV-11 - unrecognized OID;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=YY:YY:YY:YY:YY:YY;CM-QOS=1.1;CM-VER=3.1;
Wed Aug 04 18:31:57 2021	(Notice (6))	Honoring MDD; IP provisioning mode = IPv6
Wed Aug 04 18:31:49 2021	(Critical (3))	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
Wed Aug 04 18:31:47 2021	(Warning (5))	Lost MDD Timeout;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
Wed Aug 04 18:31:40 2021	(Critical (3))	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
Wed Aug 04 18:29:03 2021	(Critical (3))	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=YY:YY:YY:YY:YY:YY;CM-QOS=1.1;CM-VER=3.1;
Wed Aug 04 18:29:03 2021	(Critical (3))	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=YY:YY:YY:YY:YY:YY;CM-QOS=1.1;CM-VER=3.1;
Wed Aug 04 18:28:29 2021	(Critical (3))	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=YY:YY:YY:YY:YY:YY;CM-QOS=1.1;CM-VER=3.1;
Wed Aug 04 18:28:29 2021	(Critical (3))	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=YY:YY:YY:YY:YY:YY;CM-QOS=1.1;CM-VER=3.1;
Wed Aug 04 18:27:52 2021	(Critical (3))	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=YY:YY:YY:YY:YY:YY;CM-QOS=1.1;CM-VER=3.1;
Wed Aug 04 18:27:52 2021	(Critical (3))	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=YY:YY:YY:YY:YY:YY;CM-QOS=1.1;CM-VER=3.1;
Wed Aug 04 18:27:18 2021	(Critical (3))	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=YY:YY:YY:YY:YY:YY;CM-QOS=1.1;CM-VER=3.1;
Wed Aug 04 18:27:18 2021	(Critical (3))	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=YY:YY:YY:YY:YY:YY;CM-QOS=1.1;CM-VER=3.1;
Wed Aug 04 18:27:03 2021	(Critical (3))	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=YY:YY:YY:YY:YY:YY;CM-QOS=1.1;CM-VER=3.1;
Wed Aug 04 18:27:03 2021	(Critical (3))	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=YY:YY:YY:YY:YY:YY;CM-QOS=1.1;CM-VER=3.1;
Wed Aug 04 18:25:21 2021	(Warning (5))	MDD message timeout;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=YY:YY:YY:YY:YY:YY;CM-QOS=1.1;CM-VER=3.1;
Wed Aug 04 18:25:20 2021	(Critical (3))	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=YY:YY:YY:YY:YY:YY;CM-QOS=1.1;CM-VER=3.1;
Wed Aug 04 18:25:15 2021	(Warning (5))	MDD message timeout;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=YY:YY:YY:YY:YY:YY;CM-QOS=1.1;CM-VER=3.1;
Wed Aug 04 18:25:14 2021	(Critical (3))	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=YY:YY:YY:YY:YY:YY;CM-QOS=1.1;CM-VER=3.1;

This has happened 3 times in the last two days. Every time I try to contact Xfinity support, I'm told "there's a known outage" or "there's a tech in the area". This happens at least once a day, to the point that I'm tethered to my phone instead of Xfinity if I've got anything remotely important. What can be done to get this resolved? The response to this has been beyond disappointing after being a customer for over a decade. 

Visitor

 • 

3 Messages

@TaperCrimp  Where are you getting these messages from?

About two weeks ago I started having horrible problems with my connection--going down several times a day, everyday. At least two of my neighbors are having the same problem, almost at exactly the same time.

Visitor

 • 

13 Messages

3 years ago

If anyone from Xfinity is reading this, the ticket is <edit ticket #>. I've had the exact same conversation with support a dozen times now. I shouldn't need to look into the cost of a backup line since Xfinity goes down 2-3 times a day for 5-15 minutes at a time. I'm also definitely tired of explaining to support that resetting my modem isn't going to fix a line issue somewhere up the street. 

(edited)

Official Employee

 • 

923 Messages

Hi, @TaperCrimp

 

I do see you've had ongoing troubles here, we'd love to look into that ticket on your account. Please send us a direct message with your name and address.

To send a direct message, please click on the chat icon in the top-right corner of the screen, and select "Xfinity Support" to initiate a live chat. 

 

Click "Sign In" if necessary

Click the "direct messaging" icon or https://comca.st/3AfLUAc

Click the "New message" (pencil and paper) icon

Type "Xfinity Support" in the "To:" line and select "Xfinity Support" from the drop-down list which appears. The "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

Visitor

 • 

13 Messages

Thanks, I just reached out. A line tech was out yesterday and replaced something down the street. Everyone is still going up and down this morning though, so it obviously didn't fix it. 

Visitor

 • 

13 Messages

3 years ago

On a positive, a line tech was out yesterday that was replacing equipment down the street. On a negative, everyone on the street is still having outages this morning. I've had two since 9 AM Eastern. 

Fri Aug 06 08:13:48 2021	(Notice (6))	CM-STATUS message sent. Event Type Code: 24; Chan ID: 41; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1 2.;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=YY:YY:YY:YY:YY:YY;CM-QOS=1.1;CM-VER=3.1;
Fri Aug 06 08:13:46 2021	(Notice (6))	CM-STATUS message sent. Event Type Code: 22; Chan ID: 41; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=YY:YY:YY:YY:YY:YY;CM-QOS=1.1;CM-VER=3.1;
Fri Aug 06 08:13:37 2021	(Notice (6))	CM-STATUS message sent. Event Type Code: 23; Chan ID: 41; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=YY:YY:YY:YY:YY:YY;CM-QOS=1.1;CM-VER=3.1;
Fri Aug 06 08:13:23 2021	(Critical (3))	No Ranging Response received - T3 time-out;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=YY:YY:YY:YY:YY:YY;CM-QOS=1.1;CM-VER=3.1;
Fri Aug 06 08:13:12 2021	(Critical (3))	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=YY:YY:YY:YY:YY:YY;CM-QOS=1.1;CM-VER=3.1;
Fri Aug 06 08:11:50 2021	(Warning (5))	MDD message timeout;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=YY:YY:YY:YY:YY:YY;CM-QOS=1.1;CM-VER=3.1;
Fri Aug 06 08:11:50 2021	(Critical (3))	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=YY:YY:YY:YY:YY:YY;CM-QOS=1.1;CM-VER=3.1;
Fri Aug 06 08:11:44 2021	(Warning (5))	MDD message timeout;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=YY:YY:YY:YY:YY:YY;CM-QOS=1.1;CM-VER=3.1;
Fri Aug 06 08:11:44 2021	(Critical (3))	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=YY:YY:YY:YY:YY:YY;CM-QOS=1.1;CM-VER=3.1;
Fri Aug 06 08:06:51 2021	(Notice (6))	CM-STATUS message sent. Event Type Code: 24; Chan ID: 41; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=YY:YY:YY:YY:YY:YY;CM-QOS=1.1;CM-VER=3.1;
Fri Aug 06 08:06:22 2021	(Notice (6))	CM-STATUS message sent. Event Type Code: 16; Chan ID: 41; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=YY:YY:YY:YY:YY:YY;CM-QOS=1.1;CM-VER=3.1;
		
Fri Aug 06 08:40:40 2021	(Notice (6))	CM-STATUS message sent. Event Type Code: 24; Chan ID: 41; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=YY:YY:YY:YY:YY:YY;CM-QOS=1.1;CM-VER=3.1;
Fri Aug 06 08:40:14 2021	(Notice (6))	CM-STATUS message sent. Event Type Code: 16; Chan ID: 41; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=YY:YY:YY:YY:YY:YY;CM-QOS=1.1;CM-VER=3.1;
Fri Aug 06 08:33:08 2021	(Critical (3))	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=YY:YY:YY:YY:YY:YY;CM-QOS=1.1;CM-VER=3.1;
Fri Aug 06 08:33:02 2021	(Notice (6))	DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=YY:YY:YY:YY:YY:YY;CM-QOS=1.1;CM-VER=3.1;
Fri Aug 06 08:33:02 2021	(Notice (6))	TLV-11 - unrecognized OID;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=YY:YY:YY:YY:YY:YY;CM-QOS=1.1;CM-VER=3.1;
Fri Aug 06 08:32:51 2021	(Notice (6))	Honoring MDD; IP provisioning mode = IPv6
Fri Aug 06 08:32:42 2021	(Critical (3))	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
Fri Aug 06 08:32:00 2021	(Critical (3))	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=YY:YY:YY:YY:YY:YY;CM-QOS=1.1;CM-VER=3.1;
Fri Aug 06 08:31:59 2021	(Critical (3))	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=YY:YY:YY:YY:YY:YY;CM-QOS=1.1;CM-VER=3.1;
Fri Aug 06 08:31:51 2021	(Critical (3))	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=YY:YY:YY:YY:YY:YY;CM-QOS=1.1;CM-VER=3.1;
Fri Aug 06 08:31:51 2021	(Critical (3))	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=YY:YY:YY:YY:YY:YY;CM-QOS=1.1;CM-VER=3.1;
Fri Aug 06 08:31:51 2021	(Critical (3))	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=YY:YY:YY:YY:YY:YY;CM-QOS=1.1;CM-VER=3.1;
Fri Aug 06 08:31:51 2021	(Critical (3))	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=YY:YY:YY:YY:YY:YY;CM-QOS=1.1;CM-VER=3.1;
Fri Aug 06 08:31:49 2021	(Critical (3))	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=YY:YY:YY:YY:YY:YY;CM-QOS=1.1;CM-VER=3.1;
Fri Aug 06 08:31:49 2021	(Critical (3))	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=YY:YY:YY:YY:YY:YY;CM-QOS=1.1;CM-VER=3.1;
Fri Aug 06 08:31:48 2021	(Critical (3))	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=YY:YY:YY:YY:YY:YY;CM-QOS=1.1;CM-VER=3.1;
Fri Aug 06 08:31:48 2021	(Critical (3))	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=YY:YY:YY:YY:YY:YY;CM-QOS=1.1;CM-VER=3.1;
Fri Aug 06 08:28:16 2021	(Warning (5))	MDD message timeout;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=YY:YY:YY:YY:YY:YY;CM-QOS=1.1;CM-VER=3.1;
Fri Aug 06 08:28:15 2021	(Critical (3))	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=YY:YY:YY:YY:YY:YY;CM-QOS=1.1;CM-VER=3.1;
Fri Aug 06 08:28:10 2021	(Warning (5))	MDD message timeout;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=YY:YY:YY:YY:YY:YY;CM-QOS=1.1;CM-VER=3.1;
Fri Aug 06 08:28:09 2021	(Critical (3))	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=YY:YY:YY:YY:YY:YY;CM-QOS=1.1;CM-VER=3.1;
Fri Aug 06 08:25:00 2021	(Notice (6))	CM-STATUS message sent. Event Type Code: 24; Chan ID: 41; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1 2 3.;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=YY:YY:YY:YY:YY:YY;CM-QOS=1.1;CM-VER=3.1;
Fri Aug 06 08:24:32 2021	(Notice (6))	CM-STATUS message sent. Event Type Code: 16; Chan ID: 41; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=YY:YY:YY:YY:YY:YY;CM-QOS=1.1;CM-VER=3.1;
Fri Aug 06 08:23:00 2021	(Notice (6))	CM-STATUS message sent. Event Type Code: 24; Chan ID: 41; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1 2 3.;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=YY:YY:YY:YY:YY:YY;CM-QOS=1.1;CM-VER=3.1;
Fri Aug 06 08:22:29 2021	(Notice (6))	CM-STATUS message sent. Event Type Code: 16; Chan ID: 41; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=YY:YY:YY:YY:YY:YY;CM-QOS=1.1;CM-VER=3.1;

Visitor

 • 

13 Messages

3 years ago

The line tech was on our street twice last week. He's tried replacing equipment at two different locations. Everyone on the street is still having 3-4 outages per day, with everyone going down at the same time. @Xfinity Support how do I get them back out here? Every time I report an outage, I get asked to reset my modem, schedule an appointment, offered a Flex, etc. None of that would fix the problem. I literally just want my Internet to quit dropping every few hours. The line tech, i.e. the guy driving the bucket truck, confirmed it's a problem with Xfinity's infrastructure in the area and there's no point in having a tech sent to my house. How do I get them back out to correct this once and for all?

Literally everyone on the street goes down when this happens. It's a problem with one of the underground lines that everyone is connected to. I'm starting to wonder if there's any point in reporting 3-4 outages a day since the response from support is exactly the same, and I spend 20 minutes explaining the exact same problem over and over. At this point I would switch to another provided if I had any viable alternatives. Using my phone as a hot spot is more reliable.

(edited)

Visitor

 • 

13 Messages

3 years ago

Also, just to put it in perspective, each line represents an outage over the last 3 days. Imagine trying to work remotely though this.

failed since 2021-08-07 09:15:12-04:00; 
failed since 2021-08-07 10:26:31-04:00; 
failed since 2021-08-07 10:36:39-04:00; 
failed since 2021-08-07 10:36:39-04:00; 
failed since 2021-08-07 11:56:03-04:00; 
failed since 2021-08-07 23:52:10-04:00; 
failed since 2021-08-10 07:55:03-04:00; 
failed since 2021-08-10 08:09:36-04:00; 
failed since 2021-08-10 11:56:40-04:00; 
failed since 2021-08-10 14:17:32-04:00; 

(edited)

Official Employee

 • 

1.3K Messages

@TaperCrimp

I am sorry to hear that the tech visit didn't solve the issue. Can you send us a new Direct Message so we can keep working on this? Thank you!

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

Visitor

 • 

13 Messages

@XfinityTony

I just replied to the Xfinity Support contact. This is still ongoing 3-4 times per day and impacts the entire street. This has happened 3 times today already. I just spent $300 on a Verizon hotspot so I can stay connected to Zoom meetings. I'd cancel my service if I had viable alternatives. I'll gladly DM you the conversation I just had with support: first they tried charging me $100 to send out a tech, then he told me I should drive 25 minutes to the Xfinity store because... well, I don't know why. 

Official Employee

 • 

1.3K Messages

@TaperCrimp

I got your DM. I will continue to work with you there. Thank you!

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

Visitor

 • 

13 Messages

3 years ago

FYI to anyone reading this: 

- I've had 4 tech visits to my house in the last 3 months. 

- We've had line techs on our street 3 times, with the most recent being yesterday. They confirmed it's a problem with the street, not my house.

- I took it upon myself to escalate to the local supervisor. His tech thought he'd corrected it, but the problem is still happening. 

- I've somehow become the point of contact that asks everyone on the street to continually escalate the issue. 

- I've lost 24-36 hours of my life dealing with this that I'll never get back.

This is pure, complete, and total insanity. Nobody should need to deal with this to get an issue impacting the entire street resolved. I'm convinced that the support script is titled "WAR OF ATTRITION" and is specifically designed to get the customer to give up and quit reporting it. 

Also, if anyone would like a visual representation of what these outages look like, here's a graph:

Why are the outages showing as spikes in the chart, as opposed to gaps? Well, that's because the service has gotten so bad that I rigged up a system to fail the entire house over to a Verizon hotspot when it happens. At least that stays up.

(edited)

Visitor

 • 

13 Messages

3 years ago

4 outages today and it's only 12PM ET. The line techs were out again and attempted more rewiring for the entire street. There seems to be zero methods for relaying this information to the line techs, and instead I'm perpetually stuck dealing with the front-level tech support that makes me go through the exact same troubleshooting steps over and over.

I used to envision the biblical Hell consisting of a shopping mall filled with Apple Stores and staffed by people that write RFPs and RFIs for a living. At this point I believe there's a worse eternal punishment. 

Problem Solver

 • 

1.1K Messages

@Taperchimp 

Thank you for reaching out to the Digital Care Team. I hate to hear this has been your experience and would love to investigate this for you! Please send us a PM with your first and last name, as well as house numbers to your service address. To send us a Private Chat Message, select the message icon in the top right corner and then search for Xfinity support. With our new Xfinity support chat, you do not need to input the name of a person. Just select Xfinity support and you will be able to speak with the next available specialist.

I no longer work for Comcast.

Visitor

 • 

13 Messages

@XfinityHeather I just did. Please understand that this has been going on for months. If I got $20 credit for every time I was told "But do not worry after this you will not get any issue" after reporting an outage, I'd probably own Xfinity at this point. There's about 15 customers on our street that are impacted. Considering this has been going on for months, the entire street would switch providers if we had alternatives. The line maintenance team knows something is wrong, but the troubleshooting seems to involving replacing equipment, waiting to see if it happens again, coming back the following week, replacing more equipment, etc. At this point I feel like they're just guessing at what is causing the outages. 

To put it in perspective: it's impacted my ability to work remotely to the point that I work from my hotspot instead of Xfinity. I can't spend 5-15 minutes of an hour Zoom call waiting for my modem to reconnect. Half of our street works remotely. It's obvious when it goes down because everyone wanders outside to switch over to their phones. 

New Poster

 • 

11 Messages

3 years ago

Yes, he should hijack someone else's help thread. Maybe we can get Comcast to start taking these problems seriously. 

I am a network engineer who consulted with CERN in the specification of the World Wide Web in the 1980s. I brought the country of Kuwait online in 1994 with the first public ISP in the Middle East. I now run a company that builds high-speed Internet distribution systems around the world (Mostly outside the US but we do have a system in Albuquerque NM) and maintains a NOC for DELL. I have had a DHCP problem for over a year at home and have yet to reach anyone in Comcast who even understands the problem. The level of networking knowledge of the technical help staff of Comcast is similar to a power user at home. 

I have an Arris S33 cable modem (Which is a level 1-2 device except to access some basic configuration screens). It connects the Comcast network to a local network at that level. It does not have "modes"  and it is a recommended device from Comcast. I have a problem getting consistent DHCP leases from the Comcast server. Here is a response from Comcast Technical support:

"I'm sorry - to clarify, our DHCP server is set to send an IP to a modem, itself. Your MicroTik router from earlier is a subnetting issue and beyond the demarcation of a residential ISP.

The technician noted that the resolution of the troublecall was for home networking, and our networking engineers would be unable to assist. As a residential ISP we're not able to help with this. I would reach out to support from MicroTik, as our DHCP servers are only assigning external IP addresses to the modem on the account, and your router deals with any subnetting lease times within the scope of residential services. DHCP lease request is client side. If the registered modem on the account is getting the IP, then that's as far as Comcast is able to go on the residential services. I do see that a myriad of agents have tried to assist in the scope that we're able to help with, and even then, our engineering team is not able to assist with subnetting. "

Now the technician they sent against my advice, said: "this problem is way way above a technician's ability to solve, I have no idea why they sent me." Comcast still wanted to charge me 100$ for the tech visit I told them was unnecessary. After speaking to a supervisor and supplying the text message where the Support tech said they would waive the charge, Comcast reversed the charge explaining still that "It was a valid charge". 

So Comcast technical support believes my level 2 device is getting an IP address from the DCHP server. This response is after over 50 pages of back and forth with technical support. And my inability to CONSISTENTLY get an IP lease (I do get them, just not consistently)  from the DHCP server is a "Subnetting issue" which leads me to believe the tech here is dropping technical terms and thinking the customer will not know better. Keeping in mind that this customer (me) runs a company with a network operating center providing monitoring and control to 300+ networks around the US. That system has static addresses from Comcast and we do not face the problem there, only my home network has the problem. 

I have the highest level of service offered to residentials in my area which is supposed to be 1.2 Gbps. What is the offered solution to my problem? 

Comcast:
"I'm sorry that we've reached an impasse here, but if there's anything further my team and I can answer, I'm happy to do so! Once again, we really think a business account would better fit your needs, as those accounts are equipped to handle further dives into the demarcation that you're seeking. Let me know if you have any further questions."

I can sign up for a business account (an increased cost of 200% for equivalent service)  to fix my home technical problems. Keep in mind, my problem is that the DHCP server is not allowing my router, AN ISP CLASS ROUTER, to renew IP leases. When the "Tech" asked about my wifi, I explained that my hot spots (8 of them) are all in bridge mode and operate as two MESH networks. I have no problems in the local network at all which is a /22 net due to the number of devices I have on the net. My only problem is not getting a timely DHCP lease. 

Here is the comment previous to the quoted one above:

"When a modem is in bridge mode, the Static IP routing, LAN DHCP and other settings are disabled. A bridged modem will only assign dynamic public IPs to connected devices in the same manner as a basic cable modem. I know you are very technical so you are likely already aware of this. I believe your current setup would work better with our business services and not our entertainment internet offering. However, I do realize there can be a different need for everyone out there and you have already stated you would not prefer to change that set up. I also see we've mentioned already that we typically do not support home networking equipment owned by you and in a situation where service is being pushed to the modem, that appears to be working and would be the extent of our support options. " 

Here is the worst part, Comcast told me to contact Arris about the problem. After reviewing the "help" I got from Comcast, the Arris tech said, your modem is working properly but Comcast has no idea what they are talking about. 

I am able to work around the problem I have by hand-coding IP addresses and a default route into the router. Then I can get download speeds of up to 1 Gbps. This will be successful until there is a major reconfig at Comcast where I will have to wait until I can get a DHCP lease (Which will typically range from 4 days to 1 hour) and this provides me with the information I need to reconfigure the router when the lease renewal fails.

In many pages of chat text, I found one support tech that asked for a TCP dump (A step in the right direction) but by the time I could supply it, it had shifted to a different tech who could not parse it. Keep in mind here that my router (Mikrotik RB4011) is capable of DHCP logging to the DEBUG level, something I have both pointed out to the support staff and once provided to them. 

Keep in mind, all I have asked for is the DHCP to provide a renewed or new lease when the old one expired. Fully cognizant that the problem could be on my side, I only wanted someone on the other side of the connection to troubleshoot this with me. This has not happened. I was informed that I was asking for too much. 

"Ok, I have an update! I touched base with my support team, explained the situation, and had them read everything over. The general conclusion was that the residential system is working as intended, and that the current ask is outside of what residential services can provide--and you'd be more suited with having a business service installed as a home-based business account, as that can provide the features you need for this particular instance. There are technical and network restrictions when it comes to residential internet services: https://comca.st/37fDD2F"

So maybe if they get enough pressure on their forums, they might start giving their support staff the privileges and training to handle problems like this. 

Visitor

 • 

13 Messages

@macrhino1

I'd run out of fingers and toes if I counted how many times I've explained this issue to support. There is an entire novel of communication with support between texts, onsite visits, and forum chat. It's like living in the movie Groundhog Day. I've run out of ways to explain "the entire street is going down, not just my house". They send out a tech, the tech says the problem is beyond my house, they escalate to the line crew, the line crew doesn't fix it, and the whole process starts over. I know of 6-7 neighbors that are all reporting the same problem, yet Comcast's left hand doesn't seem to be aware of the right hand. At one point we had 4-5 orange cables laying in everyone's front yards since nobody at Comcast though "hey, it's kind of odd that we keep replacing cables on this street". 

Also, don't fall for the business line pitch. My neighbor did since she deals with medical diagnoses. They failed to explain that she's on the same node as residential. Guess what happens? 3x the cost and she keeps going down with the rest of the neighborhood. To quote what I'd sent in chat: 

>I literally tracked down the area supervisor on LinkedIn, got his phone number, and called him in the hopes he could fix it. His guy that he sent out didn't fix it either. No customer should ever need to go through this to resolve a problem with Comcast's node and neighborhood wiring, especially one that had previously been a happy customer for over a decade. I'm running out of ways to explain that this isn't a problem with my house or modem: it's the entire street going down.

New Poster

 • 

11 Messages

@TaperCrimp Yes, Here is the latest "Exchange" from Comcast support. Keep in mind I am not getting my public address renewed. 

"That's certainly not the case, we just really don't have much support when it comes to the LAN side of the modem being outside our demarcation. I ran into kind of a similar issue when I was using my router as a repeater. The DHCP server should send a public WAN IP to the modem which it looks like it is doing since the modem is working. From there the modem/gateway would act as the DHCP server distributing private IP address to the devices. Have you tried using the LAN side IP address (Default Gateway) to configure it? Having it configured from the LAN side of the gateway, should keep the AP from being disconnected no matter if the WAN refreshes. I found this Xfinity business article in the past that was helpful. https://comca.st/3iYVfXi


Now of course my problem is 100% on the WAN side of the router. The Ariss S33 modem does not have a DHCP server process and only acts as a modem. The TECH here has no idea what the problem even is. There is no LAN side of the modem. 

Visitor

 • 

1 Message

It seems like my neighborhood is experiencing almost the same issues as others report here. A few times a week there are 5 minute outages. Neighbors reporting similar issues (haven't corroborated that our outages are at the same time, but strongly suspect so).

Gold Problem Solver

 • 

3.4K Messages

Hello, @NeilPeel. We appreciate you visiting the Xfinity Forums for support. The cause of intermittent connection can be different for each customer. We ask that you please create a new topic of your own here on this board detailing your issue so that the community and our support representatives can assist with your individual issues. :)

I no longer work for Comcast.

forum icon

New to the Community?

Start Here