Cox Community | User: Ultimate_Speed_

User Profile

Ultimate_Speed_

New Contributor

Joined 8 years ago

User Widgets

Contributions

Re: Frequently dropping internet - SYNC Timing Synchronization failure, RCS Partial Service, No Ranging Response received | Internet Problems
I have had 3 days this entire billing cycle of internet service that's even close to what I pay for. So if you broke down the amount I pay by the days in this billing cycle then multiply that by 3 days of service my bill should be $ 8 . how about all of the customers in this area just pay tor the days we receive the service we requested.? Would COX get on the ball to provide service to the customers or would they say " 'Eh, you agreed to our service that says "upto" so your screwed and we here at COX couldn't care less... Just pay us what we think you should pay and we might sometimes give you services like we promised in the beginning.
7 years ago Place Internet
7Views
0likes
0Comments
Re: Frequently dropping internet - SYNC Timing Synchronization failure, RCS Partial Service, No Ranging Response received | Internet Problems
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.
7 years ago Place Internet
7Views
0likes
0Comments
Re: Frequently dropping internet - SYNC Timing Synchronization failure, RCS Partial Service, No Ranging Response received | Internet Problems
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
7 years ago Place Internet
3Views
0likes
0Comments
Re: Frequently dropping internet - SYNC Timing Synchronization failure, RCS Partial Service, No Ranging Response received | Internet Problems
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 <50mi 1/14/2018 1:34 PM CST 174.67.36.131 3.46 Mb/s 12.29 Mb/s 15 ms Dallas, TX ~200mi Share 1/14/2018 1:32 PM CST 174.67.36.131 21.64 Mb/s 5.50 Mb/s 10 ms Dallas, TX ~200mi Share 1/14/2018 1:31 PM CST 174.67.36.131 11.41 Mb/s 5.40 Mb/s 11 ms Dallas, TX ~200mi Share 1/14/2018 1:30 PM CST 174.67.36.131 24.30 Mb/s 5.38 Mb/s 12 ms Dallas, TX ~200mi Share 1/14/2018 1:29 PM CST 174.67.36.131 20.26 Mb/s 5.30 Mb/s 9 ms Dallas, TX ~200mi Share 1/14/2018 1:29 PM CST 174.67.36.131 26.84 Mb/s 5.32 Mb/s 14 ms Dallas, TX ~200mi Share 1/14/2018 12:30 PM CST 174.67.36.131 5.33 Mb/s 5.29 Mb/s 13 ms Dallas, TX ~200mi 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 <50mi Share 1/14/2018 12:58 AM CST 174.67.36.131 54.59 Mb/s 5.47 Mb/s 13 ms Dallas, TX ~200mi Share 1/13/2018 6:50 PM CST 174.67.36.131 6.54 Mb/s 5.60 Mb/s 11 ms Dallas, TX ~200mi Share 1/13/2018 6:34 PM CST 174.67.36.131 3.33 Mb/s 5.54 Mb/s 12 ms Dallas, TX ~200mi Share 1/12/2018 10:17 PM CST 174.67.36.131 58.72 Mb/s 5.48 Mb/s 13 ms Dallas, TX ~200mi 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 <50mi Share 1/12/2018 10:10 PM CST 174.67.36.131 42.30 Mb/s 5.58 Mb/s 14 ms Dallas, TX ~200mi 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 <50mi 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 <50mi 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 <50mi Share 1/12/2018 6:50 PM CST 174.67.36.131 2.21 Mb/s 11.91 Mb/s 15 ms Dallas, TX ~200mi 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 <50mi 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 <50mi Share 1/12/2018 5:32 PM CST 174.67.36.131 2.43 Mb/s 5.65 Mb/s 13 ms Dallas, TX ~200mi Share 1/12/2018 4:38 PM CST 174.67.36.131 3.98 Mb/s 5.47 Mb/s 13 ms Dallas, TX ~200mi Share 1/12/2018 4:19 PM CST 174.67.36.131 1.68 Mb/s 5.38 Mb/s 10 ms Dallas, TX ~200mi Share 1/12/2018 4:18 PM CST 174.67.36.131 2.53 Mb/s 5.53 Mb/s 10 ms Dallas, TX ~200mi Share 1/12/2018 4:17 PM CST 174.67.36.131 2.21 Mb/s 5.54 Mb/s 13 ms Dallas, TX ~200mi Share 1/12/2018 2:51 PM CST 174.67.36.131 61.37 Mb/s 5.60 Mb/s 10 ms Dallas, TX ~200mi Share 1/11/2018 7:06 PM CST 174.67.36.131 46.27 Mb/s 5.59 Mb/s 13 ms Dallas, TX ~200mi Share 1/11/2018 7:06 PM CST 174.67.36.131 23.81 Mb/s 5.49 Mb/s 13 ms Dallas, TX ~200mi 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 <50mi Share 1/11/2018 5:07 PM CST 174.67.36.131 21.63 Mb/s 5.41 Mb/s 12 ms Dallas, TX ~200mi Share 1/11/2018 4:18 PM CST 174.67.36.131 22.26 Mb/s 5.40 Mb/s 13 ms Dallas, TX ~200mi Share 1/11/2018 1:57 PM CST 174.67.36.131 27.60 Mb/s 5.41 Mb/s 15 ms Dallas, TX ~200mi Share 1/10/2018 4:59 PM CST 174.67.36.131 60.47 Mb/s 5.55 Mb/s 14 ms Dallas, TX ~200mi Share 1/8/2018 12:03 AM CST 174.67.36.131 48.24 Mb/s 5.45 Mb/s 4 ms Dallas, TX ~200mi Share 1/8/2018 12:02 AM CST 174.67.36.131 55.57 Mb/s 5.42 Mb/s 7 ms Dallas, TX ~200mi Share 1/7/2018 2:23 PM CST 174.67.36.131 59.81 Mb/s 5.46 Mb/s 10 ms Dallas, TX ~200mi 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 <50mi 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 <50mi 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 <50mi Share 1/7/2018 8:09 AM CST 174.67.36.131 59.37 Mb/s 5.40 Mb/s 10 ms Dallas, TX ~200mi Share 1/6/2018 11:29 PM CST 174.67.36.131 57.81 Mb/s 7.10 Mb/s 5 ms Dallas, TX ~200mi Share 1/6/2018 11:01 PM CST 174.67.36.131 59.39 Mb/s 5.78 Mb/s 5 ms Dallas, TX ~200mi Share 1/6/2018 9:26 PM CST 174.67.36.131 52.15 Mb/s 5.20 Mb/s 3 ms Dallas, TX ~200mi Share 1/6/2018 7:45 PM CST 174.67.36.131 60.19 Mb/s 5.46 Mb/s 10 ms Dallas, TX ~200mi Share 1/6/2018 10:38 AM CST 174.67.36.131 58.27 Mb/s 5.50 Mb/s 5 ms Dallas, TX ~200mi 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 <50mi 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 <50mi Share 1/5/2018 11:49 PM CST 174.67.36.131 53.70 Mb/s 5.50 Mb/s 5 ms Dallas, TX ~200mi Share
7 years ago Place Internet
2Views
0likes
0Comments
Re: Frequently dropping internet - SYNC Timing Synchronization failure, RCS Partial Service, No Ranging Response received | Internet Problems
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. Time Priority Description 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;
7 years ago Place Internet
2Views
0likes
0Comments
Re: Frequently dropping internet - SYNC Timing Synchronization failure, RCS Partial Service, No Ranging Response received | Internet Problems
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.
7 years ago Place Internet
20Views
0likes
0Comments
Re: Frequently dropping internet - SYNC Timing Synchronization failure, RCS Partial Service, No Ranging Response received | Internet Problems
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 usuallycaused by a loose connection on coaxial cable - this could be at a neighborshouse 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 signaland 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 veryexpensiveto replace). So it is cheaper for us to say its your equipment having the issue and not our super structure network that is a lotolder than your equipment.
7 years ago Place Internet
10Views
0likes
0Comments
Re: Not getting Ultimate speeds
I have had the Ultimate internet for over a year now in OKC OK. I average 100 to 110 MBps download speed. The sales point for this package is 300 MBps but I have NEVER been close to this. Once I accidently reached 172 MBps but COX caught it and suddenly my speeds went down. I have addressed this issue with tech support so many times, I am sick and tired of the excuses and outright lies given. Recently my bill has jumped $25 dollars. I looked online and the cox site will not allow me to view pricing for lower packages because I am signed into my account. False promises and inaccurate pricing (they add taxes, fees and surcharges making the actual price jump by almost 15$ per month) are driving customers away. the inability to downgrade online while signed into my account is beyond stupid. Cox need to realize they are not the only high speed provider in this area and yes their *** does stink. They are not giving us a gift from god and others can give us the same possibly better services without the F' you we got ya' attitude displayed through their online marketing and website. I am one seriously pissed off disappointed customer.
8 years ago Place Archives
1View
0likes
0Comments