Cox → [AR] Latency gradually getting worse, why?

A year ago my normal ping on the cox speed test was 28-35, now it's in the 70's and it's been slowly climbing there. What is the deal? I'm not exactly sure of the best way to test the situation, but I've pasted in my speed test log from the cox website. This is making the games etc. that I play slowly worse and worse. What's going on cox?

Tue Jan 27 08:17 PM Yes 126 Mbps 12 Mbps 73 millisec Kansas
Fri Jan 23 09:26 PM Yes 126 Mbps 12 Mbps 74 millisec Kansas
Fri Jan 23 09:18 PM Yes 128 Mbps 12 Mbps 71 millisec Kansas
Fri Jan 23 09:17 PM Yes 129 Mbps 11 Mbps 68 millisec Kansas
Tue Jan 06 07:29 PM Yes 110 Mbps 15 Mbps 75 millisec Kansas
Tue Jan 06 07:28 PM Yes 124 Mbps 12 Mbps 71 millisec Kansas
Sat Dec 06 03:28 PM Yes 130 Mbps 11 Mbps 52 millisec Kansas
Thu Dec 04 09:58 PM Yes 86 Mbps 16 Mbps 53 millisec Kansas
Wed Dec 03 11:46 PM Yes 106 Mbps 15 Mbps 59 millisec Kansas
Sun Nov 30 04:21 PM Yes 128 Mbps 12 Mbps 59 millisec Kansas
Tue Nov 25 09:36 PM Yes 127 Mbps 13 Mbps 61 millisec Kansas
Tue Nov 25 09:35 PM Yes 55 Mbps 18 Mbps 52 millisec Kansas
Wed Oct 08 09:42 PM Yes 130 Mbps 18 Mbps 51 millisec Kansas
Thu Sep 11 10:52 PM Yes 118 Mbps 21 Mbps 52 millisec Kansas
Thu Sep 11 08:26 PM Yes 13 Mbps 20 Mbps 52 millisec Kansas
Thu Sep 11 08:22 PM Yes 13 Mbps 32 Mbps 55 millisec Kansas
Thu Sep 11 08:00 PM Yes 16 Mbps 27 Mbps 52 millisec Kansas
Thu Sep 11 07:57 PM Yes 18 Mbps 1 Mbps 53 millisec Kansas
Thu Aug 28 10:28 PM Yes 123 Mbps 18 Mbps 49 millisec Kansas
Thu Aug 07 09:45 PM Yes 119 Mbps 21 Mbps 51 millisec Kansas
Sun Jun 22 11:22 AM Yes 65 Mbps 21 Mbps 45 millisec Kansas
Fri Jun 06 10:59 PM Yes 65 Mbps 22 Mbps 50 millisec Kansas
Sun Jun 01 03:04 PM Yes 65 Mbps 21 Mbps 51 millisec Kansas
Sat May 24 07:14 PM Yes 62 Mbps 22 Mbps 50 millisec Kansas
Sat May 24 07:14 PM Yes 64 Mbps 21 Mbps 48 millisec Kansas

I believe Cox changed alot of the speedtest servers about a month or so again, but some servers where probably changed after that. Thats why some people can't even run the test, like me. Either way, the latency is just to give you a general idea how far away the server is your testing, as well as show any general latency problems. It doesn't say anything about the latency between you and a matchmaking game server or another player. For that, you would want to do a tracert. Here is a example of how to do a Tracert for WoW, but you can just replace any server in place of the WoW servers to check your latency.

»us.battle.net/support/en ··· aceroute

Right now it's so slow we can barely access Cox site at all. Mostly times out.
Started slowing down drastically late last night\early this morn.

We're presently near Rogers area... anyone else noticing this?

It's fine for me in Fayetteville. Pings using Cox's speed tool are about 45ms, pings to 8.8.8.8 are about 30ms. Pinging a few other major services also result in ~35ms. Have you tried pinging anything other than via Cox's speed test?

Howdy Maltz, thanks for the reply

Just confirmed there are issues here [in this area] but no specifics on what they are.
Cox claims they should be resolved by 17:00 hours today. Probably not effecting you there.

Thanks again!

Now they're all like this:

Tracing route to ns1.ph.cox.net [68.2.16.30]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.1.1
2 * * * Request timed out.
3 10 ms 10 ms 8 ms wsip-70-182-122-6.ks.ks.cox.net [70.182.122.6]
4 10 ms 10 ms 10 ms wsip-70-182-122-46.ks.ks.cox.net [70.182.122.46]
5 20 ms 20 ms 22 ms wsip-70-182-120-164.ks.ks.cox.net [70.182.120.164]
6 20 ms 20 ms 20 ms 70.183.71.84
7 23 ms 23 ms 21 ms 70.183.71.60
8 53 ms 55 ms 53 ms chndbbrj02-so100.0.rd.ph.cox.net [68.1.0.173]
9 54 ms 54 ms 55 ms ns1.ph.cox.net [68.2.16.30]

Trace complete.

Here is my trace to wwww.cox.net... there are some pretty serious jumps in latency. From 4 to 5 the ping almost triples and from 6 to 7 it more than doubles....and at #9 there is 50% PL.

Target Name: www.cox.net
IP: 68.99.123.161
Date/Time: 2/9/2015 9:13:34 PM to 2/9/2015 9:15:49 PM

1 0 ms 0 ms 0 ms 0 ms 0 ms 0 ms 0 ms 0 ms 0 ms 0 ms [192.168.1.1]
2 6 ms 6 ms 10 ms 6 ms 6 ms 7 ms 6 ms 7 ms 7 ms 8 ms [10.50.0.1]
3 7 ms 7 ms 9 ms 7 ms 10 ms 8 ms 19 ms 8 ms 7 ms 7 ms [70.183.68.70]
4 7 ms 9 ms 7 ms 7 ms 8 ms 6 ms 8 ms 9 ms 8 ms 20 ms wsip-70-182-122-46.ks.ks.cox.net [70.182.122.46]
5 18 ms 37 ms 17 ms 17 ms 17 ms 18 ms 18 ms 24 ms 17 ms 17 ms wsip-70-182-120-164.ks.ks.cox.net [70.182.120.164]
6 18 ms 17 ms 19 ms 27 ms 17 ms 19 ms 21 ms 19 ms 18 ms 21 ms [70.183.71.84]
7 48 ms 48 ms 50 ms 48 ms 48 ms 49 ms 50 ms 51 ms 48 ms 56 ms dukedsrj01-ae4.0.rd.at.cox.net [68.1.1.121]
8 58 ms 51 ms 50 ms 53 ms 48 ms 48 ms 50 ms 49 ms 49 ms 48 ms [68.1.15.234]
9 48 ms * 50 ms * 49 ms * 49 ms * 59 ms * [68.99.123.4]
10 49 ms 49 ms 51 ms 49 ms 48 ms 50 ms 48 ms 49 ms 50 ms 48 ms ww2.cox.com [68.99.123.161]

Ping statistics for www.cox.net
Packets: Sent = 10, Received = 10, Lost = 0 (0.0%)
Round Trip Times: Minimum = 48ms, Maximum = 51ms, Average = 49ms

The way a trace route works, the ping time displayed in each row is cumulative. So ping time in row 5 is about double row four, but it includes the ~8ms from row 4. The additional ~10ms probably just shows that the geographic distance from wsip-70-182-122-46.ks.ks.cox.net to wsip-70-182-120-164.ks.ks.cox.net larger than some of the other connections.

That trace route very closely matches mine and looks normal to me.