30.1.1 itself is normally a network issue, however, seeing the rest of the state codes may be a power issue. Are the modem and cables plugged in securely? Are you connected to a surge protector, or directly to an outlet?
Sometimes it acts like it's getting better. For instance, at this moment I have all green checks on the hourly history and only 8 red x on the daily chart.
But, it really isn't getting better at all. My internet has been impaired or non-functional 36 hours out of 6 days. Some of the uplink/downlink outages are due to weather but unless I'm getting cut off by bad weather up at the gateway end, not very much.
Yes, all power is clean and good with no recorded noise at all lately. Only a few blacks but no browns or overvoltage. All connections are secure and tight. I don't use surge protectors. All of my important network bits and pieces run on UPS. Speaking of UPS, my driver was here yesterday so I sent my old modem return with him.
Here's the most recent 1½ days of history. Pretty ridiculous.
Hey Remy, I just noticed something promising. This thing hasn't thrown any codes since a 20.2.1 associated with a bad thunderstorm late yesterday afternoon. Maybe the wizards are getting the problems sorted out.
Edit: I just noticed another positive sign. The diagnostic code is a steady 0000.0000.0000.0005 for the past 12 hours.
Good news @Remy. It appears to be fixed. Only one thunderstorn series of failures and one 30.1.1 failure over the past 2½ days. Huge, monumental improvement over the revolving disaster that began nearly nine days ago with the installation of the replacement modem.
The hourly graphs are pretty clean now. Only a few red x showing with the same DNS Acceleration (N) but those blips aren't bad enough to throw a state code. The diagnostic codes are hanging in with 0000-0000-0000-0005 most of the time.
Thanks for getting this fixed for me. I'll post back if it goes down the tubes again but it sure appears to be business as usual now.
Update: The web acceleration crashed hard again this morning. The modem logged 25 transitions to 30.1.1 for a duration of 3¾ hours between 5:30 and 11 AM. Then we had a late morning thunderstorm that caused a slew of expected uplink/downlink state codes. The good news is, that fixed the total disater with the web acceleration. No more errors since the storm got off us 8½ hours ago
BTW, no number of MBX resets or cycling the WA control made a difference this morning. Please pass this along to the wizards. Maybe this will give them a clue.
Edit: Web Acceleration is back to the original pattern. It started going down shortly before 5 AM and is now crashing on 30.1.1 about twice an hour.
So no errors at all since that point? Interesting. Good to hear! I'll pass this along, please let us know if you have any issues with this going forward.
Oh jeez @Remy Wall to wall 30.1.1 errors since Sunday morning. Please read all the messages. You missed the Sunday message and the Monday edit. Something is still badly broken.
Here's today's update. 20 Web Acceleration failures between 5 AM and 2 PM today for a total of 3½ hours of impaired operation. Today
@Lizcan you please get me some help with this? I was sent a refurb modem but it just goes on and on and on.
As Remy has previously explained, the 30.1.1 code is a result of an event on the HughesNet side, so an equipment swap at your site won't have an effect on that code.
We've inquired about this with our engineers and will let you know once we have any news from them to share.
Your cooperation, patience, and understanding are much appreciated.
Thank you @Liz I know it's a network problem and it sure is a strange one.
Wednesday morning update. As of this moment, only 1 transition to 30.1.1 has occurred since 5 PM yesterday. It went from 282 to 283 in 15 hours while there were 10 transitions between 2 PM and 5 PM yesterday. Too weird.