I am in the 600MBps band and used to clock around 700Mbps at all times.
Once the recent work from home in MI started, the speed slows down to 6Mbps or even slower. I have to restart the modem to get back to decent speed. I have to do this multiple times a day.
Noting much has changed in terms of modem/router, #connected devices. Same number of devices as during the weekend when we all connect our laptops & phones.
Why is this happening & what is the remedy?
What do the modem's signal stats look like ? Try getting them here http://192.168.100.1 or here http://10.0.0.1
Please post the *Downstream Power Level*, the *Upstream Power Level*, and the *SNR* (Signal to Noise Ratio) numbers.
What is the exact make and model number of the modem ?
Is this a WiFi connection ?
It is a LAN via ethernet. It is connected to the back of a Netgear Orbi router.
Channel ID | Lock Status | Modulation | Frequency | Power | SNR/MER | Corrected | Uncorrectables |
9 | Locked | QAM256 | 531000000 Hz | 4.8 dBmV | 40.6 dB | 0 | 0 |
2 | Locked | QAM256 | 489000000 Hz | 5.2 dBmV | 40.8 dB | 0 | 0 |
3 | Locked | QAM256 | 495000000 Hz | 5.4 dBmV | 41.0 dB | 0 | 0 |
4 | Locked | QAM256 | 501000000 Hz | 6.1 dBmV | 41.1 dB | 0 | 0 |
5 | Locked | QAM256 | 507000000 Hz | 5.8 dBmV | 41.2 dB | 0 | 0 |
6 | Locked | QAM256 | 513000000 Hz | 6.0 dBmV | 41.1 dB | 0 | 0 |
7 | Locked | QAM256 | 519000000 Hz | 5.9 dBmV | 41.0 dB | 0 | 0 |
8 | Locked | QAM256 | 525000000 Hz | 5.2 dBmV | 40.9 dB | 0 | 0 |
10 | Locked | QAM256 | 537000000 Hz | 3.9 dBmV | 40.4 dB | 0 | 0 |
11 | Locked | QAM256 | 543000000 Hz | 5.2 dBmV | 40.9 dB | 0 | 0 |
12 | Locked | QAM256 | 549000000 Hz | 5.6 dBmV | 40.6 dB | 0 | 0 |
13 | Locked | QAM256 | 555000000 Hz | 5.6 dBmV | 40.8 dB | 0 | 0 |
14 | Locked | QAM256 | 561000000 Hz | 5.8 dBmV | 40.9 dB | 0 | 0 |
15 | Locked | QAM256 | 567000000 Hz | 6.3 dBmV | 41.0 dB | 0 | 0 |
16 | Locked | QAM256 | 573000000 Hz | 6.7 dBmV | 41.1 dB | 0 | 0 |
17 | Locked | QAM256 | 579000000 Hz | 6.8 dBmV | 41.2 dB | 0 | 0 |
18 | Locked | QAM256 | 585000000 Hz | 6.1 dBmV | 40.8 dB | 0 | 0 |
19 | Locked | QAM256 | 591000000 Hz | 5.9 dBmV | 40.7 dB | 0 | 0 |
20 | Locked | QAM256 | 597000000 Hz | 5.9 dBmV | 40.7 dB | 0 | 0 |
21 | Locked | QAM256 | 603000000 Hz | 6.2 dBmV | 40.6 dB | 0 | 0 |
22 | Locked | QAM256 | 609000000 Hz | 6.1 dBmV | 40.7 dB | 0 | 0 |
23 | Locked | QAM256 | 615000000 Hz | 6.4 dBmV | 40.6 dB | 0 | 0 |
24 | Locked | QAM256 | 621000000 Hz | 7.0 dBmV | 40.8 dB | 0 | 0 |
25 | Locked | QAM256 | 627000000 Hz | 6.9 dBmV | 40.8 dB | 0 | 0 |
26 | Locked | QAM256 | 633000000 Hz | 7.1 dBmV | 40.8 dB | 0 | 0 |
27 | Locked | QAM256 | 639000000 Hz | 7.1 dBmV | 40.9 dB | 0 | 0 |
28 | Locked | QAM256 | 645000000 Hz | 7.6 dBmV | 41.1 dB | 0 | 0 |
29 | Locked | QAM256 | 651000000 Hz | 7.5 dBmV | 41.0 dB | 0 | 0 |
30 | Locked | QAM256 | 657000000 Hz | 7.8 dBmV | 41.1 dB | 0 | 0 |
31 | Locked | QAM256 | 663000000 Hz | 7.8 dBmV | 41.1 dB | 0 | 0 |
33 | Locked | QAM256 | 669000000 Hz | 7.8 dBmV | 41.1 dB | 0 | 0 |
37 | Locked | Other | 690000000 Hz | 7.3 dBmV | 39.2 dB | 26523347 | 0 |
Upstream Bonded Channels | ||||||
---|---|---|---|---|---|---|
Channel | Channel ID | Lock Status | US Channel Type | Frequency | Width | Power |
1 | 5 | Locked | SC-QAM Upstream | 39800000 Hz | 1600000 Hz | 42.0 dBmV |
2 | 4 | Locked | SC-QAM Upstream | 16600000 Hz | 6400000 Hz | 43.0 dBmV |
3 | 3 | Locked | SC-QAM Upstream | 23000000 Hz | 6400000 Hz | 42.0 dBmV |
4 | 2 | Locked | SC-QAM Upstream | 29400000 Hz | 6400000 Hz | 42.0 dBmV |
5 | 1 | Locked | SC-QAM Upstream | 35800000 Hz | 6400000 Hz | 42.0 dBmV |
Current System Time: Mon Apr 20 11:02:26 2020
The signal stats were o/k at that snapshot in time. Are there any RF error / event log entries being shown ? If so, please post them too.
Noticing a lot of time sync issues!
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 !
Hi @Shankarhokie,
We appreciate you for posting to the Xfinity Forums! Sorry for the connectivity issues you're having. I agree with @EG. Let's chat in a private message so I can gather your account information and begin to check for issues at the node. Please send me a private message with your full name, the name of the account holder, and the house number of your address, so I can assist you. To send a private message, click on "ComcastChe" and then click send a message.
I've had the same issue and have a similar post. However, it still has not been resolved even after 2 modems and a new line put in. I am not sure what the issue is, but I haven't called back because I haven't had the time to spend with them. It takes literal hours to accomplish anything and still have nothing resolved.
Communicating with ComcastChe.
Any idea why my modem would have a 1970 time stamp? Seems like a lot of folks with intermittent connection issues have the same T3 error with 01/01/1970 timestamp.
Directly connected to modem. Here are the power and SNR
Downstream Bonded Channels | |||||||
---|---|---|---|---|---|---|---|
Channel ID | Lock Status | Modulation | Frequency | Power | SNR/MER | Corrected | Uncorrectables |
9 | Locked | QAM256 | 531000000 Hz | 7.0 dBmV | 41.0 dB | 235 | 94 |
2 | Locked | QAM256 | 489000000 Hz | 6.9 dBmV | 41.1 dB | 220 | 71 |
3 | Locked | QAM256 | 495000000 Hz | 6.9 dBmV | 41.1 dB | 189 | 68 |
4 | Locked | QAM256 | 501000000 Hz | 7.6 dBmV | 41.3 dB | 207 | 66 |
5 | Locked | QAM256 | 507000000 Hz | 7.4 dBmV | 41.2 dB | 246 | 56 |
6 | Locked | QAM256 | 513000000 Hz | 7.5 dBmV | 41.1 dB | 259 | 96 |
7 | Locked | QAM256 | 519000000 Hz | 7.6 dBmV | 41.0 dB | 311 | 96 |
8 | Locked | QAM256 | 525000000 Hz | 7.1 dBmV | 40.9 dB | 269 | 73 |
10 | Locked | QAM256 | 537000000 Hz | 6.3 dBmV | 40.7 dB | 242 | 76 |
11 | Locked | QAM256 | 543000000 Hz | 7.2 dBmV | 40.7 dB | 201 | 51 |
12 | Locked | QAM256 | 549000000 Hz | 7.1 dBmV | 41.0 dB | 167 | 85 |
13 | Locked | QAM256 | 555000000 Hz | 7.1 dBmV | 41.0 dB | 181 | 51 |
14 | Locked | QAM256 | 561000000 Hz | 7.5 dBmV | 40.9 dB | 161 | 56 |
15 | Locked | QAM256 | 567000000 Hz | 7.5 dBmV | 40.9 dB | 152 | 63 |
16 | Locked | QAM256 | 573000000 Hz | 7.5 dBmV | 40.9 dB | 232 | 221 |
17 | Locked | QAM256 | 579000000 Hz | 7.9 dBmV | 38.8 dB | 166 | 77 |
18 | Locked | QAM256 | 585000000 Hz | 8.2 dBmV | 41.0 dB | 183 | 56 |
19 | Locked | QAM256 | 591000000 Hz | 8.1 dBmV | 40.8 dB | 186 | 56 |
20 | Locked | QAM256 | 597000000 Hz | 7.7 dBmV | 40.7 dB | 205 | 48 |
21 | Locked | QAM256 | 603000000 Hz | 8.0 dBmV | 40.8 dB | 163 | 52 |
22 | Locked | QAM256 | 609000000 Hz | 7.9 dBmV | 40.7 dB | 207 | 46 |
23 | Locked | QAM256 | 615000000 Hz | 8.1 dBmV | 39.4 dB | 142 | 51 |
24 | Locked | QAM256 | 621000000 Hz | 8.6 dBmV | 40.8 dB | 158 | 29 |
25 | Locked | QAM256 | 627000000 Hz | 8.5 dBmV | 40.8 dB | 154 | 19 |
26 | Locked | QAM256 | 633000000 Hz | 8.7 dBmV | 40.7 dB | 146 | 33 |
27 | Locked | QAM256 | 639000000 Hz | 8.8 dBmV | 40.9 dB | 165 | 34 |
28 | Locked | QAM256 | 645000000 Hz | 9.2 dBmV | 41.1 dB | 167 | 28 |
29 | Locked | QAM256 | 651000000 Hz | 9.1 dBmV | 40.9 dB | 142 | 55 |
30 | Locked | QAM256 | 657000000 Hz | 9.4 dBmV | 41.0 dB | 154 | 57 |
31 | Locked | QAM256 | 663000000 Hz | 9.4 dBmV | 41.0 dB | 184 | 44 |
33 | Locked | QAM256 | 669000000 Hz | 9.4 dBmV | 41.1 dB | 151 | 61 |
37 | Locked | Other | 690000000 Hz | 9.3 dBmV | 39.2 dB | 214138946 | 45 |
Upstream
Upstream Bonded Channels | ||||||
---|---|---|---|---|---|---|
Channel | Channel ID | Lock Status | US Channel Type | Frequency | Width | Power |
1 | 5 | Locked | SC-QAM Upstream | 39800000 Hz | 1600000 Hz | 41.0 dBmV |
2 | 4 | Locked | SC-QAM Upstream | 16600000 Hz | 6400000 Hz | 42.0 dBmV |
3 | 3 | Locked | SC-QAM Upstream | 23000000 Hz | 6400000 Hz | 42.0 dBmV |
4 | 2 | Locked | SC-QAM Upstream | 29400000 Hz | 6400000 Hz | 41.0 dBmV |
5 | 1 | Locked | SC-QAM Upstream | 35800000 Hz | 6400000 Hz | 41.0 dBmV |
Current System Time: Tue Apr 21 08:58:00 2020
Today, I'm seeing a lot of T6 issues related to hannel 37. @EG had mentioned somewhere that this "Other" channel is related to Gigabit speed tier. I am not on that plan. So far today, the speed has been stable.
I have also been going back to check any recent software updates/upgrades. Recently, Malwarebytes did a big update and I wondered if that was conflicting with the modem/router firewalls and also possibly Norton Security. It also added a Malwarebytes ad blocker for the chrome browser. I have disabled Malwarebytes for now. Let me see if things stablize.
@Shankarhokie wrote:Communicating with ComcastChe.
Any idea why my modem would have a 1970 time stamp? Seems like a lot of folks with intermittent connection issues have the same T3 error with 01/01/1970 timestamp.
That's what a modem defaults to using when for whatever reason, when it is having difficulties talking to the T.O.D. (Time Of Day) server.
Update:
Hello @ComcastChe @EG : After several hours of steady internet speeds, the problem returned with the same error (going to 01/01/1970). This morning I reset the SB8200 and so far so good. I am awaiting the deep dive results from @ComcastChe
Hi @Shankarhokie!
Sorry for the delay. Yes, I do have an update for you. Based on what I see, I've been communicating with your local techs to get this escalated since I cannot schedule a normal tech visit. I've just received the ok today, so I will be replying to your private message shortly. I have a few more things I need to verify before I can get this up to them. Chat with you soon.
April 24th update.
Tech showed up promptly at 10 am. He maintained social distance and asked what issue I was having. I explained my having to restart the modem daily.
Tech mentioned that this is a bandwidth issue with everyone being online at the same time. He said that Comcast designs the network nodes and infrastructure for 50% average utilization and now it is more than 90% putting a strain on the bandwidth.
He said that there were several techs working in our neighborhood checking the cables because of complaints.
He cautioned me NOT to restart the modem during the latter part of the day since the modem may not be able to connect back.
He checked everything outside and did not find an issue. The signal strength, quality, channel powers were all within bounds.
He said that Comcast in investigating adding some more nodes in the area to reduce the number of homes using a single node.
I guess I will have to wait for Michigan to fully open up and all of us to start going back to work before this problem stops.
Until then, I'm going to do a restart early in the morning and hope for the best!
I will keep updating my daily findings.
Thanks for the update @Shankarhokie!
Although he wasn't able to do anything to completely resolve the issue, it's a good thing that he was able to isolate any issues at your home or with your equipment and confirm that your local techs are aware and investigating. Please keep us updated. If things get too bad for you reach out in our private message and I'll see what I can do.
@ComcastChe @EG Please Help!
We are having the exact same issue and nobody is helping. After half a dozen chat sessions with support all they can do is tell us to reset the modem. Today, they flat out disconnected the chat when we asked for escalation. On the phone we were also promised someone was coming to check outside the house but never showed up.
Why keep paying for 900Mbps service when our average daily speeds are around 20 Mbps? Please have someone come check the service. We have top of the line equipement all with recomended settings and regular tests showing poor sertive across WiFi and Ethernet on multiple devices and times of day. Our device setup inside the house has not changed. This is almost unusable with so many reboots required. What is going on here?
Router: Netgear RAX200 AX12
Modem: Negear Genie CM1150V (V2.02.04 Firmware)
Downstream Bonded Channels | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Upstream Bonded Channels | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Downstream OFDM Channels | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Upstream OFDMA Channels | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Time | Priority | Description |
Wed Jul 01 13:53:41 2020 | Notice (6) | DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=28:80:88:d3:3f:e8;CMTS-MAC=00:01:5c:a8:ca:60;CM-QOS=1.1;CM-VER=3.1; |
Wed Jul 01 13:53:36 2020 | Notice (6) | TLV-11 - unrecognized OID;CM-MAC=28:80:88:d3:3f:e8;CMTS-MAC=00:01:5c:a8:ca:60;CM-QOS=1.1;CM-VER=3.1; |
Time Not Established | Notice (6) | Honoring MDD; IP provisioning mode = IPv6 |
Time Not Established | Critical (3) | No Ranging Response received - T3 time-out;CM-MAC=28:80:88:d3:3f:e8;CMTS-MAC=00:01:5c:a8:ca:60;CM-QOS=1.1;CM-VER=3.1; |
Time Not Established | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=28:80:88:d3:3f:e8;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1; |
Wed Jul 01 06:24:41 2020 | Notice (6) | DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=28:80:88:d3:3f:e8;CMTS-MAC=00:01:5c:a8:ca:60;CM-QOS=1.1;CM-VER=3.1; |
Wed Jul 01 06:24:36 2020 | Notice (6) | TLV-11 - unrecognized OID;CM-MAC=28:80:88:d3:3f:e8;CMTS-MAC=00:01:5c:a8:ca:60;CM-QOS=1.1;CM-VER=3.1; |
Time Not Established | Notice (6) | Honoring MDD; IP provisioning mode = IPv6 |
Time Not Established | Critical (3) | No Ranging Response received - T3 time-out;CM-MAC=28:80:88:d3:3f:e8;CMTS-MAC=00:01:5c:a8:ca:60;CM-QOS=1.1;CM-VER=3.1; |
Time Not Established | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=28:80:88:d3:3f:e8;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1; |
Tue Jun 30 23:05:07 2020 | Notice (6) | CM-STATUS message sent. Event Type Code: 24; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1 2 3.;CM-MAC=28:80:88:d3:3f:e8;CMTS-MAC=00:01:5c:a8:ca:60;CM-QOS=1.1;CM-VER=3.1; |
Tue Jun 30 23:05:03 2020 | Notice (6) | CM-STATUS message sent. Event Type Code: 22; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=28:80:88:d3:3f:e8;CMTS-MAC=00:01:5c:a8:ca:60;CM-QOS=1.1;CM-VER=3.1; |
Tue Jun 30 23:05:02 2020 | Notice (6) | CM-STATUS message sent. Event Type Code: 23; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=28:80:88:d3:3f:e8;CMTS-MAC=00:01:5c:a8:ca:60;CM-QOS=1.1;CM-VER=3.1; |
Tue Jun 30 22:39:07 2020 | Notice (6) | CM-STATUS message sent. Event Type Code: 24; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=28:80:88:d3:3f:e8;CMTS-MAC=00:01:5c:a8:ca:60;CM-QOS=1.1;CM-VER=3.1; |
Tue Jun 30 22:38:38 2020 | Notice (6) | CM-STATUS message sent. Event Type Code: 16; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=28:80:88:d3:3f:e8;CMTS-MAC=00:01:5c:a8:ca:60;CM-QOS=1.1;CM-VER=3.1; |
Tue Jun 30 06:11:17 2020 | Notice (6) | DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=28:80:88:d3:3f:e8;CMTS-MAC=00:01:5c:a8:ca:60;CM-QOS=1.1;CM-VER=3.1; |
Tue Jun 30 06:11:12 2020 | Notice (6) | TLV-11 - unrecognized OID;CM-MAC=28:80:88:d3:3f:e8;CMTS-MAC=00:01:5c:a8:ca:60;CM-QOS=1.1;CM-VER=3.1; |
Time Not Established | Notice (6) | Honoring MDD; IP provisioning mode = IPv6 |
Time Not Established | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=28:80:88:d3:3f:e8;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1; |
Mon Jun 29 08:25:18 2020 | Notice (6) | CM-STATUS message sent. Event Type Code: 24; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=28:80:88:d3:3f:e8;CMTS-MAC=00:01:5c:a8:ca:60;CM-QOS=1.1;CM-VER=3.1; |
Mon Jun 29 08:24:52 2020 | Notice (6) | CM-STATUS message sent. Event Type Code: 16; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=28:80:88:d3:3f:e8;CMTS-MAC=00:01:5c:a8:ca:60;CM-QOS=1.1;CM-VER=3.1; |
Mon Jun 29 08:00:50 2020 | Notice (6) | DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=28:80:88:d3:3f:e8;CMTS-MAC=00:01:5c:a8:ca:60;CM-QOS=1.1;CM-VER=3.1; |
Mon Jun 29 08:00:45 2020 | Notice (6) | TLV-11 - unrecognized OID;CM-MAC=28:80:88:d3:3f:e8;CMTS-MAC=00:01:5c:a8:ca:60;CM-QOS=1.1;CM-VER=3.1; |
Time Not Established | Notice (6) | Honoring MDD; IP provisioning mode = IPv6 |
Time Not Established | Critical (3) | No Ranging Response received - T3 time-out;CM-MAC=28:80:88:d3:3f:e8;CMTS-MAC=00:01:5c:a8:ca:60;CM-QOS=1.1;CM-VER=3.1; |
Time Not Established | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=28:80:88:d3:3f:e8;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1; |
Mon Jun 29 06:39:12 2020 | Notice (6) | DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=28:80:88:d3:3f:e8;CMTS-MAC=00:01:5c:a8:ca:60;CM-QOS=1.1;CM-VER=3.1; |
Mon Jun 29 06:39:07 2020 | Notice (6) | TLV-11 - unrecognized OID;CM-MAC=28:80:88:d3:3f:e8;CMTS-MAC=00:01:5c:a8:ca:60;CM-QOS=1.1;CM-VER=3.1; |
Time Not Established | Notice (6) | Honoring MDD; IP provisioning mode = IPv6 |
Time Not Established | Critical (3) | No Ranging Response received - T3 time-out;CM-MAC=28:80:88:d3:3f:e8;CMTS-MAC=00:01:5c:a8:ca:60;CM-QOS=1.1;CM-VER=3.1; |
Time Not Established | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=28:80:88:d3:3f:e8;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1; |
Mon Jun 29 06:25:57 2020 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=28:80:88:d3:3f:e8;CMTS-MAC=00:01:5c:a8:ca:60;CM-QOS=1.1;CM-VER=3.1; |
Sun Jun 28 23:35:39 2020 | Notice (6) | DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=28:80:88:d3:3f:e8;CMTS-MAC=00:01:5c:a8:ca:60;CM-QOS=1.1;CM-VER=3.1; |
Sun Jun 28 23:35:34 2020 | Notice (6) | TLV-11 - unrecognized OID;CM-MAC=28:80:88:d3:3f:e8;CMTS-MAC=00:01:5c:a8:ca:60;CM-QOS=1.1;CM-VER=3.1; |
Time Not Established | Notice (6) | Honoring MDD; IP provisioning mode = IPv6 |
Time Not Established | Critical (3) | No Ranging Response received - T3 time-out;CM-MAC=28:80:88:d3:3f:e8;CMTS-MAC=00:01:5c:a8:ca:60;CM-QOS=1.1;CM-VER=3.1; |
Time Not Established | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=28:80:88:d3:3f:e8;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1; |
Sun Jun 28 23:27:58 2020 | Notice (6) | DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=28:80:88:d3:3f:e8;CMTS-MAC=00:01:5c:a8:ca:60;CM-QOS=1.1;CM-VER=3.1; |
Sun Jun 28 23:27:52 2020 | Notice (6) | TLV-11 - unrecognized OID;CM-MAC=28:80:88:d3:3f:e8;CMTS-MAC=00:01:5c:a8:ca:60;CM-QOS=1.1;CM-VER=3.1; |
Time Not Established | Notice (6) | Honoring MDD; IP provisioning mode = IPv6 |
Time | Text | EndpointName |
2020-07-01 13:54:00 | DHCP ERROR:OFFER;REQUESTING;Option 122.3 contains invalid FQDN | 0.0.0.0 |
Hi - I have been having this SAME ISSUE for WEEKS! We have to manually restart one to five times/day. Please help! @ComcastChe
@ComcastChe : The problem returned the next day and I have to do the restart daily.
I have the exact same problem in Santa Cruz, CA. A few months ago upgraded to Arris SB8200, we the 600 Mbps service plan (upgraded from 300 Mbps). Unfortuantely, a service tech that came a few weeks ago informed me that 400 Mbps (300 realized) is the most we can expect in our area until they install fiberoptic. The 'upgrade' only cost a few tens of dollars more per more so I'm loath to downgrade, hoping for the best bandwidth possible despite the local infrastructure limitation.
Typically I see a max of ~180 Mbps download speeds on my mid-2011 MacBook Air, up to 300 Mbps on my two year old iphone 10 and up to ~280 Mbps on my 2019 MacBook Pro laptop. Starting a few weeks ago, I find I have to reset my modem EVERY MORNING or sometimes more often, otherwise speeds go down to 2-5 Mbps. As others on this thread have noted this is VERY frustrating and has me wondering why I don't just switch to AT&T. If Xfinity doesn't get it together soon, I probably will switch. We have 4-5 people in our household attempting to work and attend school remotely. These resets seriously compromise our ability to make a living and educate our children. Considering the amount of money we (the greater community) are collectively paying Xfinity, they need to fix this ASAP.