Community Forum

1Gb Service - Seems to be "capped"? (Ongoing issues from a repair at the node 2/months ago)

New Poster

1Gb Service - Seems to be "capped"? (Ongoing issues from a repair at the node 2/months ago)

So I'll give a run down of how this all happened as quick as possible.
Key take away here is 2 months ago BEFORE the following my gig service worked EXCELLENT.
Equipment used in 1-6.

SB8200 Arris
All new COAX lines, connectors etc.
Multiple CAT6 cables used.
Router: ASUS RT-AC5300
*I've tried hardwiring from the modem, and from the router with BOTH modems the same issue occurs, the router is not the issue.

Lines 7 on
Netgear CM1000 was installed.


--- HOW IT HAPPENED ---
1. Gig service was working fine (2ish months ago). 
2. Called xFinity to report issue, tech was sent out. (Major uncorrectables / correrctables)

3. Tech notified me that the node connecting to our house was hit by lightning and a supervisor would be making the repair.
4. Supervisor made repair, notified me that a line had to be repaired as well and that it would take time because of permitting issues.
5. Line was repaired.

--- CURRENTLY ---
1. Speeds have still been no where near one gig, 250-350MBps MAX, Upload 40MBps.
2. Called xFinity for a tech to come to my home.
3. Tech noticed no issues in my home but noise in the line at the box notified me his supervisor would contact me and work on the issue.
4. Tech Supervisor visits my home, finds the issues, and corrects them.
5. I can confirm directly connected into the modem STILL 250-350MBps MAX, Upload 40MBps.
6. Tech Supervisor advises me it MAY be the modem, I agree, I order a Netgear CM1000 and have it put in the same night.
7. CM1000 connected, registered.... SAME speeds.
CM1000 Status:

Frequency start Value
This field below allows you to modify the frequency the cable modem start with its scan during initialization and registration. Enter the new start frequency and restart the cable modem for it to take effect.
Starting Frequency

Startup Procedure
Procedure Status Comment
Acquire Downstream Channel 453000000 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 / MER Unerrored Codewords Correctable Codewords Uncorrectable Codewords
1 Locked QAM256 34 453000000 Hz 4.8 dBmV 42.0 dB 2044066634 23 0
2 Locked QAM256 1 477000000 Hz 5.1 dBmV 41.9 dB 2043054747 16 0
3 Locked QAM256 2 483000000 Hz 5.0 dBmV 42.0 dB 2043059177 17 0
4 Locked QAM256 3 489000000 Hz 5.0 dBmV 41.9 dB 2043056335 21 0
5 Locked QAM256 4 495000000 Hz 4.9 dBmV 41.8 dB 2043061441 14 0
6 Locked QAM256 5 507000000 Hz 5.1 dBmV 41.7 dB 2043064714 9 0
7 Locked QAM256 6 513000000 Hz 5.2 dBmV 41.7 dB 2043069204 11 0
8 Locked QAM256 7 519000000 Hz 6.2 dBmV 42.0 dB 2043072507 11 0
9 Locked QAM256 8 525000000 Hz 5.2 dBmV 41.8 dB 2043078944 6 0
10 Locked QAM256 9 531000000 Hz 5.2 dBmV 41.9 dB 2043081922 3 0
11 Locked QAM256 10 537000000 Hz 4.8 dBmV 41.8 dB 2043086566 10 0
12 Locked QAM256 11 543000000 Hz 4.9 dBmV 41.9 dB 2043089995 4 0
13 Locked QAM256 12 549000000 Hz 4.5 dBmV 41.9 dB 2043093845 7 0
14 Locked QAM256 13 555000000 Hz 4.4 dBmV 41.8 dB 2043096406 7 0
15 Locked QAM256 14 561000000 Hz 4.5 dBmV 41.7 dB 2043102394 3 0
16 Locked QAM256 15 567000000 Hz 4.3 dBmV 41.6 dB 2043105374 9 0
17 Locked QAM256 16 573000000 Hz 4.6 dBmV 41.9 dB 2043109366 11 0
18 Locked QAM256 17 579000000 Hz 4.6 dBmV 41.9 dB 2043112954 8 0
19 Locked QAM256 18 585000000 Hz 4.7 dBmV 42.0 dB 2043116907 7 0
20 Locked QAM256 19 591000000 Hz 4.8 dBmV 41.9 dB 2043120591 18 0
21 Locked QAM256 20 597000000 Hz 4.8 dBmV 42.1 dB 2043123986 4 0
22 Locked QAM256 21 603000000 Hz 5.0 dBmV 42.2 dB 2043127879 7 0
23 Locked QAM256 22 609000000 Hz 5.0 dBmV 42.2 dB 2043131746 16 0
24 Locked QAM256 23 615000000 Hz 5.0 dBmV 42.1 dB 2043135756 19 0
25 Locked QAM256 24 621000000 Hz 5.0 dBmV 42.3 dB 2043139165 50 0
26 Locked QAM256 25 627000000 Hz 5.0 dBmV 42.2 dB 2043142570 39 25
27 Locked QAM256 26 633000000 Hz 4.9 dBmV 42.1 dB 2043109155 42 49
28 Locked QAM256 27 639000000 Hz 5.0 dBmV 42.3 dB 2043145857 40 54
29 Locked QAM256 35 459000000 Hz 4.6 dBmV 41.8 dB 2043150849 20 0
30 Locked QAM256 36 465000000 Hz 5.0 dBmV 42.0 dB 2043119839 27 0
31 Locked QAM256 37 471000000 Hz 4.9 dBmV 41.9 dB 2043122297 26 0
32 Not Locked Unknown 0 0 Hz 0.0 dBmV 0.0 dB 0 0 0

Upstream Bonded Channels
Channel Lock Status Modulation Channel ID Frequency Power
1 Locked ATDMA 57 35800000 Hz 48.3 dBmV
2 Locked ATDMA 58 29400000 Hz 46.8 dBmV
3 Locked ATDMA 59 23000000 Hz 46.3 dBmV
4 Not Locked Unknown 0 0 Hz 0.0 dBmV
5 Not Locked Unknown 0 0 Hz 0.0 dBmV
6 Not Locked Unknown 0 0 Hz 0.0 dBmV
7 Not Locked Unknown 0 0 Hz 0.0 dBmV
8 Not Locked Unknown 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 33 690000000 Hz 5.1 dBmV 40.5 dB 1228 ~ 2867 24565695 3990027 7
2 Not Locked 0 0 0 Hz 2.9 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 Unknown 0 0 Hz 0 dBmV
2 Not Locked Unknown 0 0 Hz 0 dBmV

Current System Time: Wed Jul 31 09:32:08 2019 
System Up Time: 12:29:56

CM1000 Event Log:

Time Priority Description
2019-07-30, 21:02:49 Notice (6) DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1.;CM-MAC=14:59:c0:f6:d9:88;CMTS-MAC=00:01:5c:82:fe:54;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=14:59:c0:f6:d9:88;CMTS-MAC=00:01:5c:82:fe:54;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=14:59:c0:f6:d9:88;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
Time Not Established Critical (3) No Ranging Response received - T3 time-out;CM-MAC=14:59:c0:f6:d9:88;CMTS-MAC=00:01:5c:82:fe:54;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=14:59:c0:f6:d9:88;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
Time Not Established Critical (3) No Ranging Response received - T3 time-out;CM-MAC=14:59:c0:f6:d9:88;CMTS-MAC=00:01:5c:82:fe:54;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=14:59:c0:f6:d9:88;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
2019-07-30, 20:49:29 Critical (3) Resetting the cable modem due to docsDevResetNow
Time Not Established Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=14:59:c0:f6:d9:88;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
2019-07-30, 20:31:48 Critical (3) SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=14:59:c0:f6:d9:88;CMTS-MAC=00:01:5c:82:fe:54;CM-QOS=1.1;CM-VER=3.1;
Time Not Established Critical (3) No Ranging Response received - T3 time-out;CM-MAC=14:59:c0:f6:d9:88;CMTS-MAC=00:01:5c:82:fe:54;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=14:59:c0:f6:d9:88;CMTS-MAC=00:00:00:00:00:00;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=14:59:c0:f6:d9:88;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;


Now I'm not as savvy with the netgear modem but when I had the SB8200 Arris in I can confirm that it had NO power level issues, or uncorrectables / correctables.

Can ANYONE please help me figure out what's going on here? I love my xFinity service honestly I really did when I was getting my correct speeds, I had no complaints. I understand issues happen and that things have to be repaired I've never made it a HUGE concern. Now months have passed and what seems to be from a customers view an easy fix somewhere, just isn't getting fixed... at no fault of the tech support, or technicians or supervisors that have visited my residence it seems that we are just simply missing something somewhere.

Speedtest Results 7/31/2019 10:00 AM (ish)
Xfinity Speedtest

Speedtest.xyz Results 7/31/2019 10:40 AM (ish)
Speedtest.net Results 7/31/2019 10:40 AM (ish) -- Bonita Springs, FL server I'm in Central Florida
 

 

Please someone guide me to the light on how to fix thisSmiley Sad