Forum Discussion
I just came here to complain about the same issue. I had the 300mbps service in Las Vegas, and just downgraded because why bother if I'm getting crappy ping/latency while gaming? If you do a tracert to the destionation IP (in this case, LoL NA is 104.160.131.3), you will notice that things are nice and fast until they hit Cox infrastructure. In this case, it will hit 72.215.224.162 (a Cox internal gateway/load balanced network device) and immediately spike to 60+ms. Example:
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 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
This is because Cox is downright dishonest and is filtering/throttling certain services. Unfortunately they've brokered a monopoly in my area and I can't just cancel them. I'd suggest dropping them and going to Centurylink if you can get their fiber broadband.
- ekhawaii6 years agoContributor
taur...I ran your 104.160.131.3 from SoCal, and got the same jump to 60ms at the 72.215...and the closing 4 hops ranged from 60 to 70ms. Also ran tracert to cox.net....and my hops start locally, to LA, then jumps to Toronto (label in IP). My speed goes from under 15 and jumps to 90ms and stays like that till the end at 45.60.106.167. Cox seems to have some issues.
Related Content
- 7 years ago
- 4 months ago
- 3 months ago
- 10 years ago
- 9 years ago