Skip to main content

    Support

    Offers

SA
sparks.austin99
1st Topic
1st Reply

Visitor

 • 

5 Messages

Thursday, June 17th, 2021 9:39 PM

Closed

Constant T3 errors. Internet keeps dropping in and out all throughout the day.

I have had multiple Xfinity technicians come out. Sometimes, the internet will be fine for a week or more, but then I will have multiple days where the internet is basically unusable.

I have one coax cable going directly from the outside line to my modem. I have tried both Xfinity's modem and my own. Below you can find my connection levels and my event log. This is after a reboot, so the uncorrected/corrected values are way lower than usual. Before I rebooted they were into 7 or 8 digits (if I recall correctly).

It almost certainly seems to be an issue in my area. I have called Xfinity dozens of times, gone through the standard troubleshooting so many times. Is there anything that can be done to get Xfinity to actually fix my issue?

  Downstream Bonded Channels:

   Channel	Lock Status	Modulation	Channel ID	Freq. (MHz)	Pwr (dBmV)	SNR (dB)	Corrected	Uncorrected
   1		Locked		QAM256		5		495.0		2.2		40.0		182		32
   2		Locked		QAM256		2		477.0		2.9		40.7		467		2420
   3		Locked		QAM256		3		483.0		2.1		40.1		919		4758
   4		Locked		QAM256		4		489.0		1.8		40.0		933		4746
   5		Locked		QAM256		6		507.0		3.0		40.2		797		4271
   6		Locked		QAM256		7		513.0		3.8		40.4		1062		5138
   7		Locked		QAM256		8		519.0		4.4		40.4		790		4279
   8		Locked		QAM256		9		525.0		4.5		40.3		710		3770
   9		Locked		QAM256		10		531.0		4.6		40.2		802		4262
   10		Locked		QAM256		11		537.0		4.1		40.1		870		4599
   11		Locked		QAM256		12		543.0		3.4		39.8		971		4702
   12		Locked		QAM256		13		549.0		2.6		39.6		1109		5278
   13		Locked		QAM256		14		555.0		1.9		39.2		992		4777
   14		Locked		QAM256		15		561.0		1.7		39.1		1478		7672
   15		Locked		QAM256		16		567.0		1.5		39.0		1089		5753
   16		Locked		QAM256		17		573.0		1.8		39.1		1127		5709
   17		Locked		QAM256		18		579.0		1.9		39.1		1108		5641
   18		Locked		QAM256		19		585.0		1.9		39.0		1120		5722
   19		Locked		QAM256		20		591.0		1.9		38.9		1148		5687
   20		Locked		QAM256		21		597.0		2.0		38.7		1031		5270
   21		Locked		QAM256		22		603.0		2.0		38.7		1008		5305
   22		Locked		QAM256		23		609.0		2.0		38.9		1857		9249
   23		Locked		QAM256		24		615.0		2.3		39.1		816		4315
   24		Locked		QAM256		25		621.0		2.8		39.0		639		3309
   25		Locked		QAM256		26		627.0		2.5		38.8		973		4912
   26		Locked		QAM256		27		633.0		2.4		38.3		585		2847
   27		Locked		QAM256		28		639.0		2.3		38.2		1032		5265
   28		Locked		QAM256		29		645.0		2.0		39.0		652		3485
   29		Locked		QAM256		30		651.0		1.5		38.8		1038		5475
   30		Locked		QAM256		31		657.0		1.4		38.9		582		2959
   31		Locked		QAM256		32		663.0		1.6		38.8		1014		5455
   32		Locked		OFDM PLC	37		678.0		1.7		38.3		4433487		1074

Upstream Bonded Channels:

   Channel	Lock Status	Channel Type	Channel ID	Symb. Rate (Ksym/sec)	Freq. (MHz)	Pwr (dBmV) 
   1		Locked		SC-QAM		1		5120			35.6		40.5
   2		Locked		SC-QAM		2		5120			29.2		41.3
   3		Locked		SC-QAM		3		5120			22.8		41.8
   4		Locked		SC-QAM		4		5120			16.4		42.3
   5		Locked		SC-QAM		5		1280			39.6		39.5

Event Log (CM-MAC has been redacted):

   16:16:45
Thu Jun 17 2021	 	Critical (3)	 	SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=REDACTED;CMTS-MAC=00:01:5c:7e:e8:60;CM-QOS=1.1;CM-VER=3.1;
   	16:16:51
Thu Jun 17 2021	 	Critical (3)	 	No Ranging Response received - T3 time-out;CM-MAC=REDACTED;CMTS-MAC=00:01:5c:7e:e8:60;CM-QOS=1.1;CM-VER=3.1;
   	16:16:54
Thu Jun 17 2021	 	Critical (3)	 	SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=REDACTED;CMTS-MAC=00:01:5c:7e:e8:60;CM-QOS=1.1;CM-VER=3.1;
   	16:16:58
Thu Jun 17 2021	 	Critical (3)	 	No Ranging Response received - T3 time-out;CM-MAC=REDACTED;CMTS-MAC=00:01:5c:7e:e8:60;CM-QOS=1.1;CM-VER=3.1;
   	16:17:00
Thu Jun 17 2021	 	Critical (3)	 	SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=REDACTED;CMTS-MAC=00:01:5c:7e:e8:60;CM-QOS=1.1;CM-VER=3.1;
   	16:17:06
Thu Jun 17 2021	 	Critical (3)	 	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=REDACTED;CMTS-MAC=00:01:5c:7e:e8:60;CM-QOS=1.1;CM-VER=3.1;
   	16:17:06
Thu Jun 17 2021	 	Critical (3)	 	SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=REDACTED;CMTS-MAC=00:01:5c:7e:e8:60;CM-QOS=1.1;CM-VER=3.1;
   	16:17:07
Thu Jun 17 2021	 	Critical (3)	 	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=REDACTED;CMTS-MAC=00:01:5c:7e:e8:60;CM-QOS=1.1;CM-VER=3.1;
   	16:19:23
Thu Jun 17 2021	 	Critical (3)	 	No Ranging Response received - T3 time-out;CM-MAC=REDACTED;CMTS-MAC=00:01:5c:7e:e8:60;CM-QOS=1.1;CM-VER=3.1;
   	16:19:53
Thu Jun 17 2021	 	Notice (6)	 	Honoring MDD; IP provisioning mode = IPv6
   	16:20:04
Thu Jun 17 2021	 	Notice (6)	 	DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=REDACTED;CMTS-MAC=00:01:5c:7e:e8:60;CM-QOS=1.1;CM-VER=3.1;
   	16:20:13
Thu Jun 17 2021	 	Critical (3)	 	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=REDACTED;CMTS-MAC=00:01:5c:7e:e8:60;CM-QOS=1.1;CM-VER=3.1;
   	16:25:51
Thu Jun 17 2021	 	Critical (3)	 	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=REDACTED;CMTS-MAC=00:01:5c:7e:e8:60;CM-QOS=1.1;CM-VER=3.1;
   	16:25:52
Thu Jun 17 2021	 	Critical (3)	 	SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=REDACTED;CMTS-MAC=00:01:5c:7e:e8:60;CM-QOS=1.1;CM-VER=3.1;
   	16:25:53
Thu Jun 17 2021	 	Critical (3)	 	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=REDACTED;CMTS-MAC=00:01:5c:7e:e8:60;CM-QOS=1.1;CM-VER=3.1;
   	16:25:56
Thu Jun 17 2021	 	Critical (3)	 	SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=REDACTED;CMTS-MAC=00:01:5c:7e:e8:60;CM-QOS=1.1;CM-VER=3.1;
   	16:25:58
Thu Jun 17 2021	 	Critical (3)	 	No Ranging Response received - T3 time-out;CM-MAC=REDACTED;CMTS-MAC=00:01:5c:7e:e8:60;CM-QOS=1.1;CM-VER=3.1;
   	16:26:00
Thu Jun 17 2021	 	Critical (3)	 	SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=REDACTED;CMTS-MAC=00:01:5c:7e:e8:60;CM-QOS=1.1;CM-VER=3.1;
   	16:26:04
Thu Jun 17 2021	 	Critical (3)	 	No Ranging Response received - T3 time-out;CM-MAC=REDACTED;CMTS-MAC=00:01:5c:7e:e8:60;CM-QOS=1.1;CM-VER=3.1;
   	16:26:04
Thu Jun 17 2021	 	Critical (3)	 	SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=REDACTED;CMTS-MAC=00:01:5c:7e:e8:60;CM-QOS=1.1;CM-VER=3.1;
   	16:26:09
Thu Jun 17 2021	 	Critical (3)	 	No Ranging Response received - T3 time-out;CM-MAC=REDACTED;CMTS-MAC=00:01:5c:7e:e8:60;CM-QOS=1.1;CM-VER=3.1;
   	16:26:19
Thu Jun 17 2021	 	Critical (3)	 	SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=REDACTED;CMTS-MAC=00:01:5c:7e:e8:60;CM-QOS=1.1;CM-VER=3.1;
   	16:26:19
Thu Jun 17 2021	 	Critical (3)	 	No Ranging Response received - T3 time-out;CM-MAC=REDACTED;CMTS-MAC=00:01:5c:7e:e8:60;CM-QOS=1.1;CM-VER=3.1;
   	16:26:26
Thu Jun 17 2021	 	Critical (3)	 	SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=REDACTED;CMTS-MAC=00:01:5c:7e:e8:60;CM-QOS=1.1;CM-VER=3.1;
   	16:30:45
Thu Jun 17 2021	 	Critical (3)	 	No Ranging Response received - T3 time-out;CM-MAC=REDACTED;CMTS-MAC=00:01:5c:7e:e8:60;CM-QOS=1.1;CM-VER=3.1;
   	16:32:10
Thu Jun 17 2021	 	Notice (6)	 	Honoring MDD; IP provisioning mode = IPv6
   	16:32:22
Thu Jun 17 2021	 	Notice (6)	 	DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=REDACTED;CMTS-MAC=00:01:5c:7e:e8:60;CM-QOS=1.1;CM-VER=3.1;
   	16:32:31
Thu Jun 17 2021	 	Critical (3)	 	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=REDACTED;CMTS-MAC=00:01:5c:7e:e8:60;CM-QOS=1.1;CM-VER=3.1;
   	16:32:38
Thu Jun 17 2021	 	Notice (6)	 	CM-STATUS message sent. Event Type Code: 5; Chan ID: 11 12 13 14 15 16 17 18 19; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=REDACTED;CMTS-MAC=00:01:5c:7e:e8:60;CM-QOS=1.1;CM-VER=3.1;
   	16:32:43
Thu Jun 17 2021	 	Notice (6)	 	CM-STATUS message sent. Event Type Code: 4; Chan ID: 11 12 13 14 15 16 17 18 19; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=REDACTED;CMTS-MAC=00:01:5c:7e:e8:60;CM-QOS=1.1;CM-VER=3.1;
   	16:32:50
Thu Jun 17 2021	 	Critical (3)	 	SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=REDACTED;CMTS-MAC=00:01:5c:7e:e8:60;CM-QOS=1.1;CM-VER=3.1;
   	16:32:54
Thu Jun 17 2021	 	Critical (3)	 	No Ranging Response received - T3 time-out;CM-MAC=REDACTED;CMTS-MAC=00:01:5c:7e:e8:60;CM-QOS=1.1;CM-VER=3.1;

Question

 • 

Updated 

4 years ago

 • Edited

100

3

0

This conversation is no longer open for comments or replies and is no longer visible to community members.

sparks.austin99

Visitor

 • 

5 Messages

4 years ago

Please? Even a reply is better than nothing. [Edited - abbreviated profanity] 

(edited)

3

0

XfinityJamesC

Official Employee

 • 

2.2K Messages

Greetings, @sparks.austin99! Thanks so much for taking a moment out of your busy day to leave a post on our community forum. I'm sorry to hear you're having issues with your service, but you have definitely come to the right place for assistance.

 

Thank you for providing all the relevant details about your connection issues and timeout errors. That sort of signal interference usually warrants a technician visit, but you said that you have already had multiple visits. Can you tell me what ever came of them? Was anything referred on to a maintenance team, or did the issue always clear up before any meaningful investigation could be initiated?

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

4 years ago

0

sparks.austin99

Visitor

 • 

5 Messages

One of them said they would escalate the issue, but nothing seems to have come of that. Sometimes the issues would clear up after a visit, sometimes not. Since the problems are intermittent, it's hard to predict if the problems will be present when a technician is here. A few days ago, I wrote a program to monitor my internet speeds, and as you can see, there have been multiple outages:

4 years ago

0

user_PeterC

Contributor

 • 

150 Messages

I appreciate the additional information @sparks.austin99 , and I know it can definitely be a bit tricky to pinpoint the issue, or to have the issue replicated while the technician is out since it can be intermittent, but I definitely want to see what we can do to help get a resolution on this for you. Please send us a Live Chat with your first and last name as well as your service address so we can assist. 
 
To send a Live Chat, click the Peer to Peer chat icon at the top right of the page and enter Xfinity Support in the "To" section of the chat.

4 years ago

0

sparks.austin99

Visitor

 • 

5 Messages

4 years ago

I'm having these same issues again. Nothing in my setup has changed. The internet was down for multiple days while Xfinity was doing "maintenance." The internet worked for maybe a week, but now the same issues are presenting themselves again. This is infuriating. Posting the logs below:

Event Log:

  17:40:46
Tue Jul 6 2021		   Critical (3)   No Ranging Response received - T3 time-out;CM-MAC=REDACTED;CMTS-MAC=00:01:5c:7e:e8:60;CM-QOS=1.1;CM-VER=3.1;
    17:40:52
Tue Jul 6 2021		   Critical (3)   SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=REDACTED;CMTS-MAC=00:01:5c:7e:e8:60;CM-QOS=1.1;CM-VER=3.1;
    17:41:01
Tue Jul 6 2021		   Critical (3)   No Ranging Response received - T3 time-out;CM-MAC=REDACTED;CMTS-MAC=00:01:5c:7e:e8:60;CM-QOS=1.1;CM-VER=3.1;
    17:41:03
Tue Jul 6 2021		   Critical (3)   SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=REDACTED;CMTS-MAC=00:01:5c:7e:e8:60;CM-QOS=1.1;CM-VER=3.1;
    17:41:06
Tue Jul 6 2021		   Critical (3)   No Ranging Response received - T3 time-out;CM-MAC=REDACTED;CMTS-MAC=00:01:5c:7e:e8:60;CM-QOS=1.1;CM-VER=3.1;
    17:41:07
Tue Jul 6 2021		   Critical (3)   SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=REDACTED;CMTS-MAC=00:01:5c:7e:e8:60;CM-QOS=1.1;CM-VER=3.1;
    17:41:12
Tue Jul 6 2021		   Critical (3)   No Ranging Response received - T3 time-out;CM-MAC=REDACTED;CMTS-MAC=00:01:5c:7e:e8:60;CM-QOS=1.1;CM-VER=3.1;
    17:41:14
Tue Jul 6 2021		   Critical (3)   SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=REDACTED;CMTS-MAC=00:01:5c:7e:e8:60;CM-QOS=1.1;CM-VER=3.1;
    17:41:17
Tue Jul 6 2021		   Critical (3)   No Ranging Response received - T3 time-out;CM-MAC=REDACTED;CMTS-MAC=00:01:5c:7e:e8:60;CM-QOS=1.1;CM-VER=3.1;
    17:41:18
Tue Jul 6 2021		   Critical (3)   SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=REDACTED;CMTS-MAC=00:01:5c:7e:e8:60;CM-QOS=1.1;CM-VER=3.1;
    17:41:24
Tue Jul 6 2021		   Critical (3)   No Ranging Response received - T3 time-out;CM-MAC=REDACTED;CMTS-MAC=00:01:5c:7e:e8:60;CM-QOS=1.1;CM-VER=3.1;
    17:41:26
Tue Jul 6 2021		   Critical (3)   SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=REDACTED;CMTS-MAC=00:01:5c:7e:e8:60;CM-QOS=1.1;CM-VER=3.1;
    17:41:28
Tue Jul 6 2021		   Critical (3)   No Ranging Response received - T3 time-out;CM-MAC=REDACTED;CMTS-MAC=00:01:5c:7e:e8:60;CM-QOS=1.1;CM-VER=3.1;
    17:41:30
Tue Jul 6 2021		   Critical (3)   SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=REDACTED;CMTS-MAC=00:01:5c:7e:e8:60;CM-QOS=1.1;CM-VER=3.1;
    17:41:34
Tue Jul 6 2021		   Critical (3)   No Ranging Response received - T3 time-out;CM-MAC=REDACTED;CMTS-MAC=00:01:5c:7e:e8:60;CM-QOS=1.1;CM-VER=3.1;
    17:41:36
Tue Jul 6 2021		   Critical (3)   SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=REDACTED;CMTS-MAC=00:01:5c:7e:e8:60;CM-QOS=1.1;CM-VER=3.1;
    17:41:39
Tue Jul 6 2021		   Critical (3)   No Ranging Response received - T3 time-out;CM-MAC=REDACTED;CMTS-MAC=00:01:5c:7e:e8:60;CM-QOS=1.1;CM-VER=3.1;
    17:41:40
Tue Jul 6 2021		   Critical (3)   SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=REDACTED;CMTS-MAC=00:01:5c:7e:e8:60;CM-QOS=1.1;CM-VER=3.1;
    17:41:42
Tue Jul 6 2021		   Critical (3)   No Ranging Response received - T3 time-out;CM-MAC=REDACTED;CMTS-MAC=00:01:5c:7e:e8:60;CM-QOS=1.1;CM-VER=3.1;
    17:41:44
Tue Jul 6 2021		   Critical (3)   SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=REDACTED;CMTS-MAC=00:01:5c:7e:e8:60;CM-QOS=1.1;CM-VER=3.1;
    17:41:49
Tue Jul 6 2021		   Critical (3)   No Ranging Response received - T3 time-out;CM-MAC=REDACTED;CMTS-MAC=00:01:5c:7e:e8:60;CM-QOS=1.1;CM-VER=3.1;
    17:41:50
Tue Jul 6 2021		   Critical (3)   SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=REDACTED;CMTS-MAC=00:01:5c:7e:e8:60;CM-QOS=1.1;CM-VER=3.1;
    17:41:54
Tue Jul 6 2021		   Critical (3)   No Ranging Response received - T3 time-out;CM-MAC=REDACTED;CMTS-MAC=00:01:5c:7e:e8:60;CM-QOS=1.1;CM-VER=3.1;
    17:41:58
Tue Jul 6 2021		   Critical (3)   SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=REDACTED;CMTS-MAC=00:01:5c:7e:e8:60;CM-QOS=1.1;CM-VER=3.1;
    17:41:59
Tue Jul 6 2021		   Critical (3)   SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=REDACTED;CMTS-MAC=00:01:5c:7e:e8:60;CM-QOS=1.1;CM-VER=3.1;
    17:42:02
Tue Jul 6 2021		   Critical (3)   No Ranging Response received - T3 time-out;CM-MAC=REDACTED;CMTS-MAC=00:01:5c:7e:e8:60;CM-QOS=1.1;CM-VER=3.1;
    17:42:04
Tue Jul 6 2021		   Critical (3)   SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=REDACTED;CMTS-MAC=00:01:5c:7e:e8:60;CM-QOS=1.1;CM-VER=3.1;
    17:42:06
Tue Jul 6 2021		   Critical (3)   No Ranging Response received - T3 time-out;CM-MAC=REDACTED;CMTS-MAC=00:01:5c:7e:e8:60;CM-QOS=1.1;CM-VER=3.1;
    17:42:08
Tue Jul 6 2021		   Critical (3)   SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=REDACTED;CMTS-MAC=00:01:5c:7e:e8:60;CM-QOS=1.1;CM-VER=3.1;
    17:44:19
Tue Jul 6 2021		   Critical (3)   No Ranging Response received - T3 time-out;CM-MAC=REDACTED;CMTS-MAC=00:01:5c:7e:e8:60;CM-QOS=1.1;CM-VER=3.1;
    17:45:17
Tue Jul 6 2021		   Notice (6)   Honoring MDD; IP provisioning mode = IPv6
    17:45:27
Tue Jul 6 2021		   Notice (6)   DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=REDACTED;CMTS-MAC=00:01:5c:7e:e8:60;CM-QOS=1.1;CM-VER=3.1;

Connection:

  Downstream Bonded Channels  
  
   Channel Lock Status Modulation Channel ID Freq. (MHz) Pwr (dBmV) SNR (dB) Corrected Uncorrected
   1 Locked QAM256 13 549.0 0.4 39.5 1039 418
   2 Locked QAM256 1 471.0 0.9 40.7 17688 86911
   3 Locked QAM256 2 477.0 0.5 40.5 23754 118396
   4 Locked QAM256 3 483.0 0.0 40.0 26908 131938
   5 Locked QAM256 4 489.0 0.0 39.9 29588 136734
   6 Locked QAM256 5 495.0 0.3 39.9 24648 112962
   7 Locked QAM256 6 507.0 0.8 40.2 24043 117797
   8 Locked QAM256 7 513.0 1.3 40.3 22994 116524
   9 Locked QAM256 8 519.0 1.9 40.3 24812 125204
   10 Locked QAM256 9 525.0 2.3 40.4 24214 121541
   11 Locked QAM256 10 531.0 2.6 40.4 25735 124624
   12 Locked QAM256 11 537.0 2.3 40.0 25304 120366
   13 Locked QAM256 12 543.0 1.4 39.8 33743 141794
   14 Locked QAM256 14 555.0 -0.7 39.0 33056 132067
   15 Locked QAM256 15 561.0 -1.1 38.7 35740 140514
   16 Locked QAM256 16 567.0 -1.5 38.6 38425 150058
   17 Locked QAM256 17 573.0 -1.2 38.7 35828 137240
   18 Locked QAM256 18 579.0 -0.7 38.8 40090 160128
   19 Locked QAM256 19 585.0 0.0 39.0 43233 166839
   20 Locked QAM256 33 447.0 3.1 41.6 39871 147931
   21 Locked QAM256 34 453.0 2.9 41.4 41081 140062
   22 Locked QAM256 35 459.0 2.4 41.4 41384 143796
   23 Locked QAM256 36 465.0 1.7 41.1 43910 140874
   24 Locked OFDM PLC 37 678.0 0.0 38.0 819391587 39619
   25 Locked QAM256 38 423.0 2.2 41.5 36614 140324
   26 Locked QAM256 39 429.0 2.5 41.6 37182 136828
   27 Locked QAM256 40 435.0 2.8 41.6 38490 134925
   28 Locked QAM256 41 441.0 2.9 41.5 42786 146196
   29 Locked QAM256 42 399.0 3.1 41.8 35408 138061
   30 Locked QAM256 43 405.0 2.9 41.6 50796 142599
   31 Locked QAM256 44 411.0 2.6 41.7 56988 165223
   32 Locked QAM256 45 417.0 2.3 41.6 57802 134545


   Upstream Bonded Channels  
  
   Channel Lock Status Channel Type Channel ID Symb. Rate (Ksym/sec) Freq. (MHz) Pwr (dBmV)
   1 Locked SC-QAM 1 5120 35.6 43.5
   2 Locked SC-QAM 2 5120 29.2 44.5
   3 Locked SC-QAM 3 5120 22.8 44.5
   4 Locked SC-QAM 4 5120 16.4 45.3
   5 Locked SC-QAM 5 1280 39.6 42.5

My own graph of the past few days:

1

0

XfinityBrie

Administrator

 • 

672 Messages

Hi there @sparks.austin99 thank you for the screenshots and the detailed logs, they help out tremendously. I'm sorry to hear about the drops you're experiencing, the graph you provided shows them happening on a far more frequent basis than I'd want any of my valued customers experiencing.

 

We're able to check the network health remotely, as well as run a 30-day report on the node that services your area. Any repairs or maintenance referrals would come from a field technician however, as they have to submit a signal report from the premise at the time of the referral. 

 

As I'd need your service address and account information to perform any tests, I'd ask you send us a private peer-to-peer chat through our support tools here on the forums;

 

To send a peer-to-peer chat:

  • Ensure you are first signed in, then you will see an icon at the top right of your page. Click that or follow this link: https://comca.st/3AM3Ymn
  • From there, click the 'New Message' icon. In the 'To' field, type 'Xfinity Support'.
  • Type your message in the text area that appears at the bottom of the window and hit enter to send. An official employee, such as myself or whoever is first available, will respond.

We ask that you please include your name, the account holder name (if different), and the service address alongside your inquiry so we can best assist. 

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

4 years ago

0

forum icon

New to the Community?

Start Here