New Poster
•
2 Messages
Gigabit service drops to 5-7 Mbps daily until modem reset
I am using a purchased Arris SB8200 modem, and running speed tests from a computer hardwired into Orbi router. Every 1-2 days, my gigabit connection (which usually only runs between 500-600 Mbps anyway) will drop to 5-7 Mbps. It will stay there until I do a hard reset on my modem. I've called both Comcast and Arris about this issue, and of course each company blames the other. Who is correct?? Is this a modem issue or a connection issue? I really don't want to have to purchase another modem, they're not cheap. I've attached the router status and event log below. This is right after I did a hard reset.
Thanks!
| Procedure | Status | Comment |
| Acquire Downstream Channel | 577750000 Hz | Locked |
| Connectivity State | OK | Operational |
| Boot State | OK | Operational |
| Configuration File | OK | |
| Security | Enabled | BPI+ |
| DOCSIS Network Access Enabled | Allowed |
| Downstream Bonded Channels | |||||||
|---|---|---|---|---|---|---|---|
| Channel ID | Lock Status | Modulation | Frequency | Power | SNR/MER | Corrected | Uncorrectables |
| 13 | Locked | QAM256 | 577750000 Hz | 8.1 dBmV | 42.9 dB | 0 | 0 |
| 10 | Locked | QAM256 | 559750000 Hz | 7.8 dBmV | 42.8 dB | 0 | 0 |
| 11 | Locked | QAM256 | 565750000 Hz | 7.8 dBmV | 42.7 dB | 0 | 0 |
| 12 | Locked | QAM256 | 571750000 Hz | 7.8 dBmV | 42.5 dB | 0 | 0 |
| 14 | Locked | QAM256 | 583750000 Hz | 8.0 dBmV | 42.7 dB | 0 | 0 |
| 15 | Locked | QAM256 | 589750000 Hz | 7.9 dBmV | 42.9 dB | 0 | 0 |
| 16 | Locked | QAM256 | 595750000 Hz | 8.1 dBmV | 42.8 dB | 0 | 0 |
| 17 | Locked | QAM256 | 601750000 Hz | 8.1 dBmV | 42.7 dB | 0 | 0 |
| 18 | Locked | QAM256 | 607750000 Hz | 7.9 dBmV | 42.6 dB | 0 | 0 |
| 19 | Locked | QAM256 | 613750000 Hz | 8.0 dBmV | 42.7 dB | 0 | 0 |
| 20 | Locked | QAM256 | 619750000 Hz | 8.1 dBmV | 42.8 dB | 0 | 0 |
| 21 | Locked | QAM256 | 625750000 Hz | 7.8 dBmV | 42.7 dB | 0 | 0 |
| 22 | Locked | QAM256 | 631750000 Hz | 7.9 dBmV | 42.6 dB | 0 | 0 |
| 23 | Locked | QAM256 | 637750000 Hz | 8.0 dBmV | 42.7 dB | 0 | 0 |
| 24 | Locked | QAM256 | 643750000 Hz | 7.9 dBmV | 42.7 dB | 0 | 0 |
| 25 | Locked | Other | 780000000 Hz | 8.2 dBmV | 41.0 dB | 74447039 | 0 |
| 26 | Not Locked | QAM256 | 0 Hz | 0.0 dBmV | 42.6 dB | 0 | 0 |
| 27 | Locked | QAM256 | 649750000 Hz | 7.9 dBmV | 42.5 dB | 0 | 0 |
| 28 | Locked | QAM256 | 655750000 Hz | 7.8 dBmV | 42.5 dB | 0 | 0 |
| 29 | Locked | QAM256 | 661750000 Hz | 7.6 dBmV | 42.6 dB | 0 | 0 |
| 30 | Locked | QAM256 | 667750000 Hz | 7.6 dBmV | 41.6 dB | 0 | 0 |
| 31 | Locked | QAM256 | 673750000 Hz | 7.6 dBmV | 42.7 dB | 0 | 0 |
| 32 | Locked | QAM256 | 679750000 Hz | 7.6 dBmV | 42.6 dB | 0 | 0 |
| 33 | Locked | QAM256 | 685750000 Hz | 7.7 dBmV | 42.7 dB | 0 | 0 |
| 34 | Locked | QAM256 | 691750000 Hz | 7.8 dBmV | 42.7 dB | 0 | 0 |
| 35 | Locked | QAM256 | 697750000 Hz | 7.7 dBmV | 42.7 dB | 0 | 0 |
| 36 | Locked | QAM256 | 703750000 Hz | 7.7 dBmV | 42.7 dB | 0 | 0 |
| 37 | Locked | QAM256 | 709750000 Hz | 7.7 dBmV | 42.7 dB | 0 | 0 |
| 38 | Locked | QAM256 | 715750000 Hz | 7.8 dBmV | 42.7 dB | 0 | 0 |
| 39 | Locked | QAM256 | 721750000 Hz | 7.8 dBmV | 42.4 dB | 0 | 0 |
| 40 | Locked | QAM256 | 727750000 Hz | 7.6 dBmV | 42.6 dB | 0 | 0 |
| 41 | Locked | QAM256 | 733750000 Hz | 7.9 dBmV | 42.7 dB | 0 | 0 |
| Upstream Bonded Channels | ||||||
|---|---|---|---|---|---|---|
| Channel | Channel ID | Lock Status | US Channel Type | Frequency | Width | Power |
| 1 | 4 | Locked | SC-QAM Upstream | 36500000 Hz | 6400000 Hz | 42.0 dBmV |
| 2 | 1 | Locked | SC-QAM Upstream | 17300000 Hz | 6400000 Hz | 42.0 dBmV |
| 3 | 2 | Locked | SC-QAM Upstream | 23700000 Hz | 6400000 Hz | 42.0 dBmV |
| 4 | 3 | Locked | SC-QAM Upstream | 30100000 Hz | 6400000 Hz | 42.0 dBmV |
| Date Time | Event ID | Event Level | Description |
|---|---|---|---|
| 06/25/2020 08:46 | 67061600 | 6 | "DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=2c:95:69:fb:ca:59;CMTS-MAC=00:01:5c:6a:78:62;CM-QOS=1.1;CM-VER=3.1;" |
| 01/01/1970 00:00 | 2436694066 | 6 | "Honoring MDD; IP provisioning mode = IPv6" |
| 01/01/1970 00:00 | 82000200 | 3 | "No Ranging Response received - T3 time-out;CM-MAC=2c:95:69:fb:ca:59;CMTS-MAC=00:01:5c:6a:78:62;CM-QOS=1.1;CM-VER=3.1;" |
| 01/01/1970 00:00 | 84000100 | 3 | "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=2c:95:69:fb:ca:59;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;" |
| 01/01/1970 00:00 | 82000200 | 3 | "No Ranging Response received - T3 time-out;CM-MAC=2c:95:69:fb:ca:59;CMTS-MAC=00:01:5c:6a:78:62;CM-QOS=1.1;CM-VER=3.1;" |
| 01/01/1970 00:00 | 84000100 | 3 | "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=2c:95:69:fb:ca:59;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;" |
| 06/21/2020 07:19 | 82000500 | 3 | "Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=2c:95:69:fb:ca:59;CMTS-MAC=00:01:5c:6a:78:62;CM-QOS=1.1;CM-VER=3.1;" |
| 01/01/1970 00:00 | 82000200 | 3 | "No Ranging Response received - T3 time-out;CM-MAC=2c:95:69:fb:ca:59;CMTS-MAC=00:01:5c:6a:78:62;CM-QOS=1.1;CM-VER=3.1;" |
| 01/01/1970 00:00 | 84000100 | 3 | "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=2c:95:69:fb:ca:59;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;" |
| 01/01/1970 00:00 | 82000200 | 3 | "No Ranging Response received - T3 time-out;CM-MAC=2c:95:69:fb:ca:59;CMTS-MAC=00:01:5c:6a:78:62;CM-QOS=1.1;CM-VER=3.1;" |
| 01/01/1970 00:00 | 84000100 | 3 | "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=2c:95:69:fb:ca:59;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;" |
| 01/01/1970 00:00 | 82000200 | 3 | "No Ranging Response received - T3 time-out;CM-MAC=2c:95:69:fb:ca:59;CMTS-MAC=00:01:5c:6a:78:62;CM-QOS=1.1;CM-VER=3.1;" |
| 01/01/1970 00:00 | 84000100 | 3 | "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=2c:95:69:fb:ca:59;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;" |
| 01/01/1970 00:00 | 82000200 | 3 | "No Ranging Response received - T3 time-out;CM-MAC=2c:95:69:fb:ca:59;CMTS-MAC=00:01:5c:6a:78:62;CM-QOS=1.1;CM-VER=3.1;" |
| 01/01/1970 00:00 | 84000100 | 3 | "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=2c:95:69:fb:ca:59;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;" |
| 01/01/1970 00:00 | 82000200 | 3 | "No Ranging Response received - T3 time-out;CM-MAC=2c:95:69:fb:ca:59;CMTS-MAC=00:01:5c:6a:78:62;CM-QOS=1.1;CM-VER=3.1;" |
| 01/01/1970 00:00 | 84000100 | 3 | "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=2c:95:69:fb:ca:59;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;" |
| 01/01/1970 00:00 | 82000200 | 3 | "No Ranging Response received - T3 time-out;CM-MAC=2c:95:69:fb:ca:59;CMTS-MAC=00:01:5c:6a:78:62;CM-QOS=1.1;CM-VER=3.1;" |
| 01/01/1970 00:00 | 84000100 | 3 | "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=2c:95:69:fb:ca:59;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;" |
| 01/01/1970 00:00 | 82000200 | 3 | "No Ranging Response received - T3 time-out;CM-MAC=2c:95:69:fb:ca:59;CMTS-MAC=00:01:5c:6a:78:62;CM-QOS=1.1;CM-VER=3.1;" |
| 01/01/1970 00:00 | 84000100 | 3 | "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=2c:95:69:fb:ca:59;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;" |
| 01/01/1970 00:00 | 82000200 | 3 | "No Ranging Response received - T3 time-out;CM-MAC=2c:95:69:fb:ca:59;CMTS-MAC=00:01:5c:6a:78:62;CM-QOS=1.1;CM-VER=3.1;" |
| 01/01/1970 00:00 | 84000100 | 3 | "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=2c:95:69:fb:ca:59;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;" |
| 01/01/1970 00:00 | 82000200 | 3 | "No Ranging Response received - T3 time-out;CM-MAC=2c:95:69:fb:ca:59;CMTS-MAC=00:01:5c:6a:78:62;CM-QOS=1.1;CM-VER=3.1;" |
| 01/01/1970 00:00 | 84000100 | 3 | "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=2c:95:69:fb:ca:59;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;" |
| 01/01/1970 00:00 | 82000200 | 3 | "No Ranging Response received - T3 time-out;CM-MAC=2c:95:69:fb:ca:59;CMTS-MAC=00:01:5c:6a:78:62;CM-QOS=1.1;CM-VER=3.1;" |
| 01/01/1970 00:00 | 84000100 | 3 | "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=2c:95:69:fb:ca:59;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;" |
| 01/01/1970 00:00 | 82000200 | 3 | "No Ranging Response received - T3 time-out;CM-MAC=2c:95:69:fb:ca:59;CMTS-MAC=00:01:5c:6a:78:62;CM-QOS=1.1;CM-VER=3.1;" |
| 01/01/1970 00:00 | 84000100 | 3 | "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=2c:95:69:fb:ca:59;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;" |
| 05/21/2020 05:54 | 2436694044 | 3 | "Resetting the cable modem due to docsDevResetNow" |
| 05/19/2020 12:34 | 82000500 | 3 | "Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=2c:95:69:fb:ca:59;CMTS-MAC=00:01:5c:6a:78:62;CM-QOS=1.1;CM-VER=3.1;" |
| 01/01/1970 00:00 | 82000200 | 3 | "No Ranging Response received - T3 time-out;CM-MAC=2c:95:69:fb:ca:59;CMTS-MAC=00:01:5c:6a:78:62;CM-QOS=1.1;CM-VER=3.1;" |
| 01/01/1970 00:00 | 84000100 | 3 | "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=2c:95:69:fb:ca:59;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;" |
| 01/01/1970 00:00 | 82000200 | 3 | "No Ranging Response received - T3 time-out;CM-MAC=2c:95:69:fb:ca:59;CMTS-MAC=00:01:5c:6a:78:62;CM-QOS=1.1;CM-VER=3.1;" |
| 01/01/1970 00:00 | 84000100 | 3 | "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=2c:95:69:fb:ca:59;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;" |
| 01/01/1970 00:00 | 82000200 | 3 | "No Ranging Response received - T3 time-out;CM-MAC=2c:95:69:fb:ca:59;CMTS-MAC=00:01:5c:6a:78:62;CM-QOS=1.1;CM-VER=3.1;" |
| 01/01/1970 00:00 | 84000100 | 3 | "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=2c:95:69:fb:ca:59;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;" |
| 01/01/1970 00:00 | 82000200 | 3 | "No Ranging Response received - T3 time-out;CM-MAC=2c:95:69:fb:ca:59;CMTS-MAC=00:01:5c:6a:78:62;CM-QOS=1.1;CM-VER=3.1;" |
| 01/01/1970 00:00 | 84000100 | 3 | "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=2c:95:69:fb:ca:59;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;" |
| 01/01/1970 00:00 | 82000200 | 3 | "No Ranging Response received - T3 time-out;CM-MAC=2c:95:69:fb:ca:59;CMTS-MAC=00:01:5c:6a:78:62;CM-QOS=1.1;CM-VER=3.1;" |
| 01/01/1970 00:00 | 84000100 | 3 | "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=2c:95:69:fb:ca:59;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;" |
| 01/01/1970 00:00 | 82000200 | 3 | "No Ranging Response received - T3 time-out;CM-MAC=2c:95:69:fb:ca:59;CMTS-MAC=00:01:5c:6a:78:62;CM-QOS=1.1;CM-VER=3.1;" |
| 01/01/1970 00:00 | 84000100 | 3 | "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=2c:95:69:fb:ca:59;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;" |
| 01/01/1970 00:00 | 82000200 | 3 | "No Ranging Response received - T3 time-out;CM-MAC=2c:95:69:fb:ca:59;CMTS-MAC=00:01:5c:6a:78:62;CM-QOS=1.1;CM-VER=3.1;" |
| 01/01/1970 00:00 | 84000100 | 3 | "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=2c:95:69:fb:ca:59;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;" |
| 05/01/2020 10:21 | 82000200 | 3 | "No Ranging Response received - T3 time-out;CM-MAC=2c:95:69:fb:ca:59;CMTS-MAC=00:01:5c:6a:78:62;CM-QOS=1.1;CM-VER=3.1;" |
| 05/01/2020 10:21 | 84000500 | 3 | "SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=2c:95:69:fb:ca:59;CMTS-MAC=00:01:5c:6a:78:62;CM-QOS=1.1;CM-VER=3.1;" |
| 05/01/2020 10:21 | 84000100 | 3 | "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=2c:95:69:fb:ca:59;CMTS-MAC=00:01:5c:6a:78:62;CM-QOS=1.1;CM-VER=3.1;" |
| 05/01/2020 10:20 | 84000100 | 3 | "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=2c:95:69:fb:ca:59;CMTS-MAC=00:01:5c:6a:78:62;CM-QOS=1.1;CM-VER=3.1;" |
| 05/01/2020 10:20 | 84000100 | 3 | "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=2c:95:69:fb:ca:59;CMTS-MAC=00:01:5c:6a:78:62;CM-QOS=1.1;CM-VER=3.1;" |
matt4952
Contributor
•
27 Messages
4 years ago
The Rf signal looks good so unless there is fluctuation in the RF or an Upstream SNR issue in your area. With the limited info I would have to lean towards it is an issue with your equipment.
-Are you hardwired into the Orbi that is hardwired into the modem? Or are you hardwired into a wireless Orbi unit?
-Your getting 500-600 Mbps hardwired into the Orbi but what do you get if your hardwired directly into the modem?
-When the speeds drop did someone in the house start doing something? (smart TV, play music on a Sono’s like system, online gaming, someone just got home)
Without know everything I would probably try-
-Replace the Ethernet cords (especially the ones that came with the Orbi’s)
- Make sure all coax connectors are tight (on the modem, wall plate, any cable splitters in the house)
-If possible hard wire directly into the modem tomorrow morning and see if the same issue happens at al tomorrow. (Would help to see if the issue is with the Orbi’s or the modem. If you still get the same issue when your directly plugged into the modem, then it could be a modem or a Comcast issue, but it would help to narrow down what could be causing the issues.) The speeds your seeing when your not having the issue seems like the Orbi’s are limiting your speeds, should be getting 940 to 970 Mbps download hardwired.
0
0
ArmyDogDoc
New Poster
•
2 Messages
4 years ago
Thank you for the reply. The PC is hardwired into the Orbi, and the Orbi is hardwired into the Arris.
I just changed my connection to plug the PC directly into the Arris using CAT 6 cable. On the xfinity speedtest, I'm getting 760Mbps. Typically the speed drops to 5-7 Mbps aren't tied to any specific event. I'll notice them usually in the evenings when I settle down for a video call, online gaming, or browsing on my phone. Not consistent to a single device or activity. I'll just notice the connection is sluggish, do a speed test, and it comes up 5-7 Mbps. At that point I go reset my modem and things go back to normal for a day or two.
Also, I just noticed that after this most recent modem reboot, one of the downstream channels is showing significant errors, and the upstream power has now jumped about 10 dBmV.
Current System Time: Thu Jun 25 10:24:11 2020
0
0
EG
Expert
•
103.5K Messages
4 years ago
The RF signals do not "look good" as others have suggested. The SNR's on some of the downstream channels are too low;
Looks like there is extraneous noise ingressing into the line somewhere at those frequencies.
Also, the upstream power is too high / out of spec. That can cause random disconnects, spontaneous re-booting of the modem, speed, packet loss, and latency problems.
In a self troubleshooting effort to try to obtain better connectivity / more wiggle room, check to see if there are there any excess/unneeded coax cable splitters in the line leading to the modem that can be eliminated/re-configured. Any splitters that remain should be high quality and cable rated for 5-1002 MHz, bi-directional, and no gold colored garbage types like GE, RadioShack, RCA, Philips, Leviton, Magnavox, and Rocketfish from big box stores like Home Depot, Lowes, Target, Wal-Mart etc. Splitters should be swapped with known to be good / new ones to test
If there aren't any unneeded splitters that can be eliminated and if your coax wiring setup can't be reconfigured so that there is a single two way splitter connected directly off of the drop from the street/pole with one port feeding the modem and the other port feeding the rest of the house/equipment with additional splits as needed, and you've checked all the wiring and fittings for integrity and tightness and refresh them by taking them apart then check for and clean off any corrosion / oxidation on the center wire and put them back together again, then perhaps it's best to book a tech visit to investigate and correct.
0
0