Quote Originally Posted by Laraul View Post
Several posts we're from people in AZ, including the original poster. It is not limited to just people in California.


I pinged my server, which is 204.2.229.103. I assume 204.2.229.9 is the pinger's server. I don't know for certain

I was simply trying to say that the problem is likely an issue local to the user. If you are experiencing frequent disconnects and/or lag spikes over a number of days, call Cox and have them come out and do a line test. Try also checking your modem's web management server (if it has one). I believe it's usually found by typing "http://192.168.100.1" into a web browser. Lastly you can always reboot/reset/replace your router (if possible). Most people have already tried some of these already.

The last time I was experiencing frequent disconnects and lag spikes, it turned out that line that runs to my block was mauled on by some animal. And it wasn't discovered until they did a visual line check of the line. This was causing a dip in line signal power resulting in a poor connection. It took them two or three days to find and repair it.
Just to add what the others have already said, please don't do this, it is not good advice and shows a fundamental lack of understanding how to read trace route results.

The trace routes being posted here clearly show issues after the peering hand-off to NTT. If this was an ISP or last mile issue, you would see high latency and/or packet loss the first couple of hops.


With that said, just want to add supporting evidence that it clearly looks to be a capacity issue with NTT during peak hours. I had the opportunity to play some this morning PT, off peak, and saw no issues and my trace route is totally clean:




Compared to last night where issues start to ramp up around 6pm PT, and then hit unplayable levels around 7:30PM PT: