Forum Discussion

JG333's avatar
JG333
New Contributor III
2 years ago

random disconnects

Ive been having issues in Arkansas on random quick disconnects for about a month. These last from 15 seconds to a few minutes and seem to get worse in the evenings. The connection can go an hour or t...
  • WiderMouthOpen's avatar
    WiderMouthOpen
    2 years ago

    First, post your signal levels from 192.168.100.1. See here for more info. Either copy paste the data, or if the formatting is bad, upload a screenshot. See here on how, but basically you have to join the forum. If it's easier, use Imgur and post a link.

    Next, do you see anything in the logs around the time of the disconnects? Don't post the logs unless you edit out your modem's MAC address from it. I suggest Justpaste.it for edited logs as they can sometimes set off the forum's anti spam feature.

    Last, have you tried connecting a PC direct to the S33 for a bit and see if the disconnect happen? This is moot if the signal levels or logs are obviously bad.

gaby665t's avatar
gaby665t
New Contributor

This is the exact same thing that’s happening to me and I’m so over talking to the live agent. I’m going to switch services.

WiderMouthOpen's avatar
WiderMouthOpen
Esteemed Contributor
2 years ago

Don't bother with chat. They are outsourced I believe and won't know what your talking about. That's assuming you can even get past the bot. Instead use the email or one of the Social Media contacts in the welcome thread. They may still ask you to troubleshoot your issue(like OP did) but they aren't forced to following a script like chat/Tier 1.

TL;DR Email support > Tier 1 > Chat.

  • JG333's avatar
    JG333
    New Contributor III
    2 years ago

    This was 4 minutes of down time no cycle power of anything came back on its own after that.

    • WiderMouthOpen's avatar
      WiderMouthOpen
      Esteemed Contributor
      2 years ago

      I see the usual T3/T4 errors which is mostly your issue. However I also see "CMSTATUS:US_Diplexer_Mode_Change" errors which I have never seen before. I found a interesting break down of the error here. Basically I think it just another data point for ingress on the upstream.