Oklahoma City / Edmond - Upload Power Levels Unstable - Causing T3 Timeout / Outages
I am near 14140 Broadway Ext, in Edmond, OK. I believe we are having a partial service interruption going on 3 days. I have humored tech support up to and including re-flashing my firmware on my modem. I can't rule out being a traffic increase relation, i.e. the neighbors are home in the evening, but the issues were prevalent all day Friday. Event Logs: Sat Oct 10 07:21:37 2015 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=6c:ca:08:72:9c:f1;CMTS-MAC=00:19:2f:e6:7f:b2;CM-QOS=1.1;CM-VER=3.0; Sat Oct 10 04:59:36 2015 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=6c:ca:08:72:9c:f1;CMTS-MAC=00:19:2f:e6:7f:b2;CM-QOS=1.1;CM-VER=3.0; Sat Oct 10 02:51:26 2015 Error (4) DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=6c:ca:08:72:9c:f1;CMTS-MAC=00:19:2f:e6:7f:b2;CM-QOS=1.1;CM-VER=3.0; Sat Oct 10 00:35:43 2015 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=6c:ca:08:72:9c:f1;CMTS-MAC=00:19:2f:e6:7f:b2;CM-QOS=1.1;CM-VER=3.0; Sat Oct 10 00:35:28 2015 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=6c:ca:08:72:9c:f1;CMTS-MAC=00:19:2f:e6:7f:b2;CM-QOS=1.1;CM-VER=3.0; Fri Oct 09 22:29:08 2015 Warning (5) Dynamic Range Window violation Fri Oct 09 22:28:33 2015 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=6c:ca:08:72:9c:f1;CMTS-MAC=00:19:2f:e6:7f:b2;CM-QOS=1.1;CM-VER=3.0; Fri Oct 09 22:28:09 2015 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=6c:ca:08:72:9c:f1;CMTS-MAC=00:19:2f:e6:7f:b2;CM-QOS=1.1;CM-VER=3.0; Fri Oct 09 21:39:04 2015 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=6c:ca:08:72:9c:f1;CMTS-MAC=00:19:2f:e6:7f:b2;CM-QOS=1.1;CM-VER=3.0; Fri Oct 09 21:38:49 2015 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=6c:ca:08:72:9c:f1;CMTS-MAC=00:19:2f:e6:7f:b2;CM-QOS=1.1;CM-VER=3.0; Fri Oct 09 14:52:12 2015 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=6c:ca:08:72:9c:f1;CMTS-MAC=00:19:2f:e6:7f:b2;CM-QOS=1.1;CM-VER=3.0; Fri Oct 09 14:51:29 2015 Notice (6) TLV-11 - unrecognized OID;CM-MAC=6c:ca:08:72:9c:f1;CMTS-MAC=00:19:2f:e6:7f:b2;CM-QOS=1.1;CM-VER=3.0; Time Not Established Warning (5) DHCP WARNING - Non-critical field invalid in response ;CM-MAC=6c:ca:08:72:9c:f1;CMTS-MAC=00:19:2f:e6:7f:b2;CM-QOS=1.0;CM-VER=3.0; Startup Procedure Procedure Status Comment Acquire Downstream Channel Locked Connectivity State OK Operational Boot State OK Operational Configuration File OK Security Enabled BPI+ DOCSIS Network Access Enabled Allowed Downstream Bonded Channels Channel Lock Status Modulation Channel ID Frequency Power SNR Corrected Uncorrectables 1 Locked QAM256 50 819000000 Hz -0.1 dBmV 38.4 dB 305 574 2 Locked QAM256 49 813000000 Hz 0.0 dBmV 38.5 dB 427 699 3 Locked QAM256 51 825000000 Hz 0.3 dBmV 38.6 dB 238 512 4 Locked QAM256 52 831000000 Hz 0.5 dBmV 38.9 dB 151 443 5 Locked QAM256 53 837000000 Hz 0.1 dBmV 38.9 dB 159 157 6 Locked QAM256 54 843000000 Hz -1.4 dBmV 38.3 dB 140 106 7 Locked QAM256 55 849000000 Hz -1.6 dBmV 38.3 dB 194 293 8 Locked QAM256 56 855000000 Hz -2.0 dBmV 38.2 dB 274 417 9 Locked QAM256 57 861000000 Hz -2.5 dBmV 38.3 dB 255 531 10 Locked QAM256 58 867000000 Hz -2.9 dBmV 38.3 dB 452 638 11 Locked QAM256 59 873000000 Hz -2.4 dBmV 38.3 dB 415 568 12 Locked QAM256 60 879000000 Hz -2.8 dBmV 38.1 dB 223 433 13 Locked QAM256 61 885000000 Hz -3.0 dBmV 38.1 dB 172 415 14 Locked QAM256 62 891000000 Hz -3.0 dBmV 38.2 dB 106 182 15 Locked QAM256 63 897000000 Hz -2.7 dBmV 38.3 dB 121 130 16 Locked QAM256 64 903000000 Hz -4.1 dBmV 37.8 dB 42417 51328 Upstream Bonded Channels Channel Lock Status US Channel Type Channel ID Symbol Rate Frequency Power 1 Locked ATDMA 1 2560 Ksym/sec 22600000 Hz 47.0 dBmV 2 Locked ATDMA 2 5120 Ksym/sec 27500000 Hz 47.0 dBmV 3 Locked ATDMA 3 5120 Ksym/sec 34000000 Hz 48.0 dBmV 4 Locked ATDMA 4 2560 Ksym/sec 38900000 Hz 47.5 dBmV Tech support was useless today though, they can't escalate till a technician has been on site. Funnily enough the technician has been on site 2 times now. This latest issues though has been on going issue for at least 3 days. Help Desk Ticket Reference: #2942900 Checked with my neighbors, two are experiencing it, a third didn't report any issues and I found three other forum posts, exhibiting the same or similar behavior in my area. Atypical error seen in logs: Started Unicast Maintenance Ranging - No Response received - T3 time-out; My Steps to Reproduce: Saturate your upload bandwidth 100% for 1 to 2 minutes consistently. Time out occurs, the modem may go offline, but the connection is definitely lost. Power levels at the time of upload are approaching 52.0+. It's definitely something new on Cox's end as this has only been an issue for about 72 hours. Any form of upload saturation disconnects the modem, so all connectivity is interrupted. A house full of Netflix users is not a big deal, but the minute I upload something to a FTP or play Destiny utilizing P2P hosting, the whole internet goes offline. I have some time stamps of occurrence, I set my computer to test upload in 5 minute intervals using the newer/unbiased speed test website: http://www.testmy.net Speedtest.net is not really seeing any issue so I looked for alternatives. Packet loss is 0%, unless a T3 time out is just about to occur then we start seeing it go up in %. That's expected since a timeout is in progress. The correlation is that just before disconnection, upload speeds / bandwidths are low. Examples: Fri Oct 09 2015 @ 10:26:16 pm - Upload Speed - 4.59 Mb/s (avg is normally 11.5 Mb/s) Fri Oct 09 22:29:08 2015 Warning (5) Dynamic Range Window violation Fri Oct 09 22:28:33 2015 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=6c:ca:08:72:9c:f1;CMTS-MAC=00:19:2f:e6:7f:b2;CM-QOS=1.1;CM-VER=3.0; Fri Oct 09 22:28:09 2015 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=6c:ca:08:72:9c:f1;CMTS-MAC=00:19:2f:e6:7f:b2;CM-QOS=1.1;CM-VER=3.0; Further Details: Motorola SB6183, 16xDown, 4xUp, Firmware Version: SB6183-9.2.0.0-GA-04-37-NOSH Firmware reflashed, multiple restarts/resets, removed the router from the equation, checked all fittings, last service visit "replaced" some fittings, not sure what else, they didn't communicate to my wife what they had done. They were here visiting, despite Cox finally admitting to a local outage.3.3KViews0likes6CommentsExtremely Slow Upload Speeds!!! Started Unicast Maintenance Ranging - No Response received
I have been a customer for a year now, and for four months out of the year i have been having intermittent problems. The thing is i work online and pay for the fastest internet speed that they have. My bill alone for internet is $90. I have been getting T3 and T4 timeouts constantly. They sent every level of tech out to my home, and still no fix!...... The last tech who was a supervisor said that the problem was a "plant issue". That was 2 months ago, now im still getting upload speeds @ 1.35mbps ......I hold meetings and conferences online streaming and because of this issue i have been messing up with work. Please!!!!! I need help!!! I have viewed this forum and other forums involving this problem and did the proper research, but no one will speak on this problem and there have been no resolution concerning these timeouts! HERE IS A RUNDOWN OF MY EVEN LOG! Mon Aug 24 06:46:07 2015 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=6c:b0:ce:65:db:58;CMTS-MAC=00:13:5f:00:d7:ac;CM-QOS=1.1;CM-VER=3.0; Mon Aug 24 06:03:37 2015 Notice (6) TLV-11 - unrecognized OID;CM-MAC=6c:b0:ce:65:db:58;CMTS-MAC=00:13:5f:00:d7:ac;CM-QOS=1.1;CM-VER=3.0; Mon Aug 24 06:02:31 2015 Critical (3) Resetting the cable modem due to docsDevResetNow Mon Aug 24 05:46:37 2015 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=6c:b0:ce:65:db:58;CMTS-MAC=00:13:5f:00:d7:ac;CM-QOS=1.1;CM-VER=3.0; Mon Aug 24 05:46:30 2015 Critical (3) REG RSP not received;CM-MAC=6c:b0:ce:65:db:58;CMTS-MAC=00:13:5f:00:d7:ac;CM-QOS=1.1;CM-VER=3.0; Mon Aug 24 05:20:18 2015 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=6c:b0:ce:65:db:58;CMTS-MAC=00:13:5f:00:d7:ac;CM-QOS=1.1;CM-VER=3.0; Sun Aug 23 13:43:54 2015 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=6c:b0:ce:65:db:58;CMTS-MAC=00:13:5f:00:d7:ac;CM-QOS=1.1;CM-VER=3.0; Sun Aug 23 05:34:34 2015 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=6c:b0:ce:65:db:58;CMTS-MAC=00:13:5f:00:d7:ac;CM-QOS=1.1;CM-VER=3.0; Sun Aug 23 03:00:25 2015 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=6c:b0:ce:65:db:58;CMTS-MAC=00:13:5f:00:d7:ac;CM-QOS=1.1;CM-VER=3.0; Sat Aug 22 23:48:54 2015 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=6c:b0:ce:65:db:58;CMTS-MAC=00:13:5f:00:d7:ac;CM-QOS=1.1;CM-VER=3.0; Sat Aug 22 23:48:50 2015 Critical (3) REG RSP not received;CM-MAC=6c:b0:ce:65:db:58;CMTS-MAC=00:13:5f:00:d7:ac;CM-QOS=1.1;CM-VER=3.0; Sat Aug 22 23:47:39 2015 Critical (3) Resetting the cable modem due to docsDevResetNow Sat Aug 22 23:13:48 2015 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=6c:b0:ce:65:db:58;CMTS-MAC=00:13:5f:00:d7:ac;CM-QOS=1.1;CM-VER=3.0; Sat Aug 22 12:34:55 2015 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=6c:b0:ce:65:db:58;CMTS-MAC=00:13:5f:00:d7:ac;CM-QOS=1.1;CM-VER=3.0; Sat Aug 22 02:41:10 2015 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=6c:b0:ce:65:db:58;CMTS-MAC=00:13:5f:00:d7:ac;CM-QOS=1.1;CM-VER=3.0; Sat Aug 22 02:13:34 2015 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=6c:b0:ce:65:db:58;CMTS-MAC=00:13:5f:00:d7:ac;CM-QOS=1.1;CM-VER=3.0; Fri Aug 21 13:58:15 2015 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=6c:b0:ce:65:db:58;CMTS-MAC=00:13:5f:00:d7:ac;CM-QOS=1.1;CM-VER=3.0; Thu Aug 20 06:16:20 2015 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=6c:b0:ce:65:db:58;CMTS-MAC=00:13:5f:00:d7:ac;CM-QOS=1.1;CM-VER=3.0; Thu Aug 20 03:44:51 2015 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=6c:b0:ce:65:db:58;CMTS-MAC=00:13:5f:00:d7:ac;CM-QOS=1.1;CM-VER=3.0; Wed Aug 19 12:17:40 2015 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=6c:b0:ce:65:db:58;CMTS-MAC=00:13:5f:00:d7:ac;CM-QOS=1.1;CM-VER=3.0; Wed Aug 19 05:18:34 2015 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=6c:b0:ce:65:db:58;CMTS-MAC=00:13:5f:00:d7:ac;CM-QOS=1.1;CM-VER=3.0; Tue Aug 18 18:07:48 2015 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=6c:b0:ce:65:db:58;CMTS-MAC=00:13:5f:00:d7:ac;CM-QOS=1.1;CM-VER=3.0; Mon Aug 17 07:41:24 2015 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=6c:b0:ce:65:db:58;CMTS-MAC=00:13:5f:00:d7:ac;CM-QOS=1.1;CM-VER=3.0; Mon Aug 17 02:37:55 2015 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=6c:b0:ce:65:db:58;CMTS-MAC=00:13:5f:00:d7:ac;CM-QOS=1.1;CM-VER=3.0; Sun Aug 16 01:45:48 2015 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=6c:b0:ce:65:db:58;CMTS-MAC=00:13:5f:00:d7:ac;CM-QOS=1.1;CM-VER=3.0; Sat Aug 15 18:09:15 2015 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=6c:b0:ce:65:db:58;CMTS-MAC=00:13:5f:00:d7:ac;CM-QOS=1.1;CM-VER=3.0; Startup Procedure Procedure Status Comment Acquire Downstream Channel 813000000 Hz Locked Connectivity State OK Operational Boot State OK Operational Configuration File OK ^1/675721E6/132003 Security Enabled BPI+ Downstream Bonded Channels Lock Status Modulation Channel ID Symbol rate Frequency Power SNR DOCSIS/EuroDOCSIS locked Locked QAM256 73 5360 Ksym/sec 813000000 Hz 8.7 dBmV 39.4 dB DOCSIS Locked QAM256 74 5360 Ksym/sec 819000000 Hz 8.0 dBmV 39.3 dB DOCSIS Locked QAM256 75 5360 Ksym/sec 825000000 Hz 7.3 dBmV 39.0 dB DOCSIS Locked QAM256 76 5360 Ksym/sec 831000000 Hz 6.7 dBmV 39.1 dB DOCSIS Locked QAM256 81 5360 Ksym/sec 861000000 Hz 7.0 dBmV 39.1 dB DOCSIS Locked QAM256 82 5360 Ksym/sec 867000000 Hz 7.0 dBmV 39.0 dB DOCSIS Locked QAM256 83 5360 Ksym/sec 873000000 Hz 7.3 dBmV 39.0 dB DOCSIS Locked QAM256 84 5360 Ksym/sec 879000000 Hz 7.1 dBmV 38.9 dB DOCSIS Upstream Bonded Channels Lock Status Modulation Channel ID Symbol rate Frequency Power Locked ATDMA 3 5120 Ksym/sec 28202000 Hz 43.0 dBmV Locked TDMA and ATDMA 1 2560 Ksym/sec 20202000 Hz 42.5 dBmV Locked TDMA and ATDMA 2 2560 Ksym/sec 23402000 Hz 44.5 dBmV Locked ATDMA 4 5120 Ksym/sec 35102000 Hz 44.5 dBmV 8/24/2015 6:37 AM EDT 68.13.216.18572.31 Mb/s 0.64 Mb/s 32 ms Chesapeake, VA<50miShare8/24/2015 6:29 AM EDT 68.13.216.18551.47 Mb/s 4.25 Mb/s 35 ms Chesapeake, VA<50miShare8/24/2015 6:28 AM EDT 68.13.216.18547.72 Mb/s 1.17 Mb/s 32 ms Chesapeake, VA<50miShare8/24/2015 6:25 AM EDT 68.13.216.18566.64 Mb/s 0.70 Mb/s 32 ms Chesapeake, VA<50miShare8/24/2015 6:20 AM EDT 68.13.216.185167.37 Mb/s 13.69 Mb/s 29 ms Chesapeake, VA<50miShare8/24/2015 6:17 AM EDT 68.13.216.18581.83 Mb/s 13.42 Mb/s 30 ms Chesapeake, VA<50miShare8/24/2015 6:15 AM EDT 68.13.216.18545.23 Mb/s 1.62 Mb/s 31 ms Chesapeake, VA<50miShare8/24/2015 6:14 AM EDT 68.13.216.18598.19 Mb/s 2.25 Mb/s 29 ms Chesapeake, VA<50miShare8/24/2015 6:13 AM EDT 68.13.216.18554.85 Mb/s 4.09 Mb/s 32 ms Chesapeake, VA<50miShare8/24/2015 6:11 AM EDT 68.13.216.18568.22 Mb/s 17.93 Mb/s 34 ms Chesapeake, VA<50miShare8/24/2015 6:10 AM EDT 68.13.216.18591.54 Mb/s 3.17 Mb/s 32 ms Chesapeake, VA<50miShare8/24/2015 6:10 AM EDT 68.13.216.185142.18 Mb/s 18.49 Mb/s 32 ms Chesapeake, VA<50miShare8/24/2015 6:09 AM EDT 68.13.216.18575.50 Mb/s 5.51 Mb/s 34 ms Chesapeake, VA<50miShare8/24/2015 6:07 AM EDT 68.13.216.18560.31 Mb/s 21.70 Mb/s 34 ms Chesapeake, VA<50miShare8/24/2015 6:06 AM EDT 68.13.216.185150.58 Mb/s 21.98 Mb/s 32 ms Chesapeake, VA<50miShare8/24/2015 6:05 AM EDT 68.13.216.18593.70 Mb/s 22.26 Mb/s 34 ms Chesapeake, VA<50miShare8/24/2015 5:51 AM EDT 68.98.247.19962.60 Mb/s 1.74 Mb/s 33 ms Chesapeake, VA<50miShare8/24/2015 5:41 AM EDT 68.98.247.19969.84 Mb/s 3.49 Mb/s 32 ms Chesapeake, VA<50miShare8/24/2015 5:30 AM EDT 68.98.247.19973.57 Mb/s 5.13 Mb/s 34 ms Chesapeake, VA<50miShare8/24/2015 5:29 AM EDT 68.98.247.199108.80 Mb/s 3.37 Mb/s 34 ms Chesapeake, VA<50miShare8/24/2015 5:28 AM EDT 68.98.247.199174.02 Mb/s 10.00 Mb/s 30 ms Chesapeake, VA<50miShare8/24/2015 5:27 AM EDT 68.98.247.199149.44 Mb/s 17.56 Mb/s 29 ms Chesapeake, VA<50miShare8/23/2015 2:15 PM EDT 68.98.247.19989.39 Mb/s 22.17 Mb/s 30 ms Chesapeake, VA<50miShare8/23/2015 11:14 AM EDT 68.98.247.19993.95 Mb/s 22.35 Mb/s 30 ms Chesapeake, VA<50miShare8/23/2015 11:04 AM EDT 68.98.247.19985.74 Mb/s 22.57 Mb/s 30 ms Chesapeake, VA<50miShare8/23/2015 10:12 AM EDT 68.98.247.199142.90 Mb/s 22.35 Mb/s 33 ms Chesapeake, VA<50miShare8/23/2015 10:11 AM EDT 68.98.247.199137.29 Mb/s 22.57 Mb/s 31 ms Chesapeake, VA<50miShare8/23/2015 12:59 AM EDT 68.98.247.19962.82 Mb/s 1.15 Mb/s 30 ms Chesapeake, VA<50miShare8/23/2015 12:58 AM EDT 68.98.247.19954.27 Mb/s 6.10 Mb/s 34 ms Chesapeake, VA<50miShare8/23/2015 12:55 AM EDT 68.98.247.19952.43 Mb/s 1.42 Mb/s 30 ms Chesapeake, VA<50miShare8/23/2015 12:38 AM EDT 68.98.247.19980.54 Mb/s 5.11 Mb/s 23 ms Rocky Mount, NC~100miShare8/23/2015 12:36 AM EDT 68.98.247.199109.39 Mb/s 22.28 Mb/s 21 ms Rocky Mount, NC~100miShare8/23/2015 12:35 AM EDT 68.98.247.19994.18 Mb/s 8.01 Mb/s 21 ms Rocky Mount, NC~100miShare8/23/2015 12:30 AM EDT 68.98.247.19988.04 Mb/s 0.61 Mb/s 22 ms Rocky Mount, NC~100miShare8/23/2015 12:29 AM EDT 68.98.247.19992.63 Mb/s 2.72 Mb/s 23 ms Rocky Mount, NC~100miShare8/23/2015 12:28 AM EDT 68.98.247.19979.95 Mb/s 8.43 Mb/s 22 ms Rocky Mount, NC~100miShare8/23/2015 12:26 AM EDT 68.98.247.19975.52 Mb/s 1.50 Mb/s 24 ms Rocky Mount, NC~100miShare8/22/2015 11:56 PM EDT 68.98.247.19948.79 Mb/s 1.37 Mb/s 23 ms Rocky Mount, NC~100miShare8/22/2015 11:39 PM EDT 68.98.247.19916.60 Mb/s 6.31 Mb/s 32 ms Chesapeake, VA<50miShare8/22/2015 11:10 PM EDT 68.98.247.19936.31 Mb/s 0.63 Mb/s 36 ms Chesapeake, VA<50miShare8/22/2015 11:03 PM EDT 68.98.247.19924.71 Mb/s 1.26 Mb/s 30 ms Chesapeake, VA<50miShare8/22/2015 11:02 PM EDT 68.98.247.19930.49 Mb/s 1.03 Mb/s 34 ms Chesapeake, VA<50miShare8/22/2015 11:01 PM EDT 68.98.247.19916.06 Mb/s 0.14 Mb/s 34 ms Chesapeake, VA<50miShare8/22/2015 10:59 PM EDT 68.98.247.19947.25 Mb/s 0.65 Mb/s 34 ms Chesapeake, VA<50miShare8/22/2015 10:50 PM EDT 68.98.247.19917.18 Mb/s 10.56 Mb/s 27 ms Richmond, VA~100miShare8/22/2015 9:01 PM EDT 68.98.247.19921.48 Mb/s 2.91 Mb/s 32 ms Chesapeake, VA<50miShare8/22/2015 8:41 PM EDT 68.98.247.19958.12 Mb/s 22.61 Mb/s 37 ms Chesapeake, VA<50miShare8/22/2015 8:39 PM EDT 68.98.247.19923.78 Mb/s 1.63 Mb/s 31 ms Chesapeake, VA<50miShare8/22/2015 8:33 PM EDT 68.98.247.19931.64 Mb/s 1.46 Mb/s 34 ms Chesapeake, VA<50miShare8/22/2015 7:59 PM EDT 68.98.247.19948.69 Mb/s 8.34 Mb/s 33 ms Chesapeake, VA<50miShareLOAD MORE RESULTS HERE ARE MY SPEED TEST2.7KViews0likes1CommentConnection blocking to specific IP address
Within the last week, it appears connecting to a specific IP address (91.189.95.85)has become throttled / blocked / rate limited. I can only make somewhere in the neighborhood of 7open connections before I am temporarily blocked from making any more simultaneous connections. This is not a problem on my home LAN internal network as I have tested this at multiple cox home networks in the same neighborhood with the same results. I have also run the same tests from non-cox networks (including from an AWS machine), and my test is not being blocked there in any capacity. This leads me to believe there is something new on the cox network that is rate-limiting or throttling outbound connections going to a single destination. The test I am running is: xargs -I % -P 5 curl -I "http://ppa.launchpad.net/ondrej/php/ubuntu/pool/main/p/php-imagick/php8.0-imagick_3.4.4+php8.0+3.4.4-7+ubuntu20.04.1+deb.sury.org+1_amd64.deb" < <(printf '%s\n' {1..8}) using {1..7} will complete, whereas {1..8} will hang on the last connection, and eventually time out with: curl: (7) Failed to connect to ppa.launchpad.net port 80: Operation timed out I am unsure where else to go to find a resolution to this problem.Solved1.6KViews0likes1CommentCritical T3 Errors - Multiple
Need some assistance. I've had multiple issues with disconnects while gaming and the history of errors listed below is alarming. Need some advice. Connections are tight and secure. No splitters in line. Cox installed coaxial cables. I've done the trouble shooting within the apartment. Sat Nov 23 01:48:43 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received -... Time Not Established Notice (6) Honoring MDD; IP provisioning mode = IPv4 Time Not Established Warning (5) DHCP WARNING - Non-critical field invalid in response ;CM-MA... Mon Nov 25 21:38:42 2019 Notice (6) TLV-11 - unrecognized OID;CM-MAC= ;CMTS-MAC=... Tue Nov 26 15:12:18 2019 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/... Tue Nov 26 15:12:18 2019 Warning (5) MDD message timeout;CM-MAC= ;CMTS-MAC=70:6e:... Tue Nov 26 15:12:21 2019 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/... Tue Nov 26 15:12:22 2019 Warning (5) MDD message timeout;CM-MAC= ;CMTS-MAC=70:6e:... Tue Nov 26 15:12:56 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received -... Tue Nov 26 15:13:00 2019 Critical (3) SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=00... Tue Nov 26 15:15:48 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received -... Tue Nov 26 15:15:48 2019 Critical (3) Unicast Maintenance Ranging attempted - No response - Retrie... Tue Nov 26 15:15:48 2019 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream... Tue Nov 26 15:18:47 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received -... Tue Nov 26 15:18:47 2019 Critical (3) Unicast Maintenance Ranging attempted - No response - Retrie... Tue Nov 26 15:18:47 2019 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream... Tue Nov 26 15:19:07 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received -... Tue Nov 26 15:19:07 2019 Critical (3) Unicast Maintenance Ranging attempted - No response - Retrie... Tue Nov 26 15:19:07 2019 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream... Tue Nov 26 15:28:27 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received -... Tue Nov 26 15:29:09 2019 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=00:40:36:4... Thu Nov 28 07:37:54 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received -... Fri Nov 29 03:43:24 2019 Error (4) DHCP RENEW WARNING - Field invalid in response v4 option;CM-... Sat Nov 30 05:43:25 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received -... Sat Nov 30 05:43:27 2019 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MA... Sat Nov 30 05:44:32 2019 Critical (3) Received Response to Broadcast Maintenance Request, But no U... Sat Nov 30 10:34:19 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received -...678Views0likes1Comment