Getting "US profile assignment change" constantly causing random disconnects.

Thank you for the response. I do want to point out that the techs were very helpful, unfortunately it wasn't something they could resolve and only pass it up the chain which they did. The 2nd tech did give me their information so I can follow up with them to see what the next step may be and what they can/will do. I will give them some more time and see. The techs were both very understanding. It's the main CS point of contact that is at this point, utterly useless.

It is very possible that what you described happened regarding the trapping or the source. The note left on the door next days said they "addressed the main line concern" but concern appear to still exisit.

I don't know if other people are noticing it as well on my street. Maybe they are but it doesn't effect them, intermittent loss of service for 15-30 seconds  may not be an issue for most for regular use, but any disrupt in connection IS an issue for me and my job (my livelihood). Without going into details, it is a pain and time consuming to get the VPN back up and running. Not to mention the disrupt in work flow.

This isn't my forte and I don't know what it entails to resolve this issue, neither is it my job really. I did take a stroll down the street tracking the Cox line. There's exposed junction boxes (could be normal), dangling unused Coax cables (could be normal). Just seems poorly managed line to me. I took some pictures, I can PM them to you if you are curious. But something is clearly not right and the line appears to be riddled with noise, internal or external. 

Congested as in too much traffic or too much noise/ingress? 

Documentation on CMTS load balance does sound awfully "familiar" to what I'm experiencing with the constantly changing profiles.

Old documentation (2006) but seems somehow plausible to what's going on here.

"Dynamic modulation changes—The dynamic modulation feature affects the load-balancing algorithm because it typically switches an interface from a higher-bandwidth modulation profile to a lower-bandwidth modulation profile in response to noise conditions on the interface. For example, if an upstream is configured for 16-QAM modulation, sufficient noise levels could switch the upstream to a QPSK modulation profile. Depending on the load-balancing configuration, this could then result in the movement of cable modems to other channels. Similarly, when the noise conditions improve, and the modulation is returned to the original, higher-bandwidth profile, the cable modems could be moved again to rebalance the upstream channels."

Sounds like ping pong and my modem is the ball.

Honestly, I'm just trying to nail this down as far as being informed goes because I need to know if I'm chasing something that is bigger than my service alone and if I should perhaps start looking at alternatives if Cox can't act on this in a meaningful timeframe.

nvm, saw your other post, glad the issue resolved for you. I ended up going with a differernt provider and have not hooked up my Cox modem in some time (also haven't cancelled Cox service yet). The issue for me was that the problem persisted both on my Netgear Cm1100 and a new S33 modem, just couldn't deal with it any more as it was affecting my work.

Having this EXACT issue with my Arris SB8200 and a directly connected pfsense pc. It has been going on for months.  You mention another post, but I'm not seeing the other post, can someone describe the resolution to this?  

joeldjohnston,

If you're dropping connection at the modem it could be signal or network related (which would be outside of the community's ability to help with). To be sure I'd like to take a look at your connection. Please email us at cox.help@cox.com with your name, street address and the details of the trouble you're having with a link to this forum post.

Hi ColleenD, Thanks for the quick response, I just sent an email to that address about 10 minutes ago with the details from my logs as well as my contact info. Feel free to call me directly on that phone number to troubleshoot. Thank You!

joeldjohnston

Thanks so much for sending your information.  You should get a response shortly if you haven't already.