Forum Discussion

hudhacks's avatar
hudhacks
New Contributor II
5 years ago

Inconsistent Service Disruptions (i.e. T3,T11,T4) - since July service work

Location: 85255

Modem: Arris SB6183 , no spliter

Service Level: 300mbps

Issues: Modem Event logs (see screen shot  below)

  • Started Unicast Maintenance Ranging - No Response received - T3 time-out;
  • TLV-11 - unrecognized OID
  • Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out
  • Unicast Ranging Received Abort Response - Re-initializing MAC
  • DHCP WARNING - Non-critical field invalid in response
  • No Ranging Response received - T3 time-out

Description of Issue:

No internet service for 2-5 minutes that occurs periodically between 3-5 times during the day.

I noticed the issue began approximately a week after notification from HOA that Cox was completing 2nd service operation in area, which occurred near end of July.

Resolution Actions:

Outcome from Resolution Actions:

  • Issues still exists for me, and was informed neighbors are having similar issue
  • Cox suggested having a tech come out, though I have to cover the $100 if nothing is found. This is odd since I found the above posts, people are calling to cause waits of a minimum of 30min, but Cox acts as if this is all being made up.
  • Many others in the Phoenix metro area have same issues , therefore this is not an isolated issue or related to a specific modem.

Conclusion:

Field maintenance modifications during the month of July has resulted in consistent issues across the area. The service disruption issues are "... signal-to-noise ratio (SNR) on the upstream to a point where the cable modem’s power level is insufficient to transmit any messages." , which results in "...it resets its cable interface and restarts the registration process.".

Cox only you all are aware of the modifications made in July the result was been disruptive during the past 3-4 weeks. This situation will only get worse as more schools start! I have no idea what needs to be resolved, but I've got many years in IT; when a change is bad back-it-out.

Cox what do you need from customers to get this resolved? What do I need to do to get this resolved?

IMO if this continues during the next 2 weeks as schools come online the calls will increase to support, city counsel, and state organizations ; people are going to not be kind.

Screenshots from Modem

Monday Aug-3 to Sunday Aug-9

  • hypr3060's avatar
    hypr3060
    New Contributor II

    I'm having the same issue here in 85383. I've chatted in 3 or 4 times now. I get kicked off multiple times a day. Modem logs show T3 issues. Chat rep doesn't know what that means so they ask me to reset my modem over and over.

    They scheduled a tech to come to my house and they never showed. Now Cox wants me to buy a monthly support package or pay $75 for another tech to come out.

    I started noticing the issues in July though it could have been happening sooner. With the amount that I'm working from home now, I notice it a lot more since I'm getting kicked off work calls or even the support chat with Cox today. Literally lost my internet while I was on the support chat and it didn't seem to matter. 

    This is probably the best article I've found to describe my situation. 
    https://forums.cox.com/forum_home/internet_forum/f/internet-forum/3152/t3-and-t4-timeouts-from-an-ex-field-technician 

    No idea where to go from here. 

    Aug 10 2020 18:53:17 Critical (3) Unicast Ranging Received Abort Response - initializing MAC
    Aug 10 2020 18:53:17 Critical (3) No Ranging Response received - T3 time-out
    Aug 10 2020 18:53:37 Critical (3) Unicast Ranging Received Abort Response - initializing MAC
    Aug 10 2020 18:53:37 Critical (3) No Ranging Response received - T3 time-out
    Aug 10 2020 19:07:04 Critical (3) SYNC Timing Synchronization failure - Loss of Sync
    Aug 10 2020 20:10:13 Critical (3) No Ranging Response received - T3 time-out
    Aug 10 2020 20:43:50 Critical (3) SYNC Timing Synchronization failure - Loss of Sync
    Aug 11 2020 03:09:28 Warning (5) MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1
    Aug 11 2020 03:09:28 Notice (6) TLV-11 - unrecognized OID
    Aug 11 2020 04:04:59 Critical (3) No Ranging Response received - T3 time-out
    Aug 11 2020 10:21:22 Critical (3) Unicast Ranging Received Abort Response - initializing MAC
    Aug 11 2020 10:21:23 Critical (3) No Ranging Response received - T3 time-out
    Aug 11 2020 10:22:23 Critical (3) Ranging Request Retries exhausted
    Aug 11 2020 10:22:23 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted
    Aug 11 2020 10:22:43 Critical (3) Ranging Request Retries exhausted
    Aug 11 2020 10:22:43 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted
    Aug 11 2020 10:23:03 Critical (3) Ranging Request Retries exhausted
    Aug 11 2020 10:23:03 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted
    Aug 11 2020 10:23:23 Critical (3) No Ranging Response received - T3 time-out
    Aug 11 2020 10:30:48 Critical (3) Unicast Ranging Received Abort Response - initializing MAC
    Aug 11 2020 10:30:48 Critical (3) No Ranging Response received - T3 time-out
    Aug 11 2020 10:32:58 Critical (3) Unicast Ranging Received Abort Response - initializing MAC
    Aug 11 2020 10:32:58 Critical (3) No Ranging Response received - T3 time-out
    Aug 11 2020 10:34:58 Critical (3) Unicast Ranging Received Abort Response - initializing MAC
    Aug 11 2020 10:34:58 Critical (3) No Ranging Response received - T3 time-out
    Aug 11 2020 10:37:28 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out
    Aug 11 2020 10:38:38 Critical (3) Unicast Ranging Received Abort Response - initializing MAC
    Aug 11 2020 10:38:38 Critical (3) No Ranging Response received - T3 time-out
    Aug 11 2020 10:40:37 Critical (3) Unicast Ranging Received Abort Response - initializing MAC
    Aug 11 2020 10:40:38 Critical (3) No Ranging Response received - T3 time-out
    Aug 11 2020 10:42:37 Critical (3) Unicast Ranging Received Abort Response - initializing MAC
    Aug 11 2020 10:42:37 Critical (3) No Ranging Response received - T3 time-out
    Aug 11 2020 10:44:37 Critical (3) Unicast Ranging Received Abort Response - initializing MAC
    Aug 11 2020 10:44:37 Critical (3) No Ranging Response received - T3 time-out
    Aug 11 2020 11:08:25 Warning (5) MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1
    Aug 11 2020 11:08:25 Notice (6) TLV-11 - unrecognized OID
    Aug 11 2020 12:31:17 Critical (3) SYNC Timing Synchronization failure - Loss of Sync
    Aug 11 2020 13:38:46 Critical (3) Unicast Ranging Received Abort Response - initializing MAC
    Aug 11 2020 13:38:46 Critical (3) No Ranging Response received - T3 time-out
    • Dave9's avatar
      Dave9
      Contributor III

      Did they really say you have to pay $75 to schedule the technician? Or did they say it will be $75 if the technician has to fix your equipment? I've always understood it to mean that if they send a tech out, the tech is going to fix your problem but if they have to fix your equipment then you have to pay. Seems fair enough to me. Are they now charging the fee in advance just to schedule the tech?

      Chat support techs don't understand the system. They just have a list of steps to follow and they can see a red light/green light status on your modem. All of this technical stuff about T3/T4/DRW is over their heads. Use phone or e-mail support for anything that requires troubleshooting.

      • hypr3060's avatar
        hypr3060
        New Contributor II

        This is the portion of my chat today where he told me that it would be $75 to schedule someone to come out. 

        02:17:28 PM 
        [Cox Rep Name Hidden]

        Since what we've done so far hasn't resolved the issue, it seems the issue is probably with your equipment (gateway/router/modem). For additional help, you might need to speak to your equipment manufacturer. I can check for the phone number if you'd like.

        You can also schedule a technician appointment, it has a charge of $75.00.

    • hudhacks's avatar
      hudhacks
      New Contributor II

      That link is useful, Thanks!! I have tech coming tomorrow, morning so will want to hover and see what happens.

    • Allan's avatar
      Allan
      Moderator
      @Hypr3600, We can take a closer look at this for you. Please send us an email with your full name and address to cox.help@cox.com. -Allan, Cox Support Forums Moderator.
  • hypr3060's avatar
    hypr3060
    New Contributor II

    So apparently, the fact that I posted that I'm having the same issue in a similar area (85383) is viewed as Spam or Abuse by Cox and was taken down. haha. Can't get help anywhere these days. I'm not sure how my post was any different than everything else on this thread and the numerous threads linked above. 

    • hypr3060's avatar
      hypr3060
      New Contributor II

      Meanwhile, I haven't been kicked off two business calls with potential clients and my modem log looks like this....

      Aug 11 2020 17:14:43 Critical (3) No Ranging Response received - T3 time-out
      Aug 11 2020 17:15:01 Critical (3) Unicast Ranging Received Abort Response - initializing MAC
      Aug 11 2020 17:15:01 Critical (3) No Ranging Response received - T3 time-out
      Aug 11 2020 17:16:20 Critical (3) Unicast Ranging Received Abort Response - initializing MAC
      Aug 11 2020 17:16:21 Critical (3) No Ranging Response received - T3 time-out
      Aug 11 2020 17:16:40 Critical (3) Unicast Ranging Received Abort Response - initializing MAC
      Aug 11 2020 17:16:41 Critical (3) No Ranging Response received - T3 time-out
      Aug 11 2020 17:18:00 Critical (3) Unicast Ranging Received Abort Response - initializing MAC
      Aug 11 2020 17:18:00 Critical (3) No Ranging Response received - T3 time-out
      Aug 11 2020 17:18:20 Critical (3) Unicast Ranging Received Abort Response - initializing MAC
      Aug 11 2020 17:18:20 Critical (3) No Ranging Response received - T3 time-out
      Aug 11 2020 17:19:40 Critical (3) Unicast Ranging Received Abort Response - initializing MAC
      Aug 11 2020 17:19:40 Critical (3) No Ranging Response received - T3 time-out
      Aug 11 2020 17:20:20 Critical (3) Unicast Ranging Received Abort Response - initializing MAC
      Aug 11 2020 17:20:20 Critical (3) No Ranging Response received - T3 time-out
      Aug 11 2020 17:21:20 Critical (3) Unicast Ranging Received Abort Response - initializing MAC
      Aug 11 2020 17:21:20 Critical (3) No Ranging Response received - T3 time-out
      Aug 11 2020 17:22:00 Critical (3) Unicast Ranging Received Abort Response - initializing MAC
      Aug 11 2020 17:22:00 Critical (3) No Ranging Response received - T3 time-out
      Aug 11 2020 17:23:00 Critical (3) Unicast Ranging Received Abort Response - initializing MAC
      Aug 11 2020 17:23:00 Critical (3) No Ranging Response received - T3 time-out
      Aug 11 2020 17:24:00 Critical (3) Unicast Ranging Received Abort Response - initializing MAC
      Aug 11 2020 17:24:00 Critical (3) No Ranging Response received - T3 time-out
      Aug 11 2020 17:24:40 Critical (3) Unicast Ranging Received Abort Response - initializing MAC
      Aug 11 2020 17:24:40 Critical (3) No Ranging Response received - T3 time-out
      Aug 11 2020 17:24:43 Critical (3) Ranging Request Retries exhausted
      Aug 11 2020 17:24:43 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted
      Aug 11 2020 17:25:39 Critical (3) Unicast Ranging Received Abort Response - initializing MAC
      Aug 11 2020 17:25:40 Critical (3) No Ranging Response received - T3 time-out
      Aug 11 2020 17:26:39 Critical (3) Unicast Ranging Received Abort Response - initializing MAC
      Aug 11 2020 17:26:40 Critical (3) No Ranging Response received - T3 time-out
      Aug 11 2020 17:27:39 Critical (3) Unicast Ranging Received Abort Response - initializing MAC
      Aug 11 2020 17:27:39 Critical (3) No Ranging Response received - T3 time-out
      Aug 11 2020 17:28:39 Critical (3) Unicast Ranging Received Abort Response - initializing MAC
      Aug 11 2020 17:28:39 Critical (3) No Ranging Response received - T3 time-out
      Aug 11 2020 17:29:19 Critical (3) Unicast Ranging Received Abort Response - initializing MAC
      Aug 11 2020 17:29:19 Critical (3) No Ranging Response received - T3 time-out
  • Dave9's avatar
    Dave9
    Contributor III

    This is looking more and more like a widespread issue. Up until about 10 days ago, my service was so great that I actually made a post praising Cox for their great quality.

    Now, like many others on this forum in the same area, I'm getting T3 timeouts, DRW violations, and severe packet loss of up to 35% on the upstream. The common factor in almost all of the posts you linked seems to be problems on the upstream. Some also have downstream issues, but upstream appears to be more common. Like you I've dug into the DOCSIS specification and documentation, and I came to the same conclusions that you did about possible causes.

    Here are the possibilities that I see:

    1. Everyone's modem and/or interior cabling went bad simultaneously around August 1st. I hope no Cox support techs think this is a real possibility, even though they always try to blame the modem.
    2. There are multiple individual network issues that all started around August 1st. A slim possibility at best.
    3. There is a widespread issue but Cox is not aware of it yet. In this case, these reports need to be escalated to someone who is empowered to review them as a group and investigate the overall pattern.
    4. There is a widespread issue, Cox is aware of it, but support has been directed not to disclose the issue. I hope that's not the case, but it would at least mean there's hope of getting it fixed someday.

    Some of us are likely going to need to schedule tech visits to get this escalated to the proper levels. That's too bad because it wastes our time and Cox's time, but there might be no other way to get it resolved. If you're confident that your modem and cabling is good, it's worth it to have a tech come out. They threaten a $100 charge but I've never seen anyone get charged the fee unless it was a really obvious problem like having an unplugged coaxial cable or forgetting to connect power to the modem.

    • hudhacks's avatar
      hudhacks
      New Contributor II

      I've heard the 4 or 5 calls from the same neighborhood triggers getting a data tech sent to an area, so get your neighbors to call.

    • GiveMeMoreBits's avatar
      GiveMeMoreBits
      New Contributor II

      I’m from the Las Vegas area and my areas service went down for a week, came back even faster then before. Now it goes in and out at random times. Sometimes it’ll be 3 pm and other times it is 3 am. I notice my modem started to restart itself around the same time. Also, it used to say there was an outage in my area for about a month and not it says nothing when I log onto cox.

      This wasn’t in August though. It was 2 months or more, whenever the initial outage occurred. It seems to occur more and more though and online school for most of the state is about to start.

      • DustinP's avatar
        DustinP
        Moderator
        GiveMeMoreBits,

        I understand how frustrating an off and on issue can be to face and wanting to get to the bottom of a solution. We may need to reserve a service appointment to help identify what's causing the service disruption outside of the outage alerts from before. You may email support at Cox.Help@cox.com with your complete address and details of the issues happening now.

        Dustin
        Cox Support Forum Moderator
  • Viole's avatar
    Viole
    New Contributor III

    I made one of the posts on the forum that you linked. So far, my problem still persists as well. I have gotten a new modem and I made sure that there were no amps or splitters on my coax cable. My modem is the Motorola MB8600 and it's event logs look just like yours. I also have a lot of uncorrectables on my modem's status/connection page. It seems others in my area are also experiencing the same issues as I saw some else in my zipcode(92071, San Diego County) post in the forums as well. I think the only thing left for me is to try to get a technician to come and look at the wiring. It does seem like this a widespread issue as more and more posts are being made.

    Here are my modem's event logs for comparison:

     Log  
      
        Time    Priority    Description 
        18:24:02
    Sun Aug 9 2020
      Notice (6)   CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1 2 3.;CM-MAC=00:40:36:5d:10:7e;CMTS-MAC=00:59:dc:79:0a:3c;CM-QOS=1.1;CM-VER=3.1;
        18:25:47
    Sun Aug 9 2020
      Warning (5)   RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=00:40:36:5d:10:7e;CMTS-MAC=00:59:dc:79:0a:3c;CM-QOS=1.1;CM-VER=3.1;
        18:25:47
    Sun Aug 9 2020
      Warning (5)   Dynamic Range Window violation
        18:25:47
    Sun Aug 9 2020
      Warning (5)   RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=00:40:36:5d:10:7e;CMTS-MAC=00:59:dc:79:0a:3c;CM-QOS=1.1;CM-VER=3.1;
        18:25:47
    Sun Aug 9 2020
      Warning (5)   Dynamic Range Window violation
        18:43:25
    Sun Aug 9 2020
      Warning (5)   RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=00:40:36:5d:10:7e;CMTS-MAC=00:59:dc:79:0a:3c;CM-QOS=1.1;CM-VER=3.1;
        18:43:25
    Sun Aug 9 2020
      Warning (5)   Dynamic Range Window violation
        18:43:25
    Sun Aug 9 2020
      Warning (5)   RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=00:40:36:5d:10:7e;CMTS-MAC=00:59:dc:79:0a:3c;CM-QOS=1.1;CM-VER=3.1;
        18:43:25
    Sun Aug 9 2020
      Warning (5)   Dynamic Range Window violation
        18:43:25
    Sun Aug 9 2020
      Warning (5)   RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=00:40:36:5d:10:7e;CMTS-MAC=00:59:dc:79:0a:3c;CM-QOS=1.1;CM-VER=3.1;
        18:43:25
    Sun Aug 9 2020
      Warning (5)   Dynamic Range Window violation
        18:43:25
    Sun Aug 9 2020
      Warning (5)   RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=00:40:36:5d:10:7e;CMTS-MAC=00:59:dc:79:0a:3c;CM-QOS=1.1;CM-VER=3.1;
        18:43:25
    Sun Aug 9 2020
      Warning (5)   Dynamic Range Window violation
        18:43:25
    Sun Aug 9 2020
      Warning (5)   RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=00:40:36:5d:10:7e;CMTS-MAC=00:59:dc:79:0a:3c;CM-QOS=1.1;CM-VER=3.1;
        18:43:25
    Sun Aug 9 2020
      Warning (5)   Dynamic Range Window violation
        18:43:46
    Sun Aug 9 2020
      Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:36:5d:10:7e;CMTS-MAC=00:59:dc:79:0a:3c;CM-QOS=1.1;CM-VER=3.1;
        18:43:47
    Sun Aug 9 2020
      Notice (6)   CM-STATUS message sent. Event Type Code: 16; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=00:40:36:5d:10:7e;CMTS-MAC=00:59:dc:79:0a:3c;CM-QOS=1.1;CM-VER=3.1;
        18:44:12
    Sun Aug 9 2020
      Notice (6)   CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1 2 3.;CM-MAC=00:40:36:5d:10:7e;CMTS-MAC=00:59:dc:79:0a:3c;CM-QOS=1.1;CM-VER=3.1;
        18:44:45
    Sun Aug 9 2020
      Warning (5)   RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=00:40:36:5d:10:7e;CMTS-MAC=00:59:dc:79:0a:3c;CM-QOS=1.1;CM-VER=3.1;
        18:44:45
    Sun Aug 9 2020
      Warning (5)   Dynamic Range Window violation
        18:45:05
    Sun Aug 9 2020
      Warning (5)   RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=00:40:36:5d:10:7e;CMTS-MAC=00:59:dc:79:0a:3c;CM-QOS=1.1;CM-VER=3.1;
        18:45:05
    Sun Aug 9 2020
      Warning (5)   Dynamic Range Window violation
        19:09:23
    Sun Aug 9 2020
      Warning (5)   RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=00:40:36:5d:10:7e;CMTS-MAC=00:59:dc:79:0a:3c;CM-QOS=1.1;CM-VER=3.1;
        19:09:23
    Sun Aug 9 2020
      Warning (5)   Dynamic Range Window violation
        19:09:23
    Sun Aug 9 2020
      Warning (5)   RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=00:40:36:5d:10:7e;CMTS-MAC=00:59:dc:79:0a:3c;CM-QOS=1.1;CM-VER=3.1;
        19:09:23
    Sun Aug 9 2020
      Warning (5)   Dynamic Range Window violation
        19:16:02
    Sun Aug 9 2020
      Warning (5)   RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=00:40:36:5d:10:7e;CMTS-MAC=00:59:dc:79:0a:3c;CM-QOS=1.1;CM-VER=3.1;
        19:16:02
    Sun Aug 9 2020
      Warning (5)   Dynamic Range Window violation
        19:16:02
    Sun Aug 9 2020
      Warning (5)   RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=00:40:36:5d:10:7e;CMTS-MAC=00:59:dc:79:0a:3c;CM-QOS=1.1;CM-VER=3.1;
        19:16:02
    Sun Aug 9 2020
      Warning (5)   Dynamic Range Window violation
        19:35:01
    Sun Aug 9 2020
      Warning (5)   RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=00:40:36:5d:10:7e;CMTS-MAC=00:59:dc:79:0a:3c;CM-QOS=1.1;CM-VER=3.1;
        19:35:01
    Sun Aug 9 2020
      Warning (5)   Dynamic Range Window violation

     

       Downstream Bonded Channels  
      
       Channel Lock Status Modulation Channel ID Freq. (MHz) Pwr (dBmV) SNR (dB) Corrected Uncorrected
       1 Locked QAM256 29 951.0 6.7 39.8 15460 38821
       2 Locked QAM256 1 783.0 6.0 39.5 21099 52914
       3 Locked QAM256 2 789.0 5.8 39.4 21014 54902
       4 Locked QAM256 3 795.0 5.7 39.5 20790 53369
       5 Locked QAM256 4 801.0 5.5 39.1 20376 54716
       6 Locked QAM256 5 807.0 5.2 39.2 19330 49089
       7 Locked QAM256 6 813.0 4.9 39.0 20390 52002
       8 Locked QAM256 7 819.0 4.5 38.8 19584 48155
       9 Locked QAM256 8 825.0 4.7 38.9 18990 49564
       10 Locked QAM256 9 831.0 4.9 39.1 18870 46281
       11 Locked QAM256 10 837.0 5.2 39.2 19099 50312
       12 Locked QAM256 11 843.0 5.4 39.4 18164 46269
       13 Locked QAM256 12 849.0 5.6 39.4 18579 48249
       14 Locked QAM256 13 855.0 5.8 39.5 18094 45018
       15 Locked QAM256 14 861.0 5.9 39.5 18413 48269
       16 Locked QAM256 15 867.0 6.0 39.3 18060 44841
       17 Locked QAM256 16 873.0 6.4 39.7 18141 46347
       18 Locked QAM256 17 879.0 6.3 39.6 17469 45716
       19 Locked QAM256 18 885.0 6.4 39.7 17367 45595
       20 Locked QAM256 19 891.0 6.5 39.7 17079 42992
       21 Locked QAM256 20 897.0 6.6 39.7 17214 45631
       22 Locked QAM256 21 903.0 6.4 39.7 16237 40132
       23 Locked QAM256 22 909.0 6.4 39.7 17262 45792
       24 Locked QAM256 23 915.0 6.4 39.8 16189 38994
       25 Locked QAM256 24 921.0 6.6 39.6 16620 44480
       26 Locked QAM256 25 927.0 6.5 39.7 15609 37768
       27 Locked QAM256 26 933.0 6.8 39.9 16325 43095
       28 Locked QAM256 27 939.0 6.9 39.9 15608 38797
       29 Locked QAM256 28 945.0 7.0 40.1 16499 42520
       30 Locked QAM256 30 957.0 6.4 39.8 16472 41881
       31 Locked QAM256 31 963.0 6.6 39.9 15414 39212
       32 Locked QAM256 32 969.0 6.4 39.7 15744 41957
       33 Locked OFDM PLC 159 300.0 13.9 16.9 864972397 778848



       Upstream Bonded Channels  
      
       Channel Lock Status Channel Type Channel ID Symb. Rate (Ksym/sec) Freq. (MHz) Pwr (dBmV)
       1 Locked SC-QAM 1 5120 19.4 32.8
       2 Locked SC-QAM 2 5120 25.8 33.3
       3 Locked SC-QAM 3 5120 32.2 33.3
       4 Locked SC-QAM 4 5120 38.6 34.3
       5 Locked SC-QAM 6 2560 14.6 32.3
    • c5ride's avatar
      c5ride
      New Contributor III

      Same exact thing in New Orleans.  Around Aug 1.  several days of outages (outage showing on account page) and when it comes back it's spotty and inconsistent.  SOMETHING has gone wrong on COX's end and we are all paying the price.

    • Allan's avatar
      Allan
      Moderator
      @Viole, I see that the modem is still reporting time out errors. At this point, I recommend having a tech come out and take a look. Please send us an email with your full name and address to cox.help@cox.com so we can set the appointment up for you. -Allan, Cox Support Forums Moderator.
      • Viole's avatar
        Viole
        New Contributor III

        @Allan I just sent the email. 

  • pkendo's avatar
    pkendo
    New Contributor II

    Hey, we have also been experiencing incredibly slow speeds here in our neighborhood.  We live near Warm Springs and Eastern across from Sunset Park.  There’s been a lot of utility work going on in our area also.  I’ve called Cox, only to be told it’s our modem and then to be offered an upgrade on speeds. Which was fine because it’s the same price we were paying. But no one at Cox wants to admit they have a problem. I’ve spoken with 6 of my neighbors who also have Cox internet, they have also called and received similar responses.  I’m planning on calling Cox today and requesting a manager. I don’t think the issue is anyone’s modem, I believe it’s a street connection issue and possibly Cox is unaware of the situation.  

  • pkendo's avatar
    pkendo
    New Contributor II

    Furthermore I was told you can pay $10 a month for as little as three months and have a tech come out to your house and check the system.  I’m debating spending the $30 to see what happens! I’ll have to do some research on the service. I’m not willing to spend a $100 if they don’t find a problem! My Internet speed of 3.5 mbps should be problem enough for them!

  • c5ride's avatar
    c5ride
    New Contributor III

    allen dustinp I am at my wits end with this.  EVERY day the service goes out for my entire neighborhood and outages show on the account page.  Lasts anywhere from an hour to 6 hours.  It is not my connection it is a whole neighborhood/ city wide issue.  Every other post on Nextdoor is all about Cox outages.  Can someone please help me to flag a larger issue than just the same **?  Resetting my modem will not help a city wide issue.  I can’t even talk to an agent because it will not connect me if an outage is present.  This is in New Orleans.  Please help!