Forum Discussion

ulsterman's avatar
ulsterman
New Contributor II
6 years ago

Cox Cable internet is garbage. I don't know why.

When using a separate modem and router, I ping about 25-30 ms to LA. It randomly spikes to over 300 very frequently. When I take away the router and just use the modem, I get the same results. Cox to...
internet
Internet Connection
internet speed
Internet Speed Slow
ChrisL's avatar
ChrisL
Former Moderator
@Ulsterman

Looking from this end I'm not seeing any indication of an issue from us to the modem. It may be that the issue is just intermittent. You can try using a tool called pingplotter to monitor the connection and see if any issues are discovered. They should have a free version on their website.

-Chris
ulsterman's avatar
ulsterman
New Contributor II
6 years ago

This issue also seems to be a lot more prevalent after 9:00 pm. Didn't notice any issues when testing at 4:30 PM

  • KevinM2's avatar
    KevinM2
    Former Moderator
    6 years ago
    Hello, we are not detecting any packet loss, and your modem appears to be within the normal parameters. Would you be able to provide a traceroute and/or pingplotter to the server? Please do so on a hard-wired connection to the modem. By reviewing the traceroutes, we can determine if there's latency/packet loss occurring on or off of our network. -Kevin M. Cox Support Forum Moderator
    • ulsterman's avatar
      ulsterman
      New Contributor II
      6 years ago

      Could you describe what to do exactly?

    • ulsterman's avatar
      ulsterman
      New Contributor II
      6 years ago

      Could you describe what to do exactly?

      • Becky's avatar
        Becky
        Moderator
        6 years ago
        Hi Ulsterman, PingPlotter tests your network for latency and packet loss and graphs the results. Learn more at www.pingplotter.com/.../free.html. A traceroute shows the step-by-step path that a connection takes to its destination. To run a traceroute in Windows OS, use the following steps:
        1. Click Start.
        2. In the search field, type cmd.
        3. Click to select the Command Prompt app.
        4. Type “tracert www.WebsiteName.com” or “tracert IPaddress” (without the quotation marks).
        5. Press Enter.
        6. Allow several minutes for the traceroute to complete.
        7. Click in the Command Prompt window and press Ctrl and A simultaneously to highlight the text.
        8. Press Ctrl and C simultaneously to copy the text.
        9. Paste the text (Ctrl V) into the body of an email and send it to Cox.help@cox.com or post it on this thread.
        -Becky, Cox Support Forums Moderator
    • ulsterman's avatar
      ulsterman
      New Contributor II
      6 years ago

      I ran three tests to google.com . These look to be fine, but my connection is still terrible 30 seconds after this test. This always happens after 8:00 PM. 

      Tracing route to google.com [172.217.14.78]
      over a maximum of 30 hops:

      1 1 ms 3 ms 1 ms 192.168.1.1
      2 9 ms 68 ms 22 ms 10.8.0.1
      3 12 ms 9 ms 12 ms 100.120.105.122
      4 19 ms 37 ms 21 ms ip68-4-11-96.oc.oc.cox.net [68.4.11.96]
      5 25 ms 47 ms 24 ms 68.1.1.171
      6 48 ms 23 ms 63 ms 72.14.242.92
      7 26 ms 53 ms 25 ms 108.170.247.193
      8 38 ms 40 ms 23 ms 74.125.251.39
      9 19 ms 19 ms 22 ms lax17s38-in-f14.1e100.net [172.217.14.78]

      Trace complete.

      C:\Users\kdogs>
      C:\Users\kdogs>tracert google.com

      Tracing route to google.com [172.217.14.78]
      over a maximum of 30 hops:

      1 1 ms <1 ms <1 ms 192.168.1.1
      2 31 ms 13 ms 42 ms 10.8.0.1
      3 17 ms 27 ms 8 ms 100.120.105.122
      4 20 ms 12 ms 14 ms ip68-4-11-96.oc.oc.cox.net [68.4.11.96]
      5 15 ms 15 ms 16 ms 68.1.1.171
      6 31 ms 22 ms 29 ms 72.14.242.92
      7 23 ms 31 ms 26 ms 108.170.247.193
      8 34 ms 30 ms 27 ms 74.125.251.39
      9 21 ms 16 ms 13 ms lax17s38-in-f14.1e100.net [172.217.14.78]

      Trace complete.

      C:\Users\kdogs>tracert google.com

      Tracing route to google.com [172.217.14.78]
      over a maximum of 30 hops:

      1 1 ms <1 ms <1 ms 192.168.1.1
      2 9 ms 10 ms 16 ms 10.8.0.1
      3 15 ms 22 ms 10 ms 100.120.105.122
      4 14 ms 17 ms 15 ms ip68-4-11-96.oc.oc.cox.net [68.4.11.96]
      5 18 ms 21 ms 21 ms 68.1.1.171
      6 24 ms 21 ms 24 ms 72.14.242.92
      7 26 ms 25 ms 45 ms 108.170.247.193
      8 37 ms 25 ms 31 ms 74.125.251.39
      9 18 ms 26 ms 18 ms lax17s38-in-f14.1e100.net [172.217.14.78]

      Trace complete.

      • Allan's avatar
        Allan
        Moderator
        6 years ago
        @Ulsterman. I do not see anything abnormal with those traces. I recommend having a device do the traces again when you are experiencing the issue so we can get a more accurate look at what is going on. Thanks. -Allan Cox Support Forums Moderator.