To keep a 9month long story short, I have been having issues routing to RIOT games. Having spoken to people both at Riot, and Cox, including T2, T2.5 and Noc Engineering (specifically the team working on peering with Riot Games back last summer). The consensus at this point in time, is that I have the best possible routing to Riot, and Riot Noc Engineering is telling me, that they are not having any issues, and that my issue is with Cox.
I have not seen any reports from other Cox customers, complaining about my issue, which is making me think it is more specific to my node.
If anyone is able to copy paste the following line, into command prompt, I would appreciate the tracert results.
(tracert 104.160.131.1) > "%USERPROFILE%\desktop\Tracert.txt"
This will save the tracert as a txt document named Tracert.txt on your desktop.
I think the CMTS that I am connected to is suspect, I have had anywhere from 5-200ms ping to it, depending on mood. (Time of day didn't seem to matter). However, I have no longer been able to ping the CMTS during a tracert, for the past 2-3months.
I am in the process of once again working with T2.5, having some proof that The rest of Phoenix is not having issues, will help me in resolving this problem. My final step is to submit a FCC complaint, but I need as much information as possible.
I already have Tracert's from other ISP's in Arizona, and Cox is the last that I need, since I cannot trust my tracert since I think the CMTS is suspect.
Thank you for your time,
Please don't hesitate to ask me any questions.
↧