Crazy Trace Route to cox.net

"I have pinged my IP directly and my time is < 1ms"

What do you mean exactly? What happens if you ping 192.168.100.1? If you see high latency there, problem is between PC and modem. If you don't, then problem is between modem and Cox. 

What are you modem signal levels? Any disconnects or reboots needed?

Not that I have any idea what is good  or bad, but from the signal page of my cable modem:

Signal to Noise ratio is 36 or 37 dB

Power Level 4 dBmV

C:\>ping 192.168.100.1

Pinging 192.168.100.1 with 32 bytes of data:
Reply from 192.168.100.1: bytes=32 time=1ms TTL=64
Reply from 192.168.100.1: bytes=32 time=1ms TTL=64
Reply from 192.168.100.1: bytes=32 time<1ms TTL=64
Reply from 192.168.100.1: bytes=32 time=1ms TTL=64

Ping statistics for 192.168.100.1:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 1ms, Average = 0ms

I figured pinging my IP was the same as pinging 192.168.100.1

Jimbo1234 said:
I figured pinging my IP was the same as pinging 192.168.100.1

Sometimes. If your batch files redirects, or if your router has loop back, then its the same. My guess is something going on in the area. Looks like something was happening like this before and it was fixed by Cox re-provisioning the modem? Not sure why that would help. but maybe try that again?

Also, can you post your entire signal levels? It will be the Connect tab, not the Signal tab.

I don't have a connect tab, but here is everything for the downlink:

Was looking for the upstream power levels. But I think something else is going on. I suggest having one the moderators take a look at you modem, and maybe ping it for latency from inside Cox network.

Also, has this happened before? Your last post stated your having issues with internet, but I don't see how provisioning can help with a latency issue.

Hmm. Did something big happen in the AZ/NV area last night? Saw alot of posts from that area on Cox last 2 days.

@Jimbo How long did the problem last? If you do a tracert now, does it still show the same thing?

Yea, may not have anything to do with Jimbo, specailly if they have been having the issue for more then a week. FYI, this is the post that made me suspect something.

Here's todays tracert:

Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. All rights reserved.

C:\>tracert cox.net

Tracing route to cox.net [68.99.123.161]
over a maximum of 30 hops:

  1     6 ms     9 ms    15 ms  10.80.0.1
  2     9 ms     9 ms    10 ms  24-234-16-217.ptp.lvcm.net [24.234.16.217]
  3     *        *        *     Request timed out.
  4    11 ms    10 ms     9 ms  24-234-6-250.ptp.lvcm.net [24.234.6.250]
  5    68 ms    68 ms    69 ms  dukedsrj01-ge-210.0.rd.at.cox.net [68.1.1.121]
  6    73 ms    74 ms    68 ms  68.1.15.234
  7    68 ms    67 ms    73 ms  68.99.123.4
  8    68 ms    62 ms    61 ms  ww2.cox.com [68.99.123.161]

Trace complete.

I did see the awesome speed of 60+ mb right after provisioning last night/early this morning, but it looks like currently it is:

I assume the problem just must be capacity-based....more users on during peak hours/weekend days?

Start	Cox Net	Download Speed	Upload Speed	Latency	Your IP Address	Cox Market
Sun Apr 27 1:20 PM	Yes	5 Mbps	22 Mbps	17 millisec	68.108.52.252	Las Vegas

Jimbo1234 said:
I did see the awesome speed of 60+ mb right after provisioning last night/early this morning,

Did you call to get it reprovisioned or are you assuming one of the moderators did? Because it doesn't look like they mentioned they did. How long did you get 60Mb? Seconds, min, hours?

Provisioning is just a fancy word for updating the information Cox sends to the modem to dictate how it acts on their system. Alot of people don't understand it, so suggest and try provisioning even if it has nothing to do with the problem. 

Jimbo1234 said:
I assume the problem just must be capacity-based....more users on during peak hours/weekend days?

I doubt it. Capacity issues wouldn't cause actual latency. Its probably a intermittent issue that just isn't as bad right now, so it slowing things down, but not causing the latency like before. 

EDIT Ran across this thread, and they mentioned reprovisioning fix their issue. I still feel its a false positive, meaning I think the reboot or something else that goes ALONG with the reprovisioning is fixing the issue, but Im open minded enough to share the thread. Something going on? Although they are in VA.