ContributionsMost RecentMost LikesSolutionsRe: Severe packet loss (Upload) to amazon web services (Fortnite) - UPDATE 1/9 Having the exact same issue. West side of Phoenix. Had two techs out and they were still unable to resolve the issue. Their solution is to check the signal to my home and ping the cox.net servers. Fortnite and Rocket League are unplayable and it's so *** frustrating. Re: STILL Packet Loss For Over a year in games (Fortnite, Overwatch, Rocket League, etc) Hey, I have this same issue. Have had 2 techs out and they have been unable to resolve the issue. I am on the westside of Arizona Re: Still having internet issues Maintenance is definitely not the issue. Considering I originally posted this at 9:30pm my time. Also, this is happening right now at 2pm my time. I am really *** sick of this ***. Upload dropped to 0.01 mbps again and my download is at 17mbps Re: Still having internet issues I live in Phoenix, Arizona. This is happening frequently. What about you? Still having internet issues Upload speed dropping to 0.01mbps. Cannot even do speed test, upload times out. These are my logs. Time Priority Description 2015-10-27, 22:24:59 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=40:5d:82:41:4c:80;CMTS-MAC=38:45:51:c3:06:f7;CM-QOS=1.1;CM-VER=3.0; 1970-1-1, 00:00:21 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=40:5d:82:41:4c:80;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; 1970-1-1, 00:00:30 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=40:5d:82:41:4c:80;CMTS-MAC=38:45:51:c3:06:f7;CM-QOS=1.0;CM-VER=3.0; 2015-10-27, 22:29:42 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=40:5d:82:41:4c:80;CMTS-MAC=38:45:51:c3:06:f7;CM-QOS=1.1;CM-VER=3.0; 2015-10-27, 22:30:20 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=40:5d:82:41:4c:80;CMTS-MAC=38:45:51:c3:06:f7;CM-QOS=1.1;CM-VER=3.0; 2015-10-27, 22:34:46 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=40:5d:82:41:4c:80;CMTS-MAC=38:45:51:c3:06:f7;CM-QOS=1.1;CM-VER=3.0; 2015-10-27, 23:15:38 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=40:5d:82:41:4c:80;CMTS-MAC=38:45:51:c3:06:f7;CM-QOS=1.1;CM-VER=3.0; 1970-1-1, 00:00:20 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=40:5d:82:41:4c:80;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; 1970-1-1, 00:00:29 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=40:5d:82:41:4c:80;CMTS-MAC=38:45:51:c3:06:f7;CM-QOS=1.0;CM-VER=3.0; 2015-10-27, 23:42:51 Critical (3) REG RSP not received;CM-MAC=40:5d:82:41:4c:80;CMTS-MAC=38:45:51:c3:06:f7;CM-QOS=1.1;CM-VER=3.0; 2015-10-27, 23:42:54 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=40:5d:82:41:4c:80;CMTS-MAC=38:45:51:c3:06:f7;CM-QOS=1.1;CM-VER=3.0; 2015-10-27, 23:43:30 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=40:5d:82:41:4c:80;CMTS-MAC=38:45:51:c3:06:f7;CM-QOS=1.1;CM-VER=3.0; 2015-10-27, 23:44:29 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=40:5d:82:41:4c:80;CMTS-MAC=38:45:51:c3:06:f7;CM-QOS=1.1;CM-VER=3.0; 1970-1-1, 00:00:20 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=40:5d:82:41:4c:80;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; 1970-1-1, 00:00:41 Critical (3) DHCP FAILED - Request sent, No response;CM-MAC=40:5d:82:41:4c:80;CMTS-MAC=38:45:51:c3:06:f7;CM-QOS=1.0;CM-VER=3.0; 2015-10-27, 23:45:54 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=40:5d:82:41:4c:80;CMTS-MAC=38:45:51:c3:06:f7;CM-QOS=1.1;CM-VER=3.0; 1970-1-1, 00:00:20 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=40:5d:82:41:4c:80;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; 2015-10-28, 00:20:01 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=40:5d:82:41:4c:80;CMTS-MAC=38:45:51:c3:06:f7;CM-QOS=1.1;CM-VER=3.0; 2015-10-28, 11:12:19 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=40:5d:82:41:4c:80;CMTS-MAC=38:45:51:c3:06:f7;CM-QOS=1.1;CM-VER=3.0; 2015-10-28, 14:01:45 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=40:5d:82:41:4c:80;CMTS-MAC=38:45:51:c3:06:f7;CM-QOS=1.1;CM-VER=3.0; 2015-10-30, 16:32:31 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=40:5d:82:41:4c:80;CMTS-MAC=38:45:51:c3:06:f7;CM-QOS=1.1;CM-VER=3.0; 2015-10-30, 16:32:36 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=40:5d:82:41:4c:80;CMTS-MAC=38:45:51:c3:06:f7;CM-QOS=1.1;CM-VER=3.0; 2015-10-30, 16:33:50 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=40:5d:82:41:4c:80;CMTS-MAC=38:45:51:c3:06:f7;CM-QOS=1.1;CM-VER=3.0; 2015-10-30, 16:33:51 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=40:5d:82:41:4c:80;CMTS-MAC=38:45:51:c3:06:f7;CM-QOS=1.1;CM-VER=3.0; 2015-10-30, 16:34:05 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=40:5d:82:41:4c:80;CMTS-MAC=38:45:51:c3:06:f7;CM-QOS=1.1;CM-VER=3.0; 2015-10-30, 16:34:06 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=40:5d:82:41:4c:80;CMTS-MAC=38:45:51:c3:06:f7;CM-QOS=1.1;CM-VER=3.0; 2015-10-30, 16:34:20 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=40:5d:82:41:4c:80;CMTS-MAC=38:45:51:c3:06:f7;CM-QOS=1.1;CM-VER=3.0; 2015-10-30, 16:34:21 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=40:5d:82:41:4c:80;CMTS-MAC=38:45:51:c3:06:f7;CM-QOS=1.1;CM-VER=3.0; 2015-10-30, 16:34:34 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=40:5d:82:41:4c:80;CMTS-MAC=38:45:51:c3:06:f7;CM-QOS=1.1;CM-VER=3.0; 2015-10-30, 16:34:36 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=40:5d:82:41:4c:80;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; 2015-10-30, 16:34:36 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=40:5d:82:41:4c:80;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; 1970-1-1, 00:00:31 Notice (6) Honoring MDD; IP provisioning mode = IPv4 1970-1-1, 00:00:33 Warning (5) DHCP WARNING - Non-critical field invalid in response ;CM-MAC=40:5d:82:41:4c:80;CMTS-MAC=38:45:51:c3:06:f7;CM-QOS=1.0;CM-VER=3.0; 2015-10-30, 16:51:04 Notice (6) TLV-11 - unrecognized OID;CM-MAC=40:5d:82:41:4c:80;CMTS-MAC=38:45:51:c3:06:f7;CM-QOS=1.1;CM-VER=3.0; 2015-10-30, 16:51:46 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=40:5d:82:41:4c:80;CMTS-MAC=38:45:51:c3:06:f7;CM-QOS=1.1;CM-VER=3.0; 2015-10-30, 19:37:41 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=40:5d:82:41:4c:80;CMTS-MAC=38:45:51:c3:06:f7;CM-QOS=1.1;CM-VER=3.0; 2015-10-30, 23:00:45 Warning (5) Dynamic Range Window violation 2015-10-30, 23:04:00 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=40:5d:82:41:4c:80;CMTS-MAC=38:45:51:c3:06:f7;CM-QOS=1.1;CM-VER=3.0; 2015-10-31, 14:19:42 Warning (5) Dynamic Range Window violation 2015-10-31, 14:30:55 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=40:5d:82:41:4c:80;CMTS-MAC=38:45:51:c3:06:f7;CM-QOS=1.1;CM-VER=3.0; Startup Procedure Procedure Status Comment Acquire Downstream Channel 939000000 Hz Locked Connectivity State OK Operational Boot State OK Operational Security Enabled BPI+ IP Provisioning Mode Honor MDD honorMdd(4) Downstream Bonded Channels Channel Lock Status Modulation Channel ID Frequency Power SNR Correctables Uncorrectables 1 Locked QAM256 94 939000000 Hz -3.1 dBmV 37.9 dB 7 0 2 Locked QAM256 73 813000000 Hz -1.1 dBmV 39.4 dB 4 0 3 Locked QAM256 74 819000000 Hz -0.2 dBmV 39.6 dB 2 0 4 Locked QAM256 75 825000000 Hz -1.2 dBmV 39.2 dB 9 0 5 Locked QAM256 76 831000000 Hz -1.9 dBmV 38.9 dB 16 0 6 Locked QAM256 77 837000000 Hz -1.3 dBmV 39.1 dB 12 0 7 Locked QAM256 78 843000000 Hz -1.6 dBmV 38.6 dB 32 0 8 Locked QAM256 79 849000000 Hz -1.3 dBmV 38.8 dB 31 0 9 Locked QAM256 80 855000000 Hz -1.7 dBmV 38.7 dB 38 0 10 Locked QAM256 89 909000000 Hz -2.6 dBmV 38.1 dB 23 0 11 Locked QAM256 90 915000000 Hz -2.1 dBmV 38.2 dB 30 0 12 Locked QAM256 91 921000000 Hz -2.1 dBmV 38.3 dB 33 0 13 Locked QAM256 92 927000000 Hz -2.2 dBmV 38.2 dB 23 0 14 Locked QAM256 93 933000000 Hz -3.7 dBmV 37.5 dB 35 0 15 Locked QAM256 95 945000000 Hz -3.5 dBmV 37.7 dB 19 0 16 Locked QAM256 96 951000000 Hz -4.2 dBmV 37.4 dB 9 0 Upstream Bonded Channels Channel Lock Status US Channel Type Channel ID Symbol Rate Frequency Power 1 Locked ATDMA 2 5120 Ksym/sec 23300000 Hz 39.2 dBmV 2 Locked TDMA and ATDMA 1 2560 Ksym/sec 18400000 Hz 39.2 dBmV 3 Locked ATDMA 3 5120 Ksym/sec 29800000 Hz 38.5 dBmV 4 Locked ATDMA 4 5120 Ksym/sec 36300000 Hz 40.8 dBmV Re: Internet connection slow It was the guy from this thread http://forums.cox.com/forum_home/internet_forum/f/5/t/11233.aspx EXACT same issue. Was on xbox live at the same time he was. Download and upload speed dropped really low. Couldn't stay connected. Directly connected to my modem and the issue remained. Turned off modem for 1 minute. (Still directly connected) and the issue remained. I was playing with some buddies and they were not having issues, so I know its not an xbox live issue. Re: Internet connection slow I won't need a coverage plan because I know the issue is not with my equipment. Someone else was having the exact same issue at the same time I was having this issue. I will send the email. Re: Erractic Internet Connection Speed Different PC, same results. Issue is definitely with the service. Re: Internet connection slow Is this going to cost me anything? I hope not, since the issue is not on my end. Re: Internet connection slow No splitters. I was directly connected to my modem last night when I posted this. That was my result. If I went to speedtest.net I would get the same message, or my speeds were <0.3mbs. It's back to normal again right now, but this issue is not resolved. This has been happening daily for the past 2 weeks. Another person was having the EXACT SAME issue. He posted a thread also. This was the threadhttp://forums.cox.com/forum_home/internet_forum/f/5/t/11233.aspx Modem -> Router -> PCs/Xboxes = lag Modem -> PC = lag Modem -> Xbox = lag Tested with old modem and my new modem. Tested with my old router and new router. Issue is definitely with the service.