Read the forum guidelines
Intermittent latency spikes have disrupted my ability to game, so I have resorted to adding a Centurylink DSL line just for gaming. The line is slow from a download and upload perspective, but the latency is very consistent, which makes gaming possible. I would like to know if Cox would be willing to reimburse me the $50 a month that I have to pay Centurylink since Cox is unable to provide consitent latency. The issue typically occurs at my first hop which is 10.36.72.1. I use pingplotter so I can see the latency and packet loss carrying through on the traceroute to just about any server I ping.
https://www.photobox.co.uk/my/photo?album_id=5797736786&photo_id=502610138270
Here is a pingplotter scan
You've got to be kidding me. You run an internet company and you cant even view the contents of a link. I just opened the link to make sure it was still working, and it's fine. You guys are hilarious.
@Drmsand100 The referenced website can't be viewed by other people because it requires permission. The following is displayed when the link is clicked.
https://drive.google.com/open?id=1qUTkcSAB6SOqC-1TO-Mf7QAg5t6TJMWl
How about this?
https://drive.google.com/open?id=1yMTLRG29dRWXlhuypF6fjzJpnLlWPfun
Here is what my ping looks like often early in the morning. The fact that I can get low jitter at times suggests that the problem is not local to my equipment, or another local source, etc.
It is likely that the extreme jitter I experience, which can almost shut down my data flow at times, is related to congestion interacting with insufficient or faulty COX hardware.
My current setup includes both a modem and router. I have an Araknis router and a SB8200 (Arris) modem. I will bypass the router and connect directly to the modem, then I will run another pingplotter. BTW. I have done this myself many times and the results are the same.
As far as the gaming server being the final hop, I can also do that, but it makes no difference, I use the open DNS server address 1.1.1.1 because it is extremely reliable from an ICMP echo standpoint. You will get a more accurate picture of your network issues using this as the final hop on the trace.
I can do this later this evening and submit another image link.
Also, if you are referring to the address that I provided, 10.36.72.1 is the ip address for your CMTS. That's your equipment, not mine. You know this, right?