Packet Loss Again
I had this problem before and it took me almost 3 months of calling corporate and filing an FCC to finally be free of this issue. The problem seems to have come back though its been like a week of me having random moments throughout the day of having nonstop packet loss. I have called Cox Support again and they are sending a technician out tomorrow but just to be sure I would like to eliminate any possibility of this being an issue in the home that I can fix myself. The last time every technician that came out could find no problems with the connection in my home but always found issue with the pole outside. I really hope this isn't the case again because I've only had good internet for maybe a month of no packet loss. Is there a way for them to just nonstop monitor my connection because when I call support during my times of packetloss when they do their ping test my packet loss may resolve itself during the call and then suddenly start back up again once I'm off the phone with them. C:\WINDOWS\system32>tracert -4 cox.com Tracing route to cox.com [45.60.45.167] over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms 192.168.0.1 2 22 ms 23 ms * 10.131.152.1 3 10 ms 6 ms 7 ms 100.122.142.184 4 * * 21 ms 100.122.141.68 5 23 ms 20 ms 19 ms dalsbbrj02-ae3.0.rd.dl.cox.net [68.1.5.134] 6 * * 20 ms dls-b23-link.ip.twelve99.net [62.115.14.38] 7 * * * Request timed out. 8 * * * Request timed out. 9 * * * Request timed out. 10 * * 21 ms 45.60.45.167 Trace complete. C:\WINDOWS\system32>tracert -4 cox.com Tracing route to cox.com [45.60.45.167] over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms 192.168.0.1 2 8 ms * 9 ms 10.131.152.1 3 11 ms * 9 ms 100.122.142.184 4 * * 10 ms 100.122.141.68 5 24 ms * 20 ms dalsbbrj02-ae3.0.rd.dl.cox.net [68.1.5.134] 6 35 ms * 20 ms dls-b23-link.ip.twelve99.net [62.115.14.38] 7 19 ms * * lag-14.ear5.Dallas1.Level3.net [4.68.74.165] 8 * * * Request timed out. 9 34 ms 20 ms 20 ms 4.14.131.250 10 * 21 ms 22 ms 45.60.45.167 Trace complete. C:\WINDOWS\system32>tracert -4 google.com Tracing route to google.com [172.217.14.174] over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms 192.168.0.1 2 * * * Request timed out. 3 23 ms 7 ms 8 ms 100.122.142.184 4 16 ms 9 ms 9 ms 100.122.141.68 5 * * * Request timed out. 6 * * 17 ms 72.14.223.220 7 24 ms 20 ms 22 ms 209.85.245.181 8 19 ms 19 ms 18 ms 72.14.236.139 9 * 23 ms 33 ms dfw28s22-in-f14.1e100.net [172.217.14.174] Trace complete. C:\WINDOWS\system32>ping -l 600 -n 100 google.com Pinging google.com [2607:f8b0:4000:805::200e] with 600 bytes of data: Reply from 2607:f8b0:4000:805::200e: time=30ms Request timed out. Reply from 2607:f8b0:4000:805::200e: time=29ms Request timed out. Reply from 2607:f8b0:4000:805::200e: time=21ms Reply from 2607:f8b0:4000:805::200e: time=21ms Reply from 2607:f8b0:4000:805::200e: time=19ms Reply from 2607:f8b0:4000:805::200e: time=19ms Reply from 2607:f8b0:4000:805::200e: time=19ms Reply from 2607:f8b0:4000:805::200e: time=21ms Request timed out. Request timed out. Reply from 2607:f8b0:4000:805::200e: time=38ms Reply from 2607:f8b0:4000:805::200e: time=20ms Request timed out. Request timed out. Reply from 2607:f8b0:4000:805::200e: time=36ms Reply from 2607:f8b0:4000:805::200e: time=20ms Request timed out. Reply from 2607:f8b0:4000:805::200e: time=19ms Request timed out. Request timed out. Request timed out. Request timed out. Reply from 2607:f8b0:4000:805::200e: time=40ms Request timed out. Reply from 2607:f8b0:4000:805::200e: time=20ms Request timed out. Request timed out. Reply from 2607:f8b0:4000:805::200e: time=38ms Reply from 2607:f8b0:4000:805::200e: time=42ms Reply from 2607:f8b0:4000:805::200e: time=22ms Request timed out. Reply from 2607:f8b0:4000:805::200e: time=32ms Reply from 2607:f8b0:4000:805::200e: time=19ms Request timed out. Reply from 2607:f8b0:4000:805::200e: time=34ms Reply from 2607:f8b0:4000:805::200e: time=27ms Reply from 2607:f8b0:4000:805::200e: time=29ms Reply from 2607:f8b0:4000:805::200e: time=19ms Reply from 2607:f8b0:4000:805::200e: time=21ms Request timed out. Reply from 2607:f8b0:4000:805::200e: time=21ms Reply from 2607:f8b0:4000:805::200e: time=22ms Reply from 2607:f8b0:4000:805::200e: time=21ms Reply from 2607:f8b0:4000:805::200e: time=19ms Reply from 2607:f8b0:4000:805::200e: time=21ms Reply from 2607:f8b0:4000:805::200e: time=39ms Reply from 2607:f8b0:4000:805::200e: time=19ms Reply from 2607:f8b0:4000:805::200e: time=21ms Reply from 2607:f8b0:4000:805::200e: time=24ms Request timed out. Reply from 2607:f8b0:4000:805::200e: time=20ms Reply from 2607:f8b0:4000:805::200e: time=26ms Reply from 2607:f8b0:4000:805::200e: time=19ms Reply from 2607:f8b0:4000:805::200e: time=40ms Reply from 2607:f8b0:4000:805::200e: time=27ms Reply from 2607:f8b0:4000:805::200e: time=23ms Reply from 2607:f8b0:4000:805::200e: time=19ms Reply from 2607:f8b0:4000:805::200e: time=19ms Reply from 2607:f8b0:4000:805::200e: time=19ms Reply from 2607:f8b0:4000:805::200e: time=19ms Request timed out. Reply from 2607:f8b0:4000:805::200e: time=19ms Reply from 2607:f8b0:4000:805::200e: time=20ms Request timed out. Request timed out. Reply from 2607:f8b0:4000:805::200e: time=25ms Reply from 2607:f8b0:4000:805::200e: time=27ms Reply from 2607:f8b0:4000:805::200e: time=19ms Request timed out. Request timed out. Request timed out. Request timed out. Request timed out. Reply from 2607:f8b0:4000:805::200e: time=60ms Reply from 2607:f8b0:4000:805::200e: time=35ms Request timed out. Request timed out. Request timed out. Request timed out. Reply from 2607:f8b0:4000:805::200e: time=40ms Request timed out. Reply from 2607:f8b0:4000:805::200e: time=25ms Request timed out. Reply from 2607:f8b0:4000:805::200e: time=33ms Request timed out. Request timed out. Reply from 2607:f8b0:4000:805::200e: time=19ms Request timed out. Request timed out. Reply from 2607:f8b0:4000:805::200e: time=22ms Request timed out. Request timed out. Reply from 2607:f8b0:4000:805::200e: time=45ms Reply from 2607:f8b0:4000:805::200e: time=19ms Reply from 2607:f8b0:4000:805::200e: time=22ms Reply from 2607:f8b0:4000:805::200e: time=19ms Reply from 2607:f8b0:4000:805::200e: time=18ms Reply from 2607:f8b0:4000:805::200e: time=25ms Ping statistics for 2607:f8b0:4000:805::200e: Packets: Sent = 100, Received = 62, Lost = 38 (38% loss), Approximate round trip times in milli-seconds: Minimum = 18ms, Maximum = 60ms, Average = 25ms Downstream Channel Bonding Value Index 13 1 2 3 4 5 6 7 8 9 10 11 12 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 159 Lock Status Locked Locked Locked Locked Locked Locked Locked Locked Locked Locked Locked Locked Locked Locked Locked Locked Locked Locked Locked Locked Locked Locked Locked Locked Locked Locked Locked Locked Locked Locked Locked Locked Locked Frequency 753 MHz 681 MHz 687 MHz 693 MHz 699 MHz 705 MHz 711 MHz 717 MHz 723 MHz 729 MHz 735 MHz 741 MHz 747 MHz 759 MHz 765 MHz 771 MHz 777 MHz 783 MHz 789 MHz 795 MHz 801 MHz 807 MHz 813 MHz 819 MHz 825 MHz 831 MHz 837 MHz 843 MHz 849 MHz 855 MHz 861 MHz 867 MHz 300000000 SNR 36.3 dB 36.6 dB 36.9 dB 37.2 dB 37.4 dB 37.3 dB 37.0 dB 36.9 dB 36.6 dB 36.5 dB 36.5 dB 36.4 dB 36.4 dB 36.3 dB 36.5 dB 36.9 dB 37.0 dB 36.9 dB 36.9 dB 36.5 dB 36.4 dB 36.2 dB 36.0 dB 35.8 dB 36.0 dB 35.9 dB 35.1 dB 34.4 dB 34.0 dB 34.3 dB 34.9 dB 35.3 dB NA Power Level 4.1 dBmV 6.1 dBmV 6.4 dBmV 6.7 dBmV 6.6 dBmV 6.1 dBmV 5.4 dBmV 4.9 dBmV 4.7 dBmV 4.6 dBmV 4.4 dBmV 4.4 dBmV 4.3 dBmV 4.2 dBmV 4.6 dBmV 5.1 dBmV 5.3 dBmV 5.1 dBmV 4.9 dBmV 4.5 dBmV 4.3 dBmV 3.8 dBmV 3.3 dBmV 2.8 dBmV 2.6 dBmV 2.6 dBmV 1.7 dBmV 0.6 dBmV 0.1 dBmV 0.2 dBmV 0.5 dBmV 1.1 dBmV NA Modulation 256 QAM 256 QAM 256 QAM 256 QAM 256 QAM 256 QAM 256 QAM 256 QAM 256 QAM 256 QAM 256 QAM 256 QAM 256 QAM 256 QAM 256 QAM 256 QAM 256 QAM 256 QAM 256 QAM 256 QAM 256 QAM 256 QAM 256 QAM 256 QAM 256 QAM 256 QAM 256 QAM 256 QAM 256 QAM 256 QAM 256 QAM 256 QAM OFDM Upstream Channel Bonding Value Index 1 2 3 Lock Status Locked Locked Locked Frequency 36 MHz 30 MHz 24 MHz Symbol Rate 5120 5120 5120 Power Level 36.3 dBmV 35.8 dBmV 35.3 dBmV Modulation QAM QAM QAM Channel Type ATDMA ATDMA ATDMA CM Error Codewords Index 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 Unerrored Codewords 843388334 837477272 837492640 837510576 837525335 837529535 837529697 837531674 837521541 837524437 837530820 837538285 837545292 837554646 837574886 837592965 837598977 837602471 837608285 837605096 837603688 837597588 837592573 837609615 837637990 837652262 837620427 837560831 837535769 837595857 837652945 837679205 843388334 Correctable Codewords 263703742 50917 42949 31407 23753 26376 32789 37652 53576 58533 62665 61864 61600 58696 45141 33117 33346 35833 37593 47553 55253 68146 79428 68322 47007 38079 76375 142494 173648 120227 63525 42067 263703742 Uncorrectable Codewords 10139 6738 6570 6626 6398 6274 6328 6352 6185 6350 6217 6123 6206 6242 6269 6282 6241 6286 6174 6289 6353 6311 6438 6329 6268 6163 6264 6331 6364 6423 6539 6356 10139
Packet Loss in Las Vegas (89178)
Experiencing packet loss in Las Vegas of 1-2% during the evening, and during some days. Appears to correlate with when more people are at home (after 5pm and weekends). This is affecting others in the neighborhood as well. How can we get someone to look at this at the neighborhood level? https://imgur.com/CJhSRSZhttps://imgur.com/tfPGcAV