Forum Discussion

naraisan's avatar
naraisan
New Contributor

Frequently dropping internet - SYNC Timing Synchronization failure, RCS Partial Service, No Ranging Response received | Internet Problems

For the past 2 weeks the internet in my household has been frequently cutting out. 
Sometimes it will disconnect every hour or two, other times it will disconnect multiple times in the span of 30 minutes.
Even when I hardwire my ethernet cable to the modem the issues persist as usual.
The technician on the phone said that everything seems to be normal from their side, and the technician that came out to check out the problem also said that he didn't see any issues.
I have been using the service with minimal issues for about 6 months, but the past 2 weeks have been awful. Even though I disconnect 20+ times a day, the internet speeds seem to be normal (I have frequently run speedtests) while the internet is functioning.

Through troubleshooting, calls with technicians, and a visit with the technician, it is guaranteed that the problem is limited to:
1. Modem
2. Wiring
3. Cox

I went to 192.168.100.1 to get more information about the modem (Arris SB6190) and saw this:

TimePriorityDescription
Fri Jan 12 02:16:03 2018 3 No Ranging Response received - T3 time-out;CM-MAC=5c:e3:0e:3b:71:e1;CMTS-MAC=00:59:dc:79:8d:cb;CM-QOS=1.1;CM-VER=3.0;
Fri Jan 12 02:54:13 2018 3 SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=5c:e3:0e:3b:71:e1;CMTS-MAC=00:59:dc:79:8d:cb;CM-QOS=1.1;CM-VER=3.0;
Fri Jan 12 03:40:14 2018 5 RCS Partial Service;CM-MAC=5c:e3:0e:3b:71:e1;CMTS-MAC=00:59:dc:79:8d:cb;CM-QOS=1.1;CM-VER=3.0;
Fri Jan 12 04:06:33 2018 3 No Ranging Response received - T3 time-out;CM-MAC=5c:e3:0e:3b:71:e1;CMTS-MAC=00:59:dc:79:8d:cb;CM-QOS=1.1;CM-VER=3.0;
Fri Jan 12 05:09:15 2018 3 SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=5c:e3:0e:3b:71:e1;CMTS-MAC=00:59:dc:79:8d:cb;CM-QOS=1.1;CM-VER=3.0;
Fri Jan 12 06:54:54 2018 5 RCS Partial Service;CM-MAC=5c:e3:0e:3b:71:e1;CMTS-MAC=00:59:dc:79:8d:cb;CM-QOS=1.1;CM-VER=3.0;
Fri Jan 12 07:09:13 2018 3 SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=5c:e3:0e:3b:71:e1;CMTS-MAC=00:59:dc:79:8d:cb;CM-QOS=1.1;CM-VER=3.0;
Fri Jan 12 07:28:35 2018 5 RCS Partial Service;CM-MAC=5c:e3:0e:3b:71:e1;CMTS-MAC=00:59:dc:79:8d:cb;CM-QOS=1.1;CM-VER=3.0;
Fri Jan 12 07:54:15 2018 3 SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=5c:e3:0e:3b:71:e1;CMTS-MAC=00:59:dc:79:8d:cb;CM-QOS=1.1;CM-VER=3.0;
Fri Jan 12 09:35:20 2018 5 RCS Partial Service;CM-MAC=5c:e3:0e:3b:71:e1;CMTS-MAC=00:59:dc:79:8d:cb;CM-QOS=1.1;CM-VER=3.0;
Fri Jan 12 09:39:12 2018 3 SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=5c:e3:0e:3b:71:e1;CMTS-MAC=00:59:dc:79:8d:cb;CM-QOS=1.1;CM-VER=3.0;
Fri Jan 12 11:22:43 2018 5 RCS Partial Service;CM-MAC=5c:e3:0e:3b:71:e1;CMTS-MAC=00:59:dc:79:8d:cb;CM-QOS=1.1;CM-VER=3.0;
Fri Jan 12 11:22:43 2018 3 SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=5c:e3:0e:3b:71:e1;CMTS-MAC=00:59:dc:79:8d:cb;CM-QOS=1.1;CM-VER=3.0;
Fri Jan 12 11:22:44 2018 5 RCS Partial Service;CM-MAC=5c:e3:0e:3b:71:e1;CMTS-MAC=00:59:dc:79:8d:cb;CM-QOS=1.1;CM-VER=3.0;
Fri Jan 12 11:24:13 2018 3 SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=5c:e3:0e:3b:71:e1;CMTS-MAC=00:59:dc:79:8d:cb;CM-QOS=1.1;CM-VER=3.0;
Fri Jan 12 11:43:40 2018 5 RCS Partial Service;CM-MAC=5c:e3:0e:3b:71:e1;CMTS-MAC=00:59:dc:79:8d:cb;CM-QOS=1.1;CM-VER=3.0;
Fri Jan 12 12:09:11 2018 3 SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=5c:e3:0e:3b:71:e1;CMTS-MAC=00:59:dc:79:8d:cb;CM-QOS=1.1;CM-VER=3.0;
Fri Jan 12 14:10:16 2018 5 RCS Partial Service;CM-MAC=5c:e3:0e:3b:71:e1;CMTS-MAC=00:59:dc:79:8d:cb;CM-QOS=1.1;CM-VER=3.0;
Fri Jan 12 14:24:18 2018 3 SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=5c:e3:0e:3b:71:e1;CMTS-MAC=00:59:dc:79:8d:cb;CM-QOS=1.1;CM-VER=3.0;
Fri Jan 12 15:14:59 2018 5 RCS Partial Service;CM-MAC=5c:e3:0e:3b:71:e1;CMTS-MAC=00:59:dc:79:8d:cb;CM-QOS=1.1;CM-VER=3.0;

I would really like some help as to how to fix the problem, I require a stable internet connection for work and I have resorted to using a hotspot from my phone just to have consistent internet!

12 Replies

Sort By
Most LikedOldestNewest
  • DustinP's avatar
    DustinP
    Moderator
    Hello naraisan,

    Is the issue intermittent and not happening during the time we have a technician reserved? Do you experience the issue when you bypass the router and have a computer wired directly to the Modem?



  • Ultimate_Speed_'s avatar
    Ultimate_Speed_
    New Contributor

    RCS Partial Service;CM-MAC=5c:e3:0e:3b:71:e1;CMTS-MAC=00:59:dc:79:8d:cb;CM-QOS=1.1;CM-VER=3.0; 

    = Modem is not provisioned correctly

    SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=5c:e3:0e:3b:71:e1;CMTS-MAC=00:59:dc:79:8d:cb;CM-QOS=1.1;CM-VER=3.0;

    = Noise on the line usually caused by a loose connection on coaxial cable - this could be at a neighbors house on the same ped drop as you and not at your house.

    No Ranging Response received - T3 time-out;CM-MAC=5c:e3:0e:3b:71:e1;CMTS-MAC=00:59:dc:79:8d:cb;CM-QOS=1.1;CM-VER=3.0;

    = Modem is not provisioned correctly 

    Is the issue intermittent and not happening during the time we have a technician reserved?

    = We boosted you signal and service for several days so when the tech comes out he/she finds nothing wrong with our end. We can then say its your equipment or connections at fault. After several days it will drop back off to the old junk service (because our equipment is mostly 10+ years old and very expensive to replace). So it is cheaper for us to say its your equipment having the issue and not our super structure network that is a lot older than your equipment.

  • Ultimate_Speed_'s avatar
    Ultimate_Speed_
    New Contributor

    BTW.. I have more systems and networking certifications than any of the employees at COX Oklahoma City. I could remote into  your modem un-cap it run some test then recap it. (oops just did) your modem is not at fault.

    You could reach speeds in excess of 600MBs - ultimate service is capped at 300Mbs. 1MBs is 8x more than 1Mbs so 300Mbs = 37.5MBs.

    Uncapped your modem hit 642MBs or 5136Mbs.

    Mbs = Megabits per second / MBs MegaBytes per second.

    Good luck with tech support.

  • Allan's avatar
    Allan
    Moderator

    @KrawdaddyinBR,

    We can look into any speed issues yo may be experiencing. What speeds are you currently getting? Also, is this issue happening with all devices in the home or just one? 

    Thanks,

    Allan - Cox Support Forums Moderator.

  • Ultimate_Speed_'s avatar
    Ultimate_Speed_
    New Contributor
    13 minutes of Event Log

    The table below contains the log of events that the SB6183 has detected. This log can be important to the service provider to help diagnose and correct problems, if any should occur.

    TimePriorityDescription
    Sun Jan 14 19:17:57 2018 Warning (5) MDD message timeout;CM-MAC=20:3d:66:9e:6a:ab;CMTS-MAC=00:42:5a:9e:75:d2;CM-QOS=1.1;CM-VER=3.0;
    Sun Jan 14 19:17:53 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=20:3d:66:9e:6a:ab;CMTS-MAC=00:42:5a:9e:75:d2;CM-QOS=1.1;CM-VER=3.0;
    Sun Jan 14 19:17:34 2018 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=20:3d:66:9e:6a:ab;CMTS-MAC=00:42:5a:9e:75:d2;CM-QOS=1.1;CM-VER=3.0;
    Sun Jan 14 19:17:31 2018 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=20:3d:66:9e:6a:ab;CMTS-MAC=00:42:5a:9e:75:d2;CM-QOS=1.1;CM-VER=3.0;
    Sun Jan 14 19:17:29 2018 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=20:3d:66:9e:6a:ab;CMTS-MAC=00:42:5a:9e:75:d2;CM-QOS=1.1;CM-VER=3.0;
    Sun Jan 14 19:17:25 2018 Warning (5) MDD message timeout;CM-MAC=20:3d:66:9e:6a:ab;CMTS-MAC=00:42:5a:9e:75:d2;CM-QOS=1.1;CM-VER=3.0;
    Sun Jan 14 19:15:19 2018 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=20:3d:66:9e:6a:ab;CMTS-MAC=00:42:5a:9e:75:d2;CM-QOS=1.1;CM-VER=3.0;
    Sun Jan 14 19:15:15 2018 Warning (5) MDD message timeout;CM-MAC=20:3d:66:9e:6a:ab;CMTS-MAC=00:42:5a:9e:75:d2;CM-QOS=1.1;CM-VER=3.0;
    Sun Jan 14 19:15:15 2018 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=20:3d:66:9e:6a:ab;CMTS-MAC=00:42:5a:9e:75:d2;CM-QOS=1.1;CM-VER=3.0;
    Sun Jan 14 19:15:14 2018 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=20:3d:66:9e:6a:ab;CMTS-MAC=00:42:5a:9e:75:d2;CM-QOS=1.1;CM-VER=3.0;
    Sun Jan 14 19:14:46 2018 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=20:3d:66:9e:6a:ab;CMTS-MAC=00:42:5a:9e:75:d2;CM-QOS=1.1;CM-VER=3.0;
    Sun Jan 14 19:14:41 2018 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=20:3d:66:9e:6a:ab;CMTS-MAC=00:42:5a:9e:75:d2;CM-QOS=1.1;CM-VER=3.0;
    Sun Jan 14 19:14:36 2018 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=20:3d:66:9e:6a:ab;CMTS-MAC=00:42:5a:9e:75:d2;CM-QOS=1.1;CM-VER=3.0;
    Sun Jan 14 19:14:34 2018 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=20:3d:66:9e:6a:ab;CMTS-MAC=00:42:5a:9e:75:d2;CM-QOS=1.1;CM-VER=3.0;
    Sun Jan 14 19:14:33 2018 Warning (5) MDD message timeout;CM-MAC=20:3d:66:9e:6a:ab;CMTS-MAC=00:42:5a:9e:75:d2;CM-QOS=1.1;CM-VER=3.0;
    Sun Jan 14 19:14:33 2018 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=20:3d:66:9e:6a:ab;CMTS-MAC=00:42:5a:9e:75:d2;CM-QOS=1.1;CM-VER=3.0;
    Sun Jan 14 19:14:32 2018 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=20:3d:66:9e:6a:ab;CMTS-MAC=00:42:5a:9e:75:d2;CM-QOS=1.1;CM-VER=3.0;
    Sun Jan 14 19:14:10 2018 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=20:3d:66:9e:6a:ab;CMTS-MAC=00:42:5a:9e:75:d2;CM-QOS=1.1;CM-VER=3.0;
    Sun Jan 14 19:13:59 2018 Warning (5) MDD message timeout;CM-MAC=20:3d:66:9e:6a:ab;CMTS-MAC=00:42:5a:9e:75:d2;CM-QOS=1.1;CM-VER=3.0;
    Sun Jan 14 19:13:59 2018 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=20:3d:66:9e:6a:ab;CMTS-MAC=00:42:5a:9e:75:d2;CM-QOS=1.1;CM-VER=3.0;
    Sun Jan 14 19:13:58 2018 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=20:3d:66:9e:6a:ab;CMTS-MAC=00:42:5a:9e:75:d2;CM-QOS=1.1;CM-VER=3.0;
    Sun Jan 14 19:13:56 2018 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=20:3d:66:9e:6a:ab;CMTS-MAC=00:42:5a:9e:75:d2;CM-QOS=1.1;CM-VER=3.0;
    Sun Jan 14 19:13:17 2018 Warning (5) MDD message timeout;CM-MAC=20:3d:66:9e:6a:ab;CMTS-MAC=00:42:5a:9e:75:d2;CM-QOS=1.1;CM-VER=3.0;
    Sun Jan 14 19:13:16 2018 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=20:3d:66:9e:6a:ab;CMTS-MAC=00:42:5a:9e:75:d2;CM-QOS=1.1;CM-VER=3.0;
    Sun Jan 14 19:13:12 2018 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=20:3d:66:9e:6a:ab;CMTS-MAC=00:42:5a:9e:75:d2;CM-QOS=1.1;CM-VER=3.0;
    Sun Jan 14 19:12:45 2018 Warning (5) MDD message timeout;CM-MAC=20:3d:66:9e:6a:ab;CMTS-MAC=00:42:5a:9e:75:d2;CM-QOS=1.1;CM-VER=3.0;
    Sun Jan 14 19:12:42 2018 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=20:3d:66:9e:6a:ab;CMTS-MAC=00:42:5a:9e:75:d2;CM-QOS=1.1;CM-VER=3.0;
    Sun Jan 14 19:12:41 2018 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=20:3d:66:9e:6a:ab;CMTS-MAC=00:42:5a:9e:75:d2;CM-QOS=1.1;CM-VER=3.0;
    Sun Jan 14 19:11:29 2018 Warning (5) MDD message timeout;CM-MAC=20:3d:66:9e:6a:ab;CMTS-MAC=00:42:5a:9e:75:d2;CM-QOS=1.1;CM-VER=3.0;
    Sun Jan 14 19:10:58 2018 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=20:3d:66:9e:6a:ab;CMTS-MAC=00:42:5a:9e:75:d2;CM-QOS=1.1;CM-VER=3.0;
    Sun Jan 14 19:10:55 2018 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=20:3d:66:9e:6a:ab;CMTS-MAC=00:42:5a:9e:75:d2;CM-QOS=1.1;CM-VER=3.0;
    Sun Jan 14 19:10:52 2018 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=20:3d:66:9e:6a:ab;CMTS-MAC=00:42:5a:9e:75:d2;CM-QOS=1.1;CM-VER=3.0;
    Sun Jan 14 19:10:48 2018 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=20:3d:66:9e:6a:ab;CMTS-MAC=00:42:5a:9e:75:d2;CM-QOS=1.1;CM-VER=3.0;
    Sun Jan 14 19:10:47 2018 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=20:3d:66:9e:6a:ab;CMTS-MAC=00:42:5a:9e:75:d2;CM-QOS=1.1;CM-VER=3.0;
    Sun Jan 14 19:10:43 2018 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=20:3d:66:9e:6a:ab;CMTS-MAC=00:42:5a:9e:75:d2;CM-QOS=1.1;CM-VER=3.0;
    Sun Jan 14 19:10:41 2018 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=20:3d:66:9e:6a:ab;CMTS-MAC=00:42:5a:9e:75:d2;CM-QOS=1.1;CM-VER=3.0;
    Sun Jan 14 19:10:40 2018 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=20:3d:66:9e:6a:ab;CMTS-MAC=00:42:5a:9e:75:d2;CM-QOS=1.1;CM-VER=3.0;
    Sun Jan 14 19:10:39 2018 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=20:3d:66:9e:6a:ab;CMTS-MAC=00:42:5a:9e:75:d2;CM-QOS=1.1;CM-VER=3.0;
    Sun Jan 14 19:10:37 2018 Warning (5) MDD message timeout;CM-MAC=20:3d:66:9e:6a:ab;CMTS-MAC=00:42:5a:9e:75:d2;CM-QOS=1.1;CM-VER=3.0;
    Sun Jan 14 19:10:37 2018 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=20:3d:66:9e:6a:ab;CMTS-MAC=00:42:5a:9e:75:d2;CM-QOS=1.1;CM-VER=3.0;
    Sun Jan 14 19:10:35 2018 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=20:3d:66:9e:6a:ab;CMTS-MAC=00:42:5a:9e:75:d2;CM-QOS=1.1;CM-VER=3.0;
    Sun Jan 14 19:10:33 2018 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=20:3d:66:9e:6a:ab;CMTS-MAC=00:42:5a:9e:75:d2;CM-QOS=1.1;CM-VER=3.0;
    Sun Jan 14 19:10:32 2018 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=20:3d:66:9e:6a:ab;CMTS-MAC=00:42:5a:9e:75:d2;CM-QOS=1.1;CM-VER=3.0;
    Sun Jan 14 19:10:21 2018 Warning (5) MDD message timeout;CM-MAC=20:3d:66:9e:6a:ab;CMTS-MAC=00:42:5a:9e:75:d2;CM-QOS=1.1;CM-VER=3.0;
    Sun Jan 14 19:10:21 2018 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=20:3d:66:9e:6a:ab;CMTS-MAC=00:42:5a:9e:75:d2;CM-QOS=1.1;CM-VER=3.0;
    Sun Jan 14 19:10:20 2018 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=20:3d:66:9e:6a:ab;CMTS-MAC=00:42:5a:9e:75:d2;CM-QOS=1.1;CM-VER=3.0;
    Sun Jan 14 19:10:09 2018 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=20:3d:66:9e:6a:ab;CMTS-MAC=00:42:5a:9e:75:d2;CM-QOS=1.1;CM-VER=3.0;
    Sun Jan 14 19:10:08 2018 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=20:3d:66:9e:6a:ab;CMTS-MAC=00:42:5a:9e:75:d2;CM-QOS=1.1;CM-VER=3.0;
    Sun Jan 14 19:10:07 2018 Warning (5) MDD message timeout;CM-MAC=20:3d:66:9e:6a:ab;CMTS-MAC=00:42:5a:9e:75:d2;CM-QOS=1.1;CM-VER=3.0;
    Sun Jan 14 19:10:06 2018 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=20:3d:66:9e:6a:ab;CMTS-MAC=00:42:5a:9e:75:d2;CM-QOS=1.1;CM-VER=3.0;
    Sun Jan 14 19:10:05 2018 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=20:3d:66:9e:6a:ab;CMTS-MAC=00:42:5a:9e:75:d2;CM-QOS=1.1;CM-VER=3.0;
    Sun Jan 14 19:10:02 2018 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=20:3d:66:9e:6a:ab;CMTS-MAC=00:42:5a:9e:75:d2;CM-QOS=1.1;CM-VER=3.0;
    Sun Jan 14 19:09:54 2018 Warning (5) MDD message timeout;CM-MAC=20:3d:66:9e:6a:ab;CMTS-MAC=00:42:5a:9e:75:d2;CM-QOS=1.1;CM-VER=3.0;
    Sun Jan 14 19:09:51 2018 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=20:3d:66:9e:6a:ab;CMTS-MAC=00:42:5a:9e:75:d2;CM-QOS=1.1;CM-VER=3.0;
    Sun Jan 14 19:09:48 2018 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=20:3d:66:9e:6a:ab;CMTS-MAC=00:42:5a:9e:75:d2;CM-QOS=1.1;CM-VER=3.0;
    Sun Jan 14 19:09:39 2018 Warning (5) MDD message timeout;CM-MAC=20:3d:66:9e:6a:ab;CMTS-MAC=00:42:5a:9e:75:d2;CM-QOS=1.1;CM-VER=3.0;
    Sun Jan 14 19:09:38 2018 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=20:3d:66:9e:6a:ab;CMTS-MAC=00:42:5a:9e:75:d2;CM-QOS=1.1;CM-VER=3.0;
    Sun Jan 14 19:09:10 2018 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=20:3d:66:9e:6a:ab;CMTS-MAC=00:42:5a:9e:75:d2;CM-QOS=1.1;CM-VER=3.0;
    Sun Jan 14 19:09:09 2018 Warning (5) MDD message timeout;CM-MAC=20:3d:66:9e:6a:ab;CMTS-MAC=00:42:5a:9e:75:d2;CM-QOS=1.1;CM-VER=3.0;
    Sun Jan 14 19:09:09 2018 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=20:3d:66:9e:6a:ab;CMTS-MAC=00:42:5a:9e:75:d2;CM-QOS=1.1;CM-VER=3.0;
    Sun Jan 14 19:09:08 2018 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=20:3d:66:9e:6a:ab;CMTS-MAC=00:42:5a:9e:75:d2;CM-QOS=1.1;CM-VER=3.0;
    Sun Jan 14 19:09:06 2018 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=20:3d:66:9e:6a:ab;CMTS-MAC=00:42:5a:9e:75:d2;CM-QOS=1.1;CM-VER=3.0;
    Sun Jan 14 19:09:05 2018 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=20:3d:66:9e:6a:ab;CMTS-MAC=00:42:5a:9e:75:d2;CM-QOS=1.1;CM-VER=3.0;
    Sun Jan 14 19:08:32 2018 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=20:3d:66:9e:6a:ab;CMTS-MAC=00:42:5a:9e:75:d2;CM-QOS=1.1;CM-VER=3.0;
    Sun Jan 14 19:08:31 2018 Warning (5) MDD message timeout;CM-MAC=20:3d:66:9e:6a:ab;CMTS-MAC=00:42:5a:9e:75:d2;CM-QOS=1.1;CM-VER=3.0;
    Sun Jan 14 19:08:30 2018 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=20:3d:66:9e:6a:ab;CMTS-MAC=00:42:5a:9e:75:d2;CM-QOS=1.1;CM-VER=3.0;
    Sun Jan 14 19:08:28 2018 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=20:3d:66:9e:6a:ab;CMTS-MAC=00:42:5a:9e:75:d2;CM-QOS=1.1;CM-VER=3.0;
    Sun Jan 14 19:08:15 2018 Warning (5) MDD message timeout;CM-MAC=20:3d:66:9e:6a:ab;CMTS-MAC=00:42:5a:9e:75:d2;CM-QOS=1.1;CM-VER=3.0;
    Sun Jan 14 19:08:12 2018 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=20:3d:66:9e:6a:ab;CMTS-MAC=00:42:5a:9e:75:d2;CM-QOS=1.1;CM-VER=3.0;
    Sun Jan 14 19:08:09 2018 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=20:3d:66:9e:6a:ab;CMTS-MAC=00:42:5a:9e:75:d2;CM-QOS=1.1;CM-VER=3.0;
    Sun Jan 14 19:08:07 2018 Warning (5) MDD message timeout;CM-MAC=20:3d:66:9e:6a:ab;CMTS-MAC=00:42:5a:9e:75:d2;CM-QOS=1.1;CM-VER=3.0;
    Sun Jan 14 19:07:32 2018 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=20:3d:66:9e:6a:ab;CMTS-MAC=00:42:5a:9e:75:d2;CM-QOS=1.1;CM-VER=3.0;
    Sun Jan 14 19:07:31 2018 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=20:3d:66:9e:6a:ab;CMTS-MAC=00:42:5a:9e:75:d2;CM-QOS=1.1;CM-VER=3.0;
    Sun Jan 14 19:07:13 2018 Warning (5) MDD message timeout;CM-MAC=20:3d:66:9e:6a:ab;CMTS-MAC=00:42:5a:9e:75:d2;CM-QOS=1.1;CM-VER=3.0;
    Sun Jan 14 19:07:12 2018 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=20:3d:66:9e:6a:ab;CMTS-MAC=00:42:5a:9e:75:d2;CM-QOS=1.1;CM-VER=3.0;
    Sun Jan 14 19:07:10 2018 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=20:3d:66:9e:6a:ab;CMTS-MAC=00:42:5a:9e:75:d2;CM-QOS=1.1;CM-VER=3.0;
    Sun Jan 14 19:07:08 2018 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=20:3d:66:9e:6a:ab;CMTS-MAC=00:42:5a:9e:75:d2;CM-QOS=1.1;CM-VER=3.0;
    Sun Jan 14 19:07:05 2018 Warning (5) MDD message timeout;CM-MAC=20:3d:66:9e:6a:ab;CMTS-MAC=00:42:5a:9e:75:d2;CM-QOS=1.1;CM-VER=3.0;
    Sun Jan 14 19:07:02 2018 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=20:3d:66:9e:6a:ab;CMTS-MAC=00:42:5a:9e:75:d2;CM-QOS=1.1;CM-VER=3.0;
    Sun Jan 14 19:07:01 2018 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=20:3d:66:9e:6a:ab;CMTS-MAC=00:42:5a:9e:75:d2;CM-QOS=1.1;CM-VER=3.0;
    Sun Jan 14 19:06:59 2018 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=20:3d:66:9e:6a:ab;CMTS-MAC=00:42:5a:9e:75:d2;CM-QOS=1.1;CM-VER=3.0;
    Sun Jan 14 19:06:47 2018 Warning (5) MDD message timeout;CM-MAC=20:3d:66:9e:6a:ab;CMTS-MAC=00:42:5a:9e:75:d2;CM-QOS=1.1;CM-VER=3.0;
    Sun Jan 14 19:06:47 2018 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=20:3d:66:9e:6a:ab;CMTS-MAC=00:42:5a:9e:75:d2;CM-QOS=1.1;CM-VER=3.0;
    Sun Jan 14 19:06:35 2018 Warning (5) MDD message timeout;CM-MAC=20:3d:66:9e:6a:ab;CMTS-MAC=00:42:5a:9e:75:d2;CM-QOS=1.1;CM-VER=3.0;
    Sun Jan 14 19:06:11 2018 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=20:3d:66:9e:6a:ab;CMTS-MAC=00:42:5a:9e:75:d2;CM-QOS=1.1;CM-VER=3.0;
    Sun Jan 14 19:06:05 2018 Warning (5) MDD message timeout;CM-MAC=20:3d:66:9e:6a:ab;CMTS-MAC=00:42:5a:9e:75:d2;CM-QOS=1.1;CM-VER=3.0;
    Sun Jan 14 19:06:04 2018 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=20:3d:66:9e:6a:ab;CMTS-MAC=00:42:5a:9e:75:d2;CM-QOS=1.1;CM-VER=3.0;
    Sun Jan 14 19:06:02 2018 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=20:3d:66:9e:6a:ab;CMTS-MAC=00:42:5a:9e:75:d2;CM-QOS=1.1;CM-VER=3.0;
    Sun Jan 14 19:05:45 2018 Warning (5) MDD message timeout;CM-MAC=20:3d:66:9e:6a:ab;CMTS-MAC=00:42:5a:9e:75:d2;CM-QOS=1.1;CM-VER=3.0;
    Sun Jan 14 19:05:42 2018 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=20:3d:66:9e:6a:ab;CMTS-MAC=00:42:5a:9e:75:d2;CM-QOS=1.1;CM-VER=3.0;
    Sun Jan 14 19:05:35 2018 Warning (5) MDD message timeout;CM-MAC=20:3d:66:9e:6a:ab;CMTS-MAC=00:42:5a:9e:75:d2;CM-QOS=1.1;CM-VER=3.0;
    Sun Jan 14 19:05:22 2018 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=20:3d:66:9e:6a:ab;CMTS-MAC=00:42:5a:9e:75:d2;CM-QOS=1.1;CM-VER=3.0;
    Sun Jan 14 19:05:21 2018 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=20:3d:66:9e:6a:ab;CMTS-MAC=00:42:5a:9e:75:d2;CM-QOS=1.1;CM-VER=3.0;
    Sun Jan 14 19:05:19 2018 Warning (5) MDD message timeout;CM-MAC=20:3d:66:9e:6a:ab;CMTS-MAC=00:42:5a:9e:75:d2;CM-QOS=1.1;CM-VER=3.0;
    Sun Jan 14 19:05:19 2018 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=20:3d:66:9e:6a:ab;CMTS-MAC=00:42:5a:9e:75:d2;CM-QOS=1.1;CM-VER=3.0;
    Sun Jan 14 19:05:03 2018 Warning (5) MDD message timeout;CM-MAC=20:3d:66:9e:6a:ab;CMTS-MAC=00:42:5a:9e:75:d2;CM-QOS=1.1;CM-VER=3.0;
    Sun Jan 14 19:04:58 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=20:3d:66:9e:6a:ab;CMTS-MAC=00:42:5a:9e:75:d2;CM-QOS=1.1;CM-VER=3.0;
    Sun Jan 14 19:04:39 2018 Warning (5) MDD message timeout;CM-MAC=20:3d:66:9e:6a:ab;CMTS-MAC=00:42:5a:9e:75:d2;CM-QOS=1.1;CM-VER=3.0;
    Sun Jan 14 19:04:39 2018 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=20:3d:66:9e:6a:ab;CMTS-MAC=00:42:5a:9e:75:d2;CM-QOS=1.1;CM-VER=3.0;
    Sun Jan 14 19:04:10 2018 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=20:3d:66:9e:6a:ab;CMTS-MAC=00:42:5a:9e:75:d2;CM-QOS=1.1;CM-VER=3.0;

  • Ultimate_Speed_'s avatar
    Ultimate_Speed_
    New Contributor
    1/14/2018 7:17 PM CST Date / Time Download Upload ping location
    1/14/2018 1:35 PM CST 174.67.36.131 17.72 Mb/s 5.35 Mb/s 13 ms Oklahoma City, OK < 50 mi
    1/14/2018 1:34 PM CST 174.67.36.131 3.46 Mb/s 12.29 Mb/s 15 ms Dallas, TX ~ 200 mi Share
    1/14/2018 1:32 PM CST 174.67.36.131 21.64 Mb/s 5.50 Mb/s 10 ms Dallas, TX ~ 200 mi Share
    1/14/2018 1:31 PM CST 174.67.36.131 11.41 Mb/s 5.40 Mb/s 11 ms Dallas, TX ~ 200 mi Share
    1/14/2018 1:30 PM CST 174.67.36.131 24.30 Mb/s 5.38 Mb/s 12 ms Dallas, TX ~ 200 mi Share
    1/14/2018 1:29 PM CST 174.67.36.131 20.26 Mb/s 5.30 Mb/s 9 ms Dallas, TX ~ 200 mi Share
    1/14/2018 1:29 PM CST 174.67.36.131 26.84 Mb/s 5.32 Mb/s 14 ms Dallas, TX ~ 200 mi Share
    1/14/2018 12:30 PM CST 174.67.36.131 5.33 Mb/s 5.29 Mb/s 13 ms Dallas, TX ~ 200 mi Share
    1/14/2018 12:29 PM CST 174.67.36.131 7.60 Mb/s 5.36 Mb/s 15 ms Oklahoma City, OK < 50 mi Share
    1/14/2018 12:58 AM CST 174.67.36.131 54.59 Mb/s 5.47 Mb/s 13 ms Dallas, TX ~ 200 mi Share
    1/13/2018 6:50 PM CST 174.67.36.131 6.54 Mb/s 5.60 Mb/s 11 ms Dallas, TX ~ 200 mi Share
    1/13/2018 6:34 PM CST 174.67.36.131 3.33 Mb/s 5.54 Mb/s 12 ms Dallas, TX ~ 200 mi Share
    1/12/2018 10:17 PM CST 174.67.36.131 58.72 Mb/s 5.48 Mb/s 13 ms Dallas, TX ~ 200 mi Share
    1/12/2018 10:11 PM CST 174.67.36.131 61.50 Mb/s 5.57 Mb/s 8 ms Oklahoma City, OK < 50 mi Share
    1/12/2018 10:10 PM CST 174.67.36.131 42.30 Mb/s 5.58 Mb/s 14 ms Dallas, TX ~ 200 mi Share
    1/12/2018 9:47 PM CST 174.67.36.131 1.93 Mb/s 11.35 Mb/s 8 ms Oklahoma City, OK < 50 mi Share
    1/12/2018 7:26 PM CST 174.67.36.131 2.28 Mb/s 11.87 Mb/s 8 ms Oklahoma City, OK < 50 mi Share
    1/12/2018 6:51 PM CST 174.67.36.131 2.57 Mb/s 7.85 Mb/s 7 ms Oklahoma City, OK < 50 mi Share
    1/12/2018 6:50 PM CST 174.67.36.131 2.21 Mb/s 11.91 Mb/s 15 ms Dallas, TX ~ 200 mi Share
    1/12/2018 6:41 PM CST 174.67.36.131 2.33 Mb/s 11.84 Mb/s 7 ms Oklahoma City, OK < 50 mi Share
    1/12/2018 5:33 PM CST 174.67.36.131 16.41 Mb/s 13.53 Mb/s 0 ms Oklahoma City, OK < 50 mi Share
    1/12/2018 5:32 PM CST 174.67.36.131 2.43 Mb/s 5.65 Mb/s 13 ms Dallas, TX ~ 200 mi Share
    1/12/2018 4:38 PM CST 174.67.36.131 3.98 Mb/s 5.47 Mb/s 13 ms Dallas, TX ~ 200 mi Share
    1/12/2018 4:19 PM CST 174.67.36.131 1.68 Mb/s 5.38 Mb/s 10 ms Dallas, TX ~ 200 mi Share
    1/12/2018 4:18 PM CST 174.67.36.131 2.53 Mb/s 5.53 Mb/s 10 ms Dallas, TX ~ 200 mi Share
    1/12/2018 4:17 PM CST 174.67.36.131 2.21 Mb/s 5.54 Mb/s 13 ms Dallas, TX ~ 200 mi Share
    1/12/2018 2:51 PM CST 174.67.36.131 61.37 Mb/s 5.60 Mb/s 10 ms Dallas, TX ~ 200 mi Share
    1/11/2018 7:06 PM CST 174.67.36.131 46.27 Mb/s 5.59 Mb/s 13 ms Dallas, TX ~ 200 mi Share
    1/11/2018 7:06 PM CST 174.67.36.131 23.81 Mb/s 5.49 Mb/s 13 ms Dallas, TX ~ 200 mi Share
    1/11/2018 5:09 PM CST 174.67.36.131 40.06 Mb/s 5.52 Mb/s 11 ms Oklahoma City, OK < 50 mi Share
    1/11/2018 5:07 PM CST 174.67.36.131 21.63 Mb/s 5.41 Mb/s 12 ms Dallas, TX ~ 200 mi Share
    1/11/2018 4:18 PM CST 174.67.36.131 22.26 Mb/s 5.40 Mb/s 13 ms Dallas, TX ~ 200 mi Share
    1/11/2018 1:57 PM CST 174.67.36.131 27.60 Mb/s 5.41 Mb/s 15 ms Dallas, TX ~ 200 mi Share
    1/10/2018 4:59 PM CST 174.67.36.131 60.47 Mb/s 5.55 Mb/s 14 ms Dallas, TX ~ 200 mi Share
    1/8/2018 12:03 AM CST 174.67.36.131 48.24 Mb/s 5.45 Mb/s 4 ms Dallas, TX ~ 200 mi Share
    1/8/2018 12:02 AM CST 174.67.36.131 55.57 Mb/s 5.42 Mb/s 7 ms Dallas, TX ~ 200 mi Share
    1/7/2018 2:23 PM CST 174.67.36.131 59.81 Mb/s 5.46 Mb/s 10 ms Dallas, TX ~ 200 mi Share
    1/7/2018 2:22 PM CST 174.67.36.131 59.91 Mb/s 5.62 Mb/s 14 ms Oklahoma City, OK < 50 mi Share
    1/7/2018 10:02 AM CST 174.67.36.131 60.39 Mb/s 5.61 Mb/s 16 ms Oklahoma City, OK < 50 mi Share
    1/7/2018 8:10 AM CST 174.67.36.131 61.17 Mb/s 5.62 Mb/s 0 ms Oklahoma City, OK < 50 mi Share
    1/7/2018 8:09 AM CST 174.67.36.131 59.37 Mb/s 5.40 Mb/s 10 ms Dallas, TX ~ 200 mi Share
    1/6/2018 11:29 PM CST 174.67.36.131 57.81 Mb/s 7.10 Mb/s 5 ms Dallas, TX ~ 200 mi Share
    1/6/2018 11:01 PM CST 174.67.36.131 59.39 Mb/s 5.78 Mb/s 5 ms Dallas, TX ~ 200 mi Share
    1/6/2018 9:26 PM CST 174.67.36.131 52.15 Mb/s 5.20 Mb/s 3 ms Dallas, TX ~ 200 mi Share
    1/6/2018 7:45 PM CST 174.67.36.131 60.19 Mb/s 5.46 Mb/s 10 ms Dallas, TX ~ 200 mi Share
    1/6/2018 10:38 AM CST 174.67.36.131 58.27 Mb/s 5.50 Mb/s 5 ms Dallas, TX ~ 200 mi Share
    1/6/2018 10:37 AM CST 174.67.36.131 60.42 Mb/s 5.66 Mb/s 17 ms Oklahoma City, OK < 50 mi Share
    1/5/2018 11:50 PM CST 174.67.36.131 61.37 Mb/s 5.51 Mb/s 5 ms Oklahoma City, OK < 50 mi Share
    1/5/2018 11:49 PM CST 174.67.36.131 53.70 Mb/s 5.50 Mb/s 5 ms Dallas, TX ~ 200 mi Share

  • Ultimate_Speed_'s avatar
    Ultimate_Speed_
    New Contributor

    Cox Internet Ultimate

    TV

     

    UP TO 300 MBPS

    DOWNLOADS

    (300 MBPS is equal to 2400 Mbps.

    I have never seen ANYONE who was capped reach speeds above 25 MBPS (200 Mbps) at COX Communications Incorporated OKC)

     

    PHONE

     

    HOME SECURITY & AUTOMATION

     

    Internet Ultimate

    • Up to 30 Mbps upload
    • 1,024 GB data plan
    • Now available with Panoramic WiFi!
    • Up to 200X faster than dial-up
    • Free access to over 500,000+ WiFi hotspots
    • 10 email accounts
  • Ultimate_Speed_'s avatar
    Ultimate_Speed_
    New Contributor

    Ultimate Speed User in OKC said:

    Internet Ultimate

    • Up to 30 Mbps upload
    • 1,024 GB data plan
    • Now available with Panoramic WiFi!
    • Up to 200X faster than dial-up
    • Free access to over 500,000+ WiFi hotspots
    • 10 email accounts

    Let's look at that.. Dialup is 56 k X 200 = 11200k  so take 11200 k and devide by 8 to get 1400 Mbps then devide by 8 again to get 175 MBPS... 

    But NOBODY gets above 25 MBPS while capped. Therefore COX is FALSE ADVERTISING the potential for services. If we uncapped our modems and set them to not exceed 300 MBPS  COX would have no legal recourse. But they have already breached the contract with false advertising of potential speeds available.

  • MarkM1's avatar
    MarkM1
    Former Moderator

    Ultimate Speed User in OKC,

    We do appreciate you reaching out to the Social Media group. If you are currently having an issue with your services, please send us an email at cox.help@cox.com with your name and full address so we can research your problem. Thank you for your time.