The modem has been replaced. I was told if the issue happens again would see about moving me to echostar 17. Is this something I would want to do or will i see worse preformance than I do on 19?
It's really anyone's guess, as service can vary from beam to beam and your placement within that beam footprint. If they suggested it as a possible fix, however, it might be worth it.
If you have Static IPv4 addressing, do not let them move you to ES17, that bird does not support it if my memory is correct.
I was advised could not speak with the NOC about changing the gateway or DNS. This is the server that all gateways see. Again their tests find nothing wrong. I am not really sure and was advised could not be changed to echostar 17 I should have never been told that.
In this case I am starting to think hughesnet is oversold and does not want to fix the issue.
It works if I bypass and use google dns but why I lose the web accleration part to do this? or would it hurt preformance really to stay on a third party dns for good?
It's unlikely that your issue has anything to do with system load. Hopefully the business account reps can send you up the chain to working with the engineers in order to figure out what's going on.
Strictly by definition, HughesNet must "oversell", as there's no way customers are going to pay what would be required to keep HughesNet a viable company while having a customer base so small that everyone could be guaranteed to get plan speed, barring technical and weather issues, of course. Upwards of $1000 or more per month. Since no one is going to pay anywhere near this, they impose monthly high speed data limits to force people to prioritize their activities so they don't run out, which helps to keep the service usable for a much larger customer base.
Right now, however, all bets are off, as the system is under many times the load it normally would be. That load doubled in just one week leading up to 3/20, and has likely doubled since then, or even more. Again, though, it's very unlikely that this is what's causing the issues you're seeing, as many others would be experiencing the same thing.
Not sure what all was said.... I am just gonna leave some info up about my terminal...
1: I have disabled IPv6 on LAN, but leave it enabled in modem - this helps me sometimes, though will eventually cause issues, somewhat.
2: Web Acceleration uses a few differen't techniques, but one of them involves SQUID, and SQUID on it's own will search an upstream DNS to get websites that it then sends off to you, though you still need a working local DNS. I personally avoid using WAS.
true/ But using google dns works fine I still belive something is up with hughesnet dns. But it works thats what matters. Besides I heard hughes should send up another sat soon. a LEO one hopefully. But who knows just as long as using a third party external dns does not hurt than I am good.
The Echostar 24 satellite is scheduled to go up in 2021 at the earliest, but it may be later due to the pandemic. It is a geostationary satellite, not LEO.
well so far google dns is working guess this is the soultion thank you for atleast having hughesnet dsl is no longer a real choice and 4g well can't keep up with the data demands. A hotspot for gaming works