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
TRACEROUTE ISSUES WORKING FROM HOME PLEASE HELP!!
I recently started working remote from home. I have to connect to my companies remote server on my pc at home. I work most of my day talking on the phone through the remote server with clients. I am having issues where my voice on the phone is choppy and clients cannot hear me. I contacted my tech team at work and they ran at tracert test and said one of my hops is timing out. they said to contact my ISP which is COX to fix this but no one at COX seems to be able to know how to fix this issue when I call. I even had a tech come out to look at it. does anyone know how to fix this issue? please help! this is how the traceroute is coming back as. as you can line 6 and 7 are timing out. C:\Users\AmeriSave>tracert remote8.amerisave.com Tracing route to remote8.amerisave.com [70.42.180.69] over a maximum of 30 hops: 1 1 ms 1 ms 1 ms 192.168.0.1 2 9 ms 8 ms 7 ms 10.35.48.1 3 12 ms 15 ms 13 ms 100.127.73.138 4 10 ms 11 ms 15 ms 100.120.100.10 5 25 ms 27 ms 19 ms 68.1.4.252 6 * * * Request timed out. 7 * * * Request timed out. 8 109 ms 87 ms 86 ms ae12.cs2.dfw2.us.zip.zayo.com [64.125.26.182] 9 81 ms 89 ms 83 ms ae5.cs2.iah1.us.eth.zayo.com [64.125.28.102] 10 * 82 ms * ae28.cs1.atl10.us.zip.zayo.com [64.125.31.171] 11 81 ms 85 ms 80 ms ae6.mpr3.atl6.us.zip.zayo.com [64.125.31.33] 12 82 ms 80 ms 94 ms 128.177.70.66.IPYX-072053-009-ZYO.zip.zayo.com [128.177.70.66] 13 73 ms 65 ms 65 ms border2.ae2-bbnet2.acs.pnap.net [64.94.0.93] 14 67 ms 65 ms 70 ms edge2.ae1-edgenet.acs002.pnap.net [107.150.129.34] 15 65 ms 71 ms 68 ms amerisave-5.edge2.acs002.pnap.net [70.42.176.126] 16 66 ms 77 ms 65 ms 70.42.180.69 Trace complete.
Crazy Lag and Packet Loss
Hoping to get more help here than I did with Cox customer support. I have had this ISP for about 2 months now and my connection has been horrible. Things load fine on wifi for the most part butanytime I am hardwired into my router, I have horrible packet loss. This makes gaming a huge pain in the **** and I have tried almost everything I can think of to fix it but nothing changes. Now, Xbox live and the games I play like to report that I am getting maybe about 1% packet loss but the gameplay is much much worse than just 1%. Even when I hardwire my computer into the router and run a ping test, it shows about 15-20% packet loss. Does anyone have any suggestions that I should try? Here is a list of things I have already tried: Used Cox provided modem/router: terrible packet loss on ethernet and wifi (mostly ethernet) Modem isfor sureplugged into the coax port very securely Changed ethernet ports:issue still persists Set up Xbox live port forwarding:issue still persists Setup QoS:issue still persists Tried entirely new ethernet cables:issue still persists Tried gaming on wifi:issue still persists (and I am not a heathen) Factory reset modem/router:issue still persists Switched the provided router/modem combo intobridge modeso it only acts like a modem I am now using my TP-Link AC1750 router:still terrible packet loss on wifi and ethernet (mostly ethernet) Set up QoS rules for bandwidth:issue still persists Setup port forwarding:issue still persists Reset xbox:issue still persists Manually set IP and DNS:issue still persists I have also ran a bunch of traceroute tests as well as ping tests to show where it appears to be slowing down and losing the packets. You can see all of these tests in the folder linked here: https://drive.google.com/drive/folders/1i59D5DTk2O7UvL0WBrqJYVITDr305hvT?usp=sharing All the slowdowns and packet losses appear to happenoutside of my network. It looks like it hits slowdowns when it is out in Cox's servers bouncing around. Is there anything that I can do to fix this? It looks like there is an issue with resolution of domains. My traceroutes to 8.8.8.8 show an unusual amount of dropped packets and lag at certain servers. PLEASE HELP!!Discord app and xbox live service blocked across all devices running on COX.
A few days ago DIscord and xbox live have been unable to connect. No local filtering for these websites on my router or firewall, seems to be blocked at COX servers.I already went through online support and was not help. NOTE: all other websites work on my network just not xbox live and discord.
Cox throttling speeds to gaming servers? I think so.
So I've just had it with Cox and their seemingly dishonest practice of blaming everything on the customer... I just got the 300mbps service in Las Vegas, and suspiciously get 500% increases in ping to gaming services as opposed to standard browsing/streaming service. I've validated everything is good to go on my end, and spent an hour or more being treated like a fool with Cox "technical support" people who don't even know what ping or traceroute are. As a background I've worked in IT for 15+ years and manage large load balanced networks like this for a living... Either there is an immense amount of ineptitude and apathy going on, or they're trying to push gamers to spend more money. My modem is a DOCSIS 3.1 enabled modem. My router is a gigabit router. I'm wired into the router with CAT6 cable, directly. My connection to the COX gateway is fast, and fine. The issue is the Cox internal routing. In this case, I'm going to use League of Legends for an example since they post their server IPs publicly. All I need to do to show where the breakdown is occurring is run a simple tracert. It's clear that I'm getting solid ping to Cox's gateway - langbprj01-ae1.rd.la.cox.net [68.1.1.13] - but they're choosing to route gaming traffic specifically through some kind of WAF, concentrator, or other type of internal network device which is throttling all traffic to 60-70ms (at lowest) The glaring technical evidence: Tracing route to 104.160.131.3 over a maximum of 30 hops 1 <1 ms <1 ms <1 ms 192.168.1.1 2 9 ms 8 ms 7 ms 10.67.0.1 3 8 ms 8 ms 7 ms 100.127.4.164 4 11 ms 7 ms 11 ms 100.120.102.24 5 15 ms 16 ms 12 ms langbprj01-ae1.rd.la.cox.net [68.1.1.13] 6 60 ms 61 ms 61 ms 72.215.224.162 <---- the offending Cox IP. 7 61 ms 67 ms 65 ms 104.160.152.223 8 62 ms 61 ms 60 ms 104.160.152.227 9 67 ms 70 ms 70 ms 104.160.159.100 10 68 ms 67 ms 68 ms 104.160.131.3 So why are they throttling gaming speeds to 60-70ms? It doesn't really make sense until you realize they've just started marketing their "Cox Elite Gaming" service to unlock higher speeds for a premium monthly rate. The only problem? I CAN'T EVEN BUY THEIR EXTRA SERVICE IN MY AREA. Come on! If you're going to scam me into buying a premium service, at least offer the option to buy it! My only option has been to reduce my service to the 150mgps service (why bother with bandwidth if it's slow), and subscribe to Haste for a slight ping boost to try and compensate. Note - COX - you're losing money here. In the end I'm just getting screwed, and Cox is showing how dishonest they are. If they could explain exactly what that IP is and why they refuse to address it internally, maybe it will matter. Until then I'll be planning my exit ASAP.
Tracert questions
I was receiving packet loss in a video game and several people suggested a tracert, can someone please tell me if anything is out of the ordinary? C:\Users\petti>tracert cox.com Tracing route to cox.com [45.60.49.167] over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms 192.168.1.1 2 128 ms 23 ms 14 ms 10.128.92.1 3 51 ms 29 ms 19 ms 100.127.76.40 4 53 ms 49 ms 98 ms 100.120.100.24 5 639 ms 598 ms 697 ms lag-103.bear2.Phoenix1.Level3.net [4.14.52.225] 6 37 ms * * ae-1-3512.ear4.LosAngeles1.Level3.net [4.69.211.210] 7 23 ms 23 ms 47 ms 4.7.26.34 8 33 ms 24 ms 54 ms 45.60.49.167 Trace complete. C:\Users\petti>tracert cox.com Tracing route to cox.com [45.60.49.167] over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms 192.168.1.1 2 12 ms 10 ms 44 ms 10.128.92.1 3 44 ms 125 ms 11 ms 100.127.76.40 4 36 ms 71 ms 138 ms 100.120.100.24 5 * 742 ms 699 ms lag-103.bear2.Phoenix1.Level3.net [4.14.52.225] 6 * * * Request timed out. 7 21 ms 21 ms 22 ms 4.7.26.34 8 35 ms 17 ms 46 ms 45.60.49.167 Trace complete. C:\Users\petti>tracert cox.com Tracing route to cox.com [45.60.49.167] over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms 192.168.1.1 2 31 ms 8 ms 9 ms 10.128.92.1 3 12 ms 13 ms 16 ms 100.127.76.40 4 23 ms 7 ms 15 ms 100.120.100.24 5 * 1046 ms 797 ms lag-103.bear2.Phoenix1.Level3.net [4.14.52.225] 6 * * * Request timed out. 7 30 ms 20 ms 20 ms 4.7.26.34 8 43 ms 22 ms 21 ms 45.60.49.167 Trace complete. C:\Users\petti>tracert cox.com Tracing route to cox.com [45.60.49.167] over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms 192.168.1.1 2 34 ms 13 ms * 10.128.92.1 3 31 ms 8 ms 68 ms 100.127.76.40 4 61 ms 14 ms 42 ms 100.120.100.24 5 737 ms 799 ms 699 ms lag-103.bear2.Phoenix1.Level3.net [4.14.52.225] 6 * * * Request timed out. 7 90 ms 27 ms 117 ms 4.7.26.34 8 23 ms 78 ms 43 ms 45.60.49.167 Trace complete.
