Latency and Packet Loss Issues
I have noticed latency issues and slight but constant packet loss with PC gaming for many months that varies from obnoxious to making games unplayable. I primarily play CS:GO and PUBG. The network diagnostics in game for PUBG indicate I am having constant 3-10% packet loss on upstream data only, with occasional higher spikes.
Network info: Netgeear CM1000 modem; ASUS AC2900 WiFi router (both purchased December 2018); hardwired connection b/t router and desktop PC.
I contacted COX by phone last month about latency issues. They tried to find my previous COX-rented internet/telephone modem remotely, but had issues finding it. Eventually, I was told the modem was bad and to visit the local COX store for a replacement. Instead of renting the panoramic WiFi, I decided to purchase the setup described above from Amazon. While the home WiFi coverage is far more reliable with the new router, I am still having latency issues and packet loss.
I have not had a tech come out to check the lines yet. One possibility that comes to mind is the sagging cable line between my house and the utility poll. Since I bought the home in 2015, it has been hanging too law in the yard. The wire between the two utility polls behind my house, that looks like it is designed to support the cable line, must have snapped in a storm years ago. I reported the sagging line to COX when I moved in, and they sent someone to look at it. He said there was nothing he could do about it personally, but that he would report it to the line maintenance department at COX and they would come fix it. They never did anything about it, and I didn't follow-up further. I'm wondering if the stress on the line has made the line bad or caused a bad connection at the tap that could explain the issues I'm having.
Any help solving these issues would be greatly appreciated.
Posting my signal strength info and cable modem log info since reset 5 days ago.
Downstream Bonded Channels | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Upstream Bonded Channels | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Downstream OFDM Channels | |||||||||||||||||||||||||||||||||
|
Time | Priority | Description |
2019-01-29, 07:30:35 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-QOS=1.1;CM-VER=3.1; |
2019-01-28, 17:30:13 | Notice (6) | CM-STATUS message sent. Event Type Code: 3; Chan ID: N/A; DSID: �; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-QOS=1.1;CM-VER=3.1; |
2019-01-28, 17:30:13 | Warning (5) | Unicast DSID PSN startup error |
2019-01-28, 17:29:43 | Critical (3) | No Ranging Response received - T3 time-out;CM-QOS=1.1;CM-VER=3.1; |
2019-01-28, 17:29:33 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-QOS=1.1;CM-VER=3.1; |
2019-01-28, 17:29:32 | Critical (3) | No Ranging Response received - T3 time-out;CM-QOS=1.1;CM-VER=3.1; |
2019-01-28, 17:29:31 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-QOS=1.1;CM-VER=3.1; |
2019-01-28, 17:29:31 | Critical (3) | No Ranging Response received - T3 time-out;CM-QOS=1.1;CM-VER=3.1; |
2019-01-28, 17:29:30 | Warning (5) | Dynamic Range Window violation |
2019-01-28, 17:29:30 | Warning (5) | RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-QOS=1.1;CM-VER=3.1; |
2019-01-28, 17:29:30 | Warning (5) | Dynamic Range Window violation |
2019-01-28, 17:29:30 | Warning (5) | RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-QOS=1.1;CM-VER=3.1; |
2019-01-28, 17:29:29 | Critical (3) | No Ranging Response received - T3 time-out;CM-QOS=1.1;CM-VER=3.1; |
2019-01-28, 17:29:29 | Warning (5) | Dynamic Range Window violation |
2019-01-28, 17:29:29 | Warning (5) | RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-QOS=1.1;CM-VER=3.1; |
2019-01-28, 17:29:29 | Warning (5) | Dynamic Range Window violation |
2019-01-28, 17:29:29 | Warning (5) | RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-QOS=1.1;CM-VER=3.1; |
2019-01-28, 17:29:29 | Warning (5) | Dynamic Range Window violation |
2019-01-28, 17:29:29 | Warning (5) | RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-QOS=1.1;CM-VER=3.1; |
2019-01-28, 17:29:19 | Notice (6) | DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3 .;CM-VER=3.1; |
2019-01-28, 17:29:10 | Notice (6) | TLV-11 - unrecognized OID;CM-QOS=1.1;CM-VER=3.1; |
Time Not Established | Warning (5) | DHCP WARNING - Non-critical field invalid in response ;CM-QOS=1.1;CM-VER=3.1; |
Time Not Established | Critical (3) | DHCP FAILED - Request sent, No response;CM-QOS=1.1;CM-VER=3.1; |
Time Not Established | Notice (6) | Honoring MDD; IP provisioning mode = IPv4 |
Time Not Established | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-QOS=1.1;CM-VER=3.1; |
Time Not Established | Critical (3) | No Ranging Response received - T3 time-out;CM-QOS=1.1;CM-VER=3.1; |
Time Not Established | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-QOS=1.1;CM-VER=3.1; |
2019-01-24, 07:52:40 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-QOS=1.1;CM-VER=3.1; |
2019-01-24, 03:27:30 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-QOS=1.1;CM-VER=3.1; |
2019-01-24, 03:27:22 | Critical (3) | Unicast Ranging Received Abort Response - Re-initializing MAC;CM-QOS=1.1;CM-VER=3.1; |
2019-01-24, 03:27:22 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-QOS=1.1;CM-VER=3.1; |
2019-01-24, 03:27:11 | Critical (3) | Unicast Ranging Received Abort Response - Re-initializing MAC;CM-QOS=1.1;CM-VER=3.1; |
2019-01-24, 03:27:11 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-QOS=1.1;CM-VER=3.1; |
2019-01-24, 03:27:03 | Critical (3) | Unicast Ranging Received Abort Response - Re-initializing MAC;CM-QOS=1.1;CM-VER=3.1; |
2019-01-24, 03:27:01 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-QOS=1.1;CM-VER=3.1; |
2019-01-24, 03:26:52 | Critical (3) | Unicast Ranging Received Abort Response - Re-initializing MAC;CM-QOS=1.1;CM-VER=3.1; |
2019-01-24, 03:26:51 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-QOS=1.1;CM-VER=3.1; |
2019-01-24, 03:26:31 | Critical (3) | Unicast Ranging Received Abort Response - Re-initializing MAC;CM-QOS=1.1;CM-VER=3.1; |
2019-01-24, 03:26:31 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-QOS=1.1;CM-VER=3.1; |
2019-01-24, 03:01:36 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-QOS=1.1;CM-VER=3.1; |