Forum Discussion

mkautzm's avatar
mkautzm
New Contributor II
6 years ago

Service Oversold in Irvine, CA. CMTS response time fluctuates wildly

It appears that Cox does not have the infrastructure to support usage at peak hours near my location.  This results in highly degraded service in the afternoon until later at night.  Some investigati...
KevinM2's avatar
KevinM2
Former Moderator
6 years ago
Hi mkautzm, can you please unplug your modem for at least 30 seconds and plug it back in for us? Please also make sure there are no loose or damaged connections in the home either. What issues are you experiencing specifically, is it slow speeds or intermittent connectivity? Are all devices experiencing this? In reference to traceroutes, we strongly recommend performing them on a hard-wired connection. -Kevin M. Cox Support Forum Moderator
  • mkautzm's avatar
    mkautzm
    New Contributor II
    6 years ago

    This is after power cycling hardware, although it doesn't really matter because the problem is outside my house (I assume 10.75.135.1 is the CMTS).  Everything is wired, but it wouldn't matter because the problem is at the CMTS - you can even verify this by looking at the hop to my router, which is reliably sub 1ms.  Same thing with damaged connections - the response time to my router is sub 1ms.

    The problems I experience are self-evident.  If the the response time to the CMTS has +/- 300ms, it means response times to every service is +/- 300ms.

    Evidence suggests strongly that the area is oversold and the CMTS is overloaded during peak hours.

    • KevinM2's avatar
      KevinM2
      Former Moderator
      6 years ago
      Hello, the second hop (10.75.135.1) is more than likely your modem, as it is a private IP Address. Additionally, the first hop appears to be a wireless router because the numbers begin with 192. Your modem shows it's been online for 67 days. When power-cycling the equipment, I recommend unplugging the modem itself for at least 60 seconds. Can you please perform another traceroute on a hard-wired connection?

      Also, issues are you experiencing with our internet service specifically? -Kevin M. Cox Support Forum Moderator
      • mkautzm's avatar
        mkautzm
        New Contributor II
        6 years ago

        It is not uncommon for a CMTS to show up as a local address.  If you'd like another view of this, these results are FROM a service provider, TO my house:

        02/12/2019 04:13:22 UTC
        --------------------

        MTR:
        Start: Mon Dec 2 04:13:26 2019 Blizzard 1.|-- Blizzard 0.0% 10 0.3 0.3 0.2 0.5 0.0
        2.|-- 24.105.18.3 0.0% 10 0.7 5.4 0.5 47.9 14.9
        3.|-- 137.221.105.16 0.0% 10 0.7 1.0 0.6 1.2 0.0
        4.|-- 137.221.66.18 0.0% 10 1.3 9.0 1.0 60.6 18.8
        5.|-- 137.221.83.66 0.0% 10 5.7 5.9 5.7 6.2 0.0
        6.|-- 137.221.65.68 0.0% 10 5.8 14.2 5.7 53.1 17.7
        7.|-- 137.221.68.32 0.0% 10 5.8 9.5 5.8 35.3 9.1
        8.|-- langbbrj02-ae1.301.r2.la.cox.net 0.0% 10 5.4 7.9 5.4 29.7 7.6
        9.|-- 68.1.1.170 0.0% 10 7.5 10.1 7.5 31.1 7.3
        10.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
        11.|-- ip70-181-109-239.oc.oc.cox.net 0.0% 10 122.2 78.3 16.7 297.4 85.6

        Looking at the last result, you can clearly see there is a great deal of variance, indicating an overloaded (or misconfigured) node in the route.  I had a post with a lot of other examples showing similar results.