John_H3's profile

Contributor

 • 

40 Messages

Wednesday, May 27th, 2020 6:00 AM

Closed

Xfinity 100 Mbps connection keeps dropping (intermittent) multiple times per hour

Hi All,

 

I am reaching out to see if someone can help me with my internet connection. I am experiencing huge issues. My internet connection keeps randomly dropping every 10 minutes, or so. It stays down for 1 to 2 minutes (usually, but it can stay down for longer, up to 5-10 minutes), then comes back. As an example, in the last 6 hours, it dropped 34x times, being down for almost 25% of the time. I need to work from home, vpn, t-calls, etc. and this is just not working. Unfortunate.

 

Some background. I have moved to a new apartment ~9 months ago. Internet has been working just fine until about ~6-7 weeks ago. Then the intermitted connection problem showed up.

 

My equipment. I have been using for the last ~6 years an Arris sb6141 (modem) with an Apple AirPort Extreme (router). I talked to Xfinity customer service and they blamed right away my modem/router. I was not very convinced (just because cause the combo has been working fine for years until few weeks ago), however, following their recommendation, I got a new modem from the list of Xfinity recommended devices (Netgear CM600), and a new router, too (Google Nest). Unfortunately, the problem remained.

 

Xfinity Technician. I contacted back Xfinity support and then they decided to send a technician to check my building and apartment. The technician was here, and checked everything in both the basement and apartment, installed new filters, replaced switches, etc. He did not found anything wrong on my side, however, he could not solve the problem, but he acknowledged the intermitted issue.

 

He then sent it another ticket to have someone to come and check the post next to my apartment and connection getting to my building. They were supposed to be here yesterday morning, however, unfortunately, no-one showed up yet.

 

I will post below logs from my modem. I am hoping someone here can give some wise insight about what I should do next. Having to work from home and having internet going down every 10 mins is like to having an internet connection 😐

 

Thanks everyone in advance, ~JH

 

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

Accepted Solution

Contributor

 • 

40 Messages

5 years ago

A last update which hopefully is the end of the story. It seems that I was finally able to pin-down my internet issue. It seems that the problem was about a sub-optimal connection outside my building. I had 2x technicians coming here a few weeks ago, checking all inside connections without finding an issue. Did not help, so I got a third technician to came out 2 days ago. This time I asked him to check the connections outside the building. He remade the termination for the cable that from a splitter from a Comcast central unit is getting to my building an apartment and further tighten all other connection. Since then, 72 hours have gone by and have not had a single T3-T4 error, yet - looks promising. Hope it stays this way

 

The only advice from this story I have for people with the same issue is to be persistent, get technicians out, give them as many details you need, try to understand yourself how wiring is done for you inside and outside your building, and keep going until the issue is fixed 🙂

 

It has been real painful for me not having an internet connection for the last 3 months, and not always easy to deal with the customer support, but at last the third technician coming out was a really good guy willing to help and listen, and together we figured out how to solve the issue.

 

If the problem will come back, I will open a new post, but hopefully I will be good for a while now...

Contributor

 • 

40 Messages

5 years ago

And this is the event log from the modem

 

Time Priority Description
2020-05-27, 07:06:22 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=08:36:c9:c1:69:40;CMTS-MAC=18:8b:9d:d4:08:ec;CM-QOS=1.1;CM-VER=3.0;
2020-05-27, 07:05:50 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=08:36:c9:c1:69:40;CMTS-MAC=18:8b:9d:d4:08:ec;CM-QOS=1.1;CM-VER=3.0;
2020-05-27, 07:05:49 Warning (5) Dynamic Range Window violation
2020-05-27, 07:05:37 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=08:36:c9:c1:69:40;CMTS-MAC=18:8b:9d:d4:08:ec;CM-QOS=1.1;CM-VER=3.0;
2020-05-27, 03:45:03 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=08:36:c9:c1:69:40;CMTS-MAC=18:8b:9d:d4:08:ec;CM-QOS=1.1;CM-VER=3.0;
2020-05-27, 03:45:03 Warning (5) Dynamic Range Window violation
2020-05-27, 01:16:36 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=08:36:c9:c1:69:40;CMTS-MAC=18:8b:9d:d4:08:ec;CM-QOS=1.1;CM-VER=3.0;
2020-05-27, 01:16:23 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=08:36:c9:c1:69:40;CMTS-MAC=18:8b:9d:d4:08:ec;CM-QOS=1.1;CM-VER=3.0;
2020-05-27, 01:16:03 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=08:36:c9:c1:69:40;CMTS-MAC=18:8b:9d:d4:08:ec;CM-QOS=1.1;CM-VER=3.0;
2020-05-27, 01:16:03 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=08:36:c9:c1:69:40;CMTS-MAC=18:8b:9d:d4:08:ec;CM-QOS=1.1;CM-VER=3.0;
2020-05-27, 01:01:55 Warning (5) Dynamic Range Window violation
2020-05-27, 01:01:54 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=08:36:c9:c1:69:40;CMTS-MAC=18:8b:9d:d4:08:ec;CM-QOS=1.1;CM-VER=3.0;
2020-05-27, 00:00:58 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=08:36:c9:c1:69:40;CMTS-MAC=18:8b:9d:d4:08:ec;CM-QOS=1.1;CM-VER=3.0;
2020-05-27, 00:00:21 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=08:36:c9:c1:69:40;CMTS-MAC=18:8b:9d:d4:08:ec;CM-QOS=1.1;CM-VER=3.0;
2020-05-26, 23:59:53 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=08:36:c9:c1:69:40;CMTS-MAC=18:8b:9d:d4:08:ec;CM-QOS=1.1;CM-VER=3.0;
2020-05-26, 23:59:44 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=08:36:c9:c1:69:40;CMTS-MAC=18:8b:9d:d4:08:ec;CM-QOS=1.1;CM-VER=3.0;
2020-05-26, 23:49:04 Warning (5) Dynamic Range Window violation
2020-05-26, 23:48:56 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=08:36:c9:c1:69:40;CMTS-MAC=18:8b:9d:d4:08:ec;CM-QOS=1.1;CM-VER=3.0;
2020-05-26, 23:28:22 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=08:36:c9:c1:69:40;CMTS-MAC=18:8b:9d:d4:08:ec;CM-QOS=1.1;CM-VER=3.0;
2020-05-26, 23:27:17 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=08:36:c9:c1:69:40;CMTS-MAC=18:8b:9d:d4:08:ec;CM-QOS=1.1;CM-VER=3.0;
2020-05-26, 23:27:06 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=08:36:c9:c1:69:40;CMTS-MAC=18:8b:9d:d4:08:ec;CM-QOS=1.1;CM-VER=3.0;
2020-05-26, 23:26:53 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=08:36:c9:c1:69:40;CMTS-MAC=18:8b:9d:d4:08:ec;CM-QOS=1.1;CM-VER=3.0;
2020-05-26, 23:26:26 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=08:36:c9:c1:69:40;CMTS-MAC=18:8b:9d:d4:08:ec;CM-QOS=1.1;CM-VER=3.0;
2020-05-26, 23:25:53 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=08:36:c9:c1:69:40;CMTS-MAC=18:8b:9d:d4:08:ec;CM-QOS=1.1;CM-VER=3.0;
2020-05-26, 22:41:22 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=08:36:c9:c1:69:40;CMTS-MAC=18:8b:9d:d4:08:ec;CM-QOS=1.1;CM-VER=3.0;
2020-05-26, 22:38:06 Warning (5) Dynamic Range Window violation
2020-05-26, 22:38:05 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=08:36:c9:c1:69:40;CMTS-MAC=18:8b:9d:d4:08:ec;CM-QOS=1.1;CM-VER=3.0;
2020-05-26, 19:48:49 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=08:36:c9:c1:69:40;CMTS-MAC=18:8b:9d:d4:08:ec;CM-QOS=1.1;CM-VER=3.0;
2020-05-26, 19:48:49 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=08:36:c9:c1:69:40;CMTS-MAC=18:8b:9d:d4:08:ec;CM-QOS=1.1;CM-VER=3.0;
2020-05-26, 19:48:16 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=08:36:c9:c1:69:40;CMTS-MAC=18:8b:9d:d4:08:ec;CM-QOS=1.1;CM-VER=3.0;
2020-05-26, 19:48:04 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=08:36:c9:c1:69:40;CMTS-MAC=18:8b:9d:d4:08:ec;CM-QOS=1.1;CM-VER=3.0;
2020-05-26, 19:46:07 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=08:36:c9:c1:69:40;CMTS-MAC=18:8b:9d:d4:08:ec;CM-QOS=1.1;CM-VER=3.0;
2020-05-26, 19:45:59 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=08:36:c9:c1:69:40;CMTS-MAC=18:8b:9d:d4:08:ec;CM-QOS=1.1;CM-VER=3.0;
2020-05-26, 19:45:34 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=08:36:c9:c1:69:40;CMTS-MAC=18:8b:9d:d4:08:ec;CM-QOS=1.1;CM-VER=3.0;
2020-05-26, 19:25:06 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=08:36:c9:c1:69:40;CMTS-MAC=18:8b:9d:d4:08:ec;CM-QOS=1.1;CM-VER=3.0;
2020-05-26, 19:24:41 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=08:36:c9:c1:69:40;CMTS-MAC=18:8b:9d:d4:08:ec;CM-QOS=1.1;CM-VER=3.0;
2020-05-26, 19:24:34 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=08:36:c9:c1:69:40;CMTS-MAC=18:8b:9d:d4:08:ec;CM-QOS=1.1;CM-VER=3.0;
2020-05-26, 19:24:01 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=08:36:c9:c1:69:40;CMTS-MAC=18:8b:9d:d4:08:ec;CM-QOS=1.1;CM-VER=3.0;
2020-05-26, 19:23:29 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=08:36:c9:c1:69:40;CMTS-MAC=18:8b:9d:d4:08:ec;CM-QOS=1.1;CM-VER=3.0;
2020-05-26, 19:23:21 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=08:36:c9:c1:69:40;CMTS-MAC=18:8b:9d:d4:08:ec;CM-QOS=1.1;CM-VER=3.0;

Contributor

 • 

40 Messages

5 years ago

this is modem connection - as you can see, power and SNR values are looking good, however a lot of 'uncorrectables' - let me know if I am missing something here

 

Starting Frequency
 
Startup Procedure
Procedure Status Comment
Acquire Downstream Channel 459000000 Hz Locked
Connectivity State OK Operational
Boot State OK Operational
Security Enable BPI+
IP Provisioning Mode Honor MDD IPv6 only
 
Downstream Bonded Channels
Channel Lock Status Modulation Channel ID Frequency Power SNR Correctables Uncorrectables
1 Locked QAM256 1 459000000 Hz -1.4 dBmV 40.1 dB 21196 9113
2 Locked QAM256 17 555000000 Hz -1.2 dBmV 40.0 dB 11373 4681
3 Locked QAM256 18 561000000 Hz -1.2 dBmV 39.9 dB 11407 4538
4 Locked QAM256 19 567000000 Hz -1.3 dBmV 39.9 dB 11095 4053
5 Locked QAM256 20 573000000 Hz -1.7 dBmV 39.7 dB 11187 4788
6 Locked QAM256 21 579000000 Hz -1.6 dBmV 39.8 dB 10776 3621
7 Locked QAM256 22 585000000 Hz -1.6 dBmV 39.7 dB 10243 3783
8 Locked QAM256 23 591000000 Hz -1.6 dBmV 39.7 dB 9813 4100
9 Locked QAM256 24 597000000 Hz -1.7 dBmV 38.8 dB 9318 3455
10 Locked QAM256 2 465000000 Hz -1.4 dBmV 40.0 dB 19247 7606
11 Locked QAM256 3 471000000 Hz -1.5 dBmV 40.0 dB 17291 7749
12 Locked QAM256 4 477000000 Hz -1.7 dBmV 39.9 dB 18070 7455
13 Locked QAM256 5 483000000 Hz -1.7 dBmV 39.9 dB 17662 7142
14 Locked QAM256 6 489000000 Hz -1.7 dBmV 40.0 dB 17511 7258
15 Locked QAM256 7 495000000 Hz -1.7 dBmV 39.9 dB 15374 6632
16 Locked QAM256 8 501000000 Hz -1.7 dBmV 39.8 dB 15121 5947
17 Locked QAM256 9 507000000 Hz -1.9 dBmV 40.8 dB 0 0
18 Locked QAM256 10 513000000 Hz -2.2 dBmV 40.8 dB 0 0
19 Locked QAM256 11 519000000 Hz -2.1 dBmV 40.8 dB 0 0
20 Locked QAM256 12 525000000 Hz -2.1 dBmV 40.8 dB 0 0
21 Locked QAM256 13 531000000 Hz -1.8 dBmV 40.8 dB 0 0
22 Locked QAM256 14 537000000 Hz -1.8 dBmV 40.8 dB 0 0
23 Locked QAM256 15 543000000 Hz -2.0 dBmV 40.8 dB 0 0
24 Locked QAM256 16 549000000 Hz -1.8 dBmV 40.8 dB 0 0
 
Upstream Bonded Channels
Channel Lock Status US Channel Type Channel ID Symbol Rate Frequency Power
1 Locked ATDMA 5 5120 Ksym/sec 36500000 Hz 42.3 dBmV
2 Locked ATDMA 6 5120 Ksym/sec 30100000 Hz 41.8 dBmV
3 Locked ATDMA 7 5120 Ksym/sec 23700000 Hz 42.0 dBmV
4 Locked ATDMA 8 5120 Ksym/sec 17300000 Hz 42.5 dBmV
5 Not Locked Unknown 0 0 Ksym/sec 0 Hz 0.0 dBmV
6 Not Locked Unknown 0 0 Ksym/sec 0 Hz 0.0 dBmV
7 Not Locked Unknown 0 0 Ksym/sec 0 Hz 0.0 dBmV
8 Not Locked Unknown 0 0 Ksym/sec 0 Hz 0.0 dBmV
 
Current System Time: Wed May 27 08:17:57 2020
System Up Time: 15:54:56

Expert

 • 

111.4K Messages

5 years ago

Even though the signal stats looked o/k at that snapshot in time, the error log entries confirm that something is going on. Perhaps there is noise ingress into the line(s) somewhere.

 

There are other signal stat figures that can't be read by the modem. They are the "Upstream Rx Power" (Upstream Receive Power Level), the "Upstream SNR Ch." (Upstream Signal To Noise Ratio), and the "Upstream ICFR" (In Channel Frequency Response). These are as equally important in diagnosing connectivity issues as are the modem's stats.


I'm going to escalate your issue to the Comcast corporate employees that are available to these boards. They can check the CMTS (Cable Modem Termination System) for any real time degradation and / or error reports, see your node / cable plant and modem health, and see whether or not everything is in the green zone. They can also see a history plot for the modem and poll for those upstream receive signal stats.

You should get a reply here in your topic. Good luck !

Contributor

 • 

40 Messages

5 years ago

could it be that it's the ISP  that drops the connection and not my router/modem?

Official Employee

 • 

6.9K Messages

5 years ago

Hi @John_H3

 

Thank you for posting and welcome to the Xfinity Forum! I agree with @EG. I'd be more than happy to investigate your issues a little more to see what we need to do to make this right. To get started, please send me a private message with your first and last name. To send a private message, click on "ComcastChe" and then click send a message. 

Contributor

 • 

40 Messages

5 years ago

Great - I will get in touch through private messaging

p.s., I hope we can improve it soon - working from home with a connection dropping multiple times an hour is literally killing me

Contributor

 • 

40 Messages

5 years ago

Thank you so much for your help EG! I would be glad to be working with Xfinity tech support team and figure our the problem

Contributor

 • 

40 Messages

5 years ago

and this are the log from this afternoon - it has been really bad

 

Time Priority Description
2020-05-27, 17:42:24 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=08:36:c9:c1:69:40;CMTS-MAC=18:8b:9d:d4:08:ec;CM-QOS=1.1;CM-VER=3.0;
2020-05-27, 17:01:04 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=08:36:c9:c1:69:40;CMTS-MAC=18:8b:9d:d4:08:ec;CM-QOS=1.1;CM-VER=3.0;
2020-05-27, 17:00:19 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=08:36:c9:c1:69:40;CMTS-MAC=18:8b:9d:d4:08:ec;CM-QOS=1.1;CM-VER=3.0;
2020-05-27, 16:58:48 Critical (3) No UCDs Received - Timeout;;CM-MAC=08:36:c9:c1:69:40;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2020-05-27, 16:58:31 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=08:36:c9:c1:69:40;CMTS-MAC=18:8b:9d:d4:08:ec;CM-QOS=1.0;CM-VER=3.0;
2020-05-27, 16:58:27 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=08:36:c9:c1:69:40;CMTS-MAC=18:8b:9d:d4:08:ec;CM-QOS=1.1;CM-VER=3.0;
2020-05-27, 16:57:45 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=08:36:c9:c1:69:40;CMTS-MAC=18:8b:9d:d4:08:ec;CM-QOS=1.0;CM-VER=3.0;
2020-05-27, 16:57:39 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=08:36:c9:c1:69:40;CMTS-MAC=18:8b:9d:d4:08:ec;CM-QOS=1.1;CM-VER=3.0;
2020-05-27, 16:56:49 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=08:36:c9:c1:69:40;CMTS-MAC=18:8b:9d:d4:08:ec;CM-QOS=1.0;CM-VER=3.0;
2020-05-27, 16:56:48 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=08:36:c9:c1:69:40;CMTS-MAC=18:8b:9d:d4:08:ec;CM-QOS=1.0;CM-VER=3.0;
2020-05-27, 16:56:15 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=08:36:c9:c1:69:40;CMTS-MAC=18:8b:9d:d4:08:ec;CM-QOS=1.0;CM-VER=3.0;
2020-05-27, 16:55:52 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=08:36:c9:c1:69:40;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2020-05-27, 16:55:50 Critical (3) No UCDs Received - Timeout;;CM-MAC=08:36:c9:c1:69:40;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2020-05-27, 16:55:33 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=08:36:c9:c1:69:40;CMTS-MAC=18:8b:9d:d4:08:ec;CM-QOS=1.0;CM-VER=3.0;
2020-05-27, 16:55:32 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=08:36:c9:c1:69:40;CMTS-MAC=18:8b:9d:d4:08:ec;CM-QOS=1.0;CM-VER=3.0;
2020-05-27, 16:55:31 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=08:36:c9:c1:69:40;CMTS-MAC=18:8b:9d:d4:08:ec;CM-QOS=1.0;CM-VER=3.0;
2020-05-27, 16:55:19 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=08:36:c9:c1:69:40;CMTS-MAC=18:8b:9d:d4:08:ec;CM-QOS=1.0;CM-VER=3.0;
2020-05-27, 16:55:18 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=08:36:c9:c1:69:40;CMTS-MAC=18:8b:9d:d4:08:ec;CM-QOS=1.0;CM-VER=3.0;
2020-05-27, 16:55:18 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=08:36:c9:c1:69:40;CMTS-MAC=18:8b:9d:d4:08:ec;CM-QOS=1.0;CM-VER=3.0;
2020-05-27, 16:55:15 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=08:36:c9:c1:69:40;CMTS-MAC=18:8b:9d:d4:08:ec;CM-QOS=1.1;CM-VER=3.0;
2020-05-27, 16:54:27 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=08:36:c9:c1:69:40;CMTS-MAC=18:8b:9d:d4:08:ec;CM-QOS=1.0;CM-VER=3.0;
2020-05-27, 16:54:19 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=08:36:c9:c1:69:40;CMTS-MAC=18:8b:9d:d4:08:ec;CM-QOS=1.0;CM-VER=3.0;
2020-05-27, 16:53:46 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=08:36:c9:c1:69:40;CMTS-MAC=18:8b:9d:d4:08:ec;CM-QOS=1.0;CM-VER=3.0;
2020-05-27, 16:52:27 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=08:36:c9:c1:69:40;CMTS-MAC=18:8b:9d:d4:08:ec;CM-QOS=1.0;CM-VER=3.0;
2020-05-27, 16:51:29 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=08:36:c9:c1:69:40;CMTS-MAC=18:8b:9d:d4:08:ec;CM-QOS=1.0;CM-VER=3.0;
2020-05-27, 16:50:09 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=08:36:c9:c1:69:40;CMTS-MAC=18:8b:9d:d4:08:ec;CM-QOS=1.0;CM-VER=3.0;
2020-05-27, 16:50:06 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=08:36:c9:c1:69:40;CMTS-MAC=18:8b:9d:d4:08:ec;CM-QOS=1.0;CM-VER=3.0;
2020-05-27, 16:49:41 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=08:36:c9:c1:69:40;CMTS-MAC=18:8b:9d:d4:08:ec;CM-QOS=1.0;CM-VER=3.0;
2020-05-27, 16:49:40 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=08:36:c9:c1:69:40;CMTS-MAC=18:8b:9d:d4:08:ec;CM-QOS=1.0;CM-VER=3.0;
2020-05-27, 16:49:35 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=08:36:c9:c1:69:40;CMTS-MAC=18:8b:9d:d4:08:ec;CM-QOS=1.0;CM-VER=3.0;
2020-05-27, 16:48:48 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=08:36:c9:c1:69:40;CMTS-MAC=18:8b:9d:d4:08:ec;CM-QOS=1.0;CM-VER=3.0;
2020-05-27, 16:48:45 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=08:36:c9:c1:69:40;CMTS-MAC=18:8b:9d:d4:08:ec;CM-QOS=1.0;CM-VER=3.0;
2020-05-27, 16:45:19 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=08:36:c9:c1:69:40;CMTS-MAC=18:8b:9d:d4:08:ec;CM-QOS=1.0;CM-VER=3.0;
2020-05-27, 16:44:21 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=08:36:c9:c1:69:40;CMTS-MAC=18:8b:9d:d4:08:ec;CM-QOS=1.0;CM-VER=3.0;
2020-05-27, 16:43:23 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=08:36:c9:c1:69:40;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2020-05-27, 16:43:21 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=08:36:c9:c1:69:40;CMTS-MAC=18:8b:9d:d4:08:ec;CM-QOS=1.0;CM-VER=3.0;
2020-05-27, 16:42:49 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=08:36:c9:c1:69:40;CMTS-MAC=18:8b:9d:d4:08:ec;CM-QOS=1.0;CM-VER=3.0;
2020-05-27, 16:41:29 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=08:36:c9:c1:69:40;CMTS-MAC=18:8b:9d:d4:08:ec;CM-QOS=1.0;CM-VER=3.0;
2020-05-27, 16:40:31 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=08:36:c9:c1:69:40;CMTS-MAC=18:8b:9d:d4:08:ec;CM-QOS=1.0;CM-VER=3.0;
Time Not Established Notice (6) Honoring MDD; IP provisioning mode = IPv6

Contributor

 • 

40 Messages

5 years ago

Hi ComcastChe,

 

thank you for working on it and for conferming Upstream issues and T3/T4 timeouts.

 

I will be working from home tomorrow all day, and I will be in front of my PC. Let's see how it goes and I will report it here. Hope we can soon find a solution.

 

Have a good evening and I will be in touch.

Thank you, ~JH 

Contributor

 • 

40 Messages

5 years ago

... and these are the results from StarTrinity Continuous Speet Test (it is an image, it would need to be approved by a moderator, I think).

 

text summary for the last 2 hours:

-1h 2m uptime (58%)

-45 m downtime (42%)

-61x downtime(s)

 

 

Untitled.png

 

Official Employee

 • 

6.9K Messages

5 years ago

I'm done testing on my end. Upon checking your node, I was able to confirm there are some Upstream issues being reported in your area, but it has not yet been confirmed an outage or known issue. Your signals are all green as well, but I do see a lot of T3/T4 timeouts. Let's see if the troubleshooting I completed will help any. 

 

Can we please monitor this over the next 24-hours and let me know if there is a change on your end? If the issues are still present as of tomorrow, I will see if I am able to get a tech out again so we can get this escalated to the maintenance team, for investigation of possible issues at the node or on your line. 

 

 

Contributor

 • 

40 Messages

5 years ago

Hi, good morning - unfortunately I keep having huge issues. I began working this morning around 7 am, connection already dropped >50 times! I need to work from home - this is like not having an internet connection: cannot make a work t-call, the longest internet is up is ~10 minutes 😞

 

Let me know, what next steps are. Thanks everyone again for help and support!

 

this is snapshot of the last 20 minutes: 3 downtimes

Untitled.png 

some more modem logs:

Time Priority Description
2020-05-28, 09:06:38 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=08:36:c9:c1:69:40;CMTS-MAC=18:8b:9d:d4:08:ec;CM-QOS=1.1;CM-VER=3.0;
2020-05-28, 08:54:22 Warning (5) Unicast DSID PSN startup error
2020-05-28, 08:54:00 Notice (6) Honoring MDD; IP provisioning mode = IPv6
2020-05-28, 08:53:47 Critical (3) No UCDs Received - Timeout;;CM-MAC=08:36:c9:c1:69:40;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2020-05-28, 08:53:37 Warning (5) Lost MDD Timeout;CM-MAC=08:36:c9:c1:69:40;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2020-05-28, 08:53:30 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=08:36:c9:c1:69:40;CMTS-MAC=18:8b:9d:d4:08:ec;CM-QOS=1.0;CM-VER=3.0;
2020-05-28, 08:53:27 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=08:36:c9:c1:69:40;CMTS-MAC=18:8b:9d:d4:08:ec;CM-QOS=1.0;CM-VER=3.0;
2020-05-28, 08:53:09 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=08:36:c9:c1:69:40;CMTS-MAC=18:8b:9d:d4:08:ec;CM-QOS=1.0;CM-VER=3.0;
2020-05-28, 08:53:02 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=08:36:c9:c1:69:40;CMTS-MAC=18:8b:9d:d4:08:ec;CM-QOS=1.0;CM-VER=3.0;
2020-05-28, 08:52:53 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=08:36:c9:c1:69:40;CMTS-MAC=18:8b:9d:d4:08:ec;CM-QOS=1.0;CM-VER=3.0;
2020-05-28, 08:52:21 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=08:36:c9:c1:69:40;CMTS-MAC=18:8b:9d:d4:08:ec;CM-QOS=1.0;CM-VER=3.0;
2020-05-28, 08:52:03 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=08:36:c9:c1:69:40;CMTS-MAC=18:8b:9d:d4:08:ec;CM-QOS=1.0;CM-VER=3.0;
2020-05-28, 08:51:56 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=08:36:c9:c1:69:40;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2020-05-28, 08:51:51 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=08:36:c9:c1:69:40;CMTS-MAC=18:8b:9d:d4:08:ec;CM-QOS=1.0;CM-VER=3.0;
2020-05-28, 08:51:29 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=08:36:c9:c1:69:40;CMTS-MAC=18:8b:9d:d4:08:ec;CM-QOS=1.0;CM-VER=3.0;
2020-05-28, 08:51:17 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=08:36:c9:c1:69:40;CMTS-MAC=18:8b:9d:d4:08:ec;CM-QOS=1.1;CM-VER=3.0;
2020-05-28, 08:50:41 Notice (6) Honoring MDD; IP provisioning mode = IPv6
2020-05-28, 08:50:33 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=08:36:c9:c1:69:40;CMTS-MAC=18:8b:9d:d4:08:ec;CM-QOS=1.0;CM-VER=3.0;
2020-05-28, 08:50:25 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=08:36:c9:c1:69:40;CMTS-MAC=18:8b:9d:d4:08:ec;CM-QOS=1.0;CM-VER=3.0;
2020-05-28, 08:50:04 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=08:36:c9:c1:69:40;CMTS-MAC=18:8b:9d:d4:08:ec;CM-QOS=1.0;CM-VER=3.0;
2020-05-28, 08:49:38 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=08:36:c9:c1:69:40;CMTS-MAC=18:8b:9d:d4:08:ec;CM-QOS=1.1;CM-VER=3.0;
2020-05-28, 08:49:26 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=08:36:c9:c1:69:40;CMTS-MAC=18:8b:9d:d4:08:ec;CM-QOS=1.1;CM-VER=3.0;
2020-05-28, 08:49:19 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=08:36:c9:c1:69:40;CMTS-MAC=18:8b:9d:d4:08:ec;CM-QOS=1.1;CM-VER=3.0;
2020-05-28, 08:49:06 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=08:36:c9:c1:69:40;CMTS-MAC=18:8b:9d:d4:08:ec;CM-QOS=1.1;CM-VER=3.0;
2020-05-28, 08:48:38 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=08:36:c9:c1:69:40;CMTS-MAC=18:8b:9d:d4:08:ec;CM-QOS=1.1;CM-VER=3.0;
2020-05-28, 08:48:36 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=08:36:c9:c1:69:40;CMTS-MAC=18:8b:9d:d4:08:ec;CM-QOS=1.1;CM-VER=3.0;
2020-05-28, 08:48:18 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=08:36:c9:c1:69:40;CMTS-MAC=18:8b:9d:d4:08:ec;CM-QOS=1.1;CM-VER=3.0;
2020-05-28, 08:48:06 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=08:36:c9:c1:69:40;CMTS-MAC=18:8b:9d:d4:08:ec;CM-QOS=1.1;CM-VER=3.0;
2020-05-28, 08:47:58 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=08:36:c9:c1:69:40;CMTS-MAC=18:8b:9d:d4:08:ec;CM-QOS=1.1;CM-VER=3.0;
2020-05-28, 08:47:46 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=08:36:c9:c1:69:40;CMTS-MAC=18:8b:9d:d4:08:ec;CM-QOS=1.1;CM-VER=3.0;
2020-05-28, 08:47:19 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=08:36:c9:c1:69:40;CMTS-MAC=18:8b:9d:d4:08:ec;CM-QOS=1.1;CM-VER=3.0;
2020-05-28, 08:46:46 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=08:36:c9:c1:69:40;CMTS-MAC=18:8b:9d:d4:08:ec;CM-QOS=1.1;CM-VER=3.0;
2020-05-28, 08:46:39 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=08:36:c9:c1:69:40;CMTS-MAC=18:8b:9d:d4:08:ec;CM-QOS=1.1;CM-VER=3.0;
2020-05-28, 08:46:26 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=08:36:c9:c1:69:40;CMTS-MAC=18:8b:9d:d4:08:ec;CM-QOS=1.1;CM-VER=3.0;
2020-05-28, 08:45:59 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=08:36:c9:c1:69:40;CMTS-MAC=18:8b:9d:d4:08:ec;CM-QOS=1.1;CM-VER=3.0;
2020-05-28, 08:45:26 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=08:36:c9:c1:69:40;CMTS-MAC=18:8b:9d:d4:08:ec;CM-QOS=1.1;CM-VER=3.0;
2020-05-28, 08:45:20 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=08:36:c9:c1:69:40;CMTS-MAC=18:8b:9d:d4:08:ec;CM-QOS=1.1;CM-VER=3.0;
2020-05-28, 08:45:06 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=08:36:c9:c1:69:40;CMTS-MAC=18:8b:9d:d4:08:ec;CM-QOS=1.1;CM-VER=3.0;
2020-05-28, 08:44:39 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=08:36:c9:c1:69:40;CMTS-MAC=18:8b:9d:d4:08:ec;CM-QOS=1.1;CM-VER=3.0;
2020-05-28, 08:44:37 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=08:36:c9:c1:69:40;CMTS-MAC=18:8b:9d:d4:08:ec;CM-QOS=1.1;CM-VER=3.0;

 

Time

Priority

Description

2020-05-28, 07:33:55

Warning (5)

Dynamic Range Window violation

2020-05-28, 07:33:54

Critical (3)

Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=08:36:c9:c1:69:40;CMTS-MAC=18:8b:9d:d4:08:ec;CM-QOS=1.1;CM-VER=3.0;

2020-05-28, 07:17:33

Notice (6)

Honoring MDD; IP provisioning mode = IPv6

2020-05-28, 07:17:27

Critical (3)

Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=08:36:c9:c1:69:40;CMTS-MAC=18:8b:9d:d4:08:ec;CM-QOS=1.0;CM-VER=3.0;

2020-05-28, 07:17:23

Critical (3)

No Ranging Response received - T3 time-out;CM-MAC=08:36:c9:c1:69:40;CMTS-MAC=18:8b:9d:d4:08:ec;CM-QOS=1.0;CM-VER=3.0;

2020-05-28, 07:17:13

Critical (3)

Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=08:36:c9:c1:69:40;CMTS-MAC=18:8b:9d:d4:08:ec;CM-QOS=1.1;CM-VER=3.0;

2020-05-28, 07:15:42

Critical (3)

Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=08:36:c9:c1:69:40;CMTS-MAC=18:8b:9d:d4:08:ec;CM-QOS=1.1;CM-VER=3.0;

2020-05-28, 07:15:15

Critical (3)

Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=08:36:c9:c1:69:40;CMTS-MAC=18:8b:9d:d4:08:ec;CM-QOS=1.1;CM-VER=3.0;

2020-05-28, 07:15:03

Critical (3)

Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=08:36:c9:c1:69:40;CMTS-MAC=18:8b:9d:d4:08:ec;CM-QOS=1.1;CM-VER=3.0;

2020-05-28, 07:14:42

Critical (3)

Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=08:36:c9:c1:69:40;CMTS-MAC=18:8b:9d:d4:08:ec;CM-QOS=1.1;CM-VER=3.0;

Contributor

 • 

40 Messages

5 years ago

Can someone from xfinity please get back to me? Thank you

Contributor

 • 

40 Messages

5 years ago

to add more info,

 

in the last 80 minutes today (5/28), I have had 8 downtimes

 

my internet was down:

- at 5:14 pm for 11m 45s

- at 5:26 pm for 20m 36s

-at 17:58 for 1m 3s

- at 18:14 for 5m37s

-at 18:24 for 4m22s

 

overall, internet is being down more than 50% of the time

forum icon

New to the Community?

Start Here