T9

Visitor

 • 

3 Messages

Tue, Jun 14, 2022 8:00 PM

Closed

Randomly loosing connection

Ever since the four days of internet issues last week, I’ve randomly been loosing my internet connection and have to restart my SB200 & not my eero mesh.  I googled some of the errors in the modem logs and some say it’s splitter related, but I don’t have a tv connection just modem internet only cable coming inside.  I am loosing connection at random times every 2-3 days.  Here are some of the errors I found since this afternoons most recent modem reboot.  Any help is much appreciated.  I thought about calling support, but figured they would just push their own rented modem gateway on me as this is my own equipment even though it’s been happening right after daily system issues last week.  It leads me to think they are still having smaller issues even though it’s not reported on the site. 

Event ID Event Level Description
06/14/2022 14:48 82000500 3 "Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;"
06/14/2022 14:42 67061600 6 "DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;"
06/14/2022 14:44 2436694066 6 "Honoring MDD; IP provisioning mode = IPv6"
06/14/2022 14:44 82000200 3 "No Ranging Response received - T3 time-out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;"
06/14/2022 14:44 84000100 3 "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;"
06/14/2022 14:43 82000400 3 "Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;"
06/14/2022 14:43 84000100 3 "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;"
06/14/2022 14:42 82000400 3 "Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;"
06/14/2022 14:42 84000100 3 "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;"
06/14/2022 14:42 82000400 3 "Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;"
06/14/2022 14:42 84000100 3 "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;"
06/14/2022 14:41 82000400 3 "Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;"
06/14/2022 14:41 84000100 3 "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;"
06/14/2022 14:41 82000400 3 "Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;"
06/14/2022 14:41 84000100 3 "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;"
06/14/2022 14:39 84020300 5 "MDD message timeout;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;"
06/14/2022 14:39 84000100 3 "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;"
06/14/2022 14:39 84020300 5 "MDD message timeout;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;"
06/14/2022 14:39 84000100 3 "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;"
06/14/2022 14:39 82000500 3 "Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-



Visitor

 • 

3 Messages

19 d ago

Channel ID Lock Status Modulation Frequency Power SNR/MER Corrected Uncorrectables
25 Locked QAM256 651000000 Hz 0.0 dBmV 42.8 dB 379 1572
6 Locked QAM256 531000000 Hz -0.6 dBmV 37.0 dB 460 1534
7 Locked QAM256 537000000 Hz -0.7 dBmV 41.5 dB 555 2427
8 Locked QAM256 543000000 Hz -0.7 dBmV 40.4 dB 596 2525
9 Locked QAM256 555000000 Hz -0.2 dBmV 41.5 dB 597 2338
10 Locked QAM256 561000000 Hz -0.2 dBmV 42.0 dB 29695 10006
11 Locked QAM256 567000000 Hz -0.2 dBmV 35.6 dB 1197 2408
12 Locked QAM256 573000000 Hz -0.5 dBmV 35.0 dB 589 2512
13 Locked QAM256 579000000 Hz -0.2 dBmV 39.2 dB 526 2353
14 Locked QAM256 585000000 Hz 0.2 dBmV 42.6 dB 696 2393
15 Locked QAM256 591000000 Hz 0.1 dBmV 42.9 dB 538 1928
16 Locked QAM256 597000000 Hz 0.3 dBmV 35.2 dB 89707 18608
17 Locked QAM256 603000000 Hz 0.4 dBmV 43.1 dB 7484 9274
18 Locked QAM256 609000000 Hz 0.2 dBmV 43.2 dB 500 2402
19 Locked QAM256 615000000 Hz 0.1 dBmV 43.1 dB 537 2277
20 Locked QAM256 621000000 Hz 0.3 dBmV 42.7 dB 620 2498
21 Locked QAM256 627000000 Hz -0.1 dBmV 42.6 dB 552 2340
22 Locked QAM256 633000000 Hz 0.2 dBmV 42.8 dB 535 2326
23 Locked QAM256 639000000 Hz 0.1 dBmV 42.9 dB 528 2332
24 Locked QAM256 645000000 Hz 0.0 dBmV 40.9 dB 576 2453
26 Locked QAM256 657000000 Hz 0.0 dBmV 42.8 dB 504 2378
27 Locked QAM256 663000000 Hz 0.1 dBmV 42.9 dB 553 2374
28 Locked QAM256 669000000 Hz 0.3 dBmV 43.0 dB 546 2430
29 Locked QAM256 675000000 Hz 0.5 dBmV 42.3 dB 555 2546
30 Locked QAM256 681000000 Hz 0.2 dBmV 43.0 dB 551 2559
31 Locked QAM256 687000000 Hz 0.4 dBmV 43.1 dB 615 2502
32 Locked QAM256 693000000 Hz 0.6 dBmV 42.8 dB 594 2471
33 Locked QAM256 699000000 Hz 0.6 dBmV 43.3 dB 648 2473
34 Locked QAM256 705000000 Hz 0.4 dBmV 43.1 dB 745 2647
35 Locked QAM256 711000000 Hz 0.6 dBmV 43.2 dB 478 2082
36 Locked QAM256 717000000 Hz 0.5 dBmV 43.2 dB 554 2544
41 Locked Other 762000000 Hz 0.0 dBmV 41.2 dB 3839596441 1480


Upstream Bonded Channels
Channel Channel ID Lock Status US Channel Type Frequency Width Power
1 1 Locked SC-QAM Upstream 35600000 Hz 6400000 Hz 46.0 dBmV
2 2 Locked SC-QAM Upstream 29200000 Hz 6400000 Hz 45.0 dBmV
3 3 Locked SC-QAM Upstream 22800000 Hz 6400000 Hz 45.0 dBmV
4 4 Locked SC-QAM Upstream 16400000 Hz 6400000 Hz 46.0 dBmV
5 9 Locked SC-QAM Upstream 39600000 Hz 1600000 Hz 44.0 dBmV

Official Employee

 • 

177 Messages

@trekker182-954 Thank you for reaching out on the Xfinity Community Forums. I am happy to assist you. Are you still seeing an issue with the connection dropping? What troubleshooting steps have you completed as we would not want to have you repeat them. We look forward to assisting 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

 • 

3 Messages

@XfinityJanelle​ Thanks for reaching out!  A tech had to patch my cable at the pole & upgrade the grounding inside the box after that my modem hasn’t yet lost sync with the signal thanks! 

(edited)

XfinityGina

Official Employee

 • 

560 Messages

@Trekker182-954 that's excellent news! We appreciate the update :) We have really amazing techs, I'm so glad they were able to get things all patched up and working as it should be again! 

 

Thank you so much for being a contributing part of our Forum community!

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
forum icon

New to the Community?

Start Here