@lighthope1 - Yes, they have been. It's funny though, isn't it? I've been forced to use HughesNet for years, and have complained for years, and have been told repeatedly there's nothing they can do. Nothing at all. But now that the Starlink open beta is about a month away, magically, mysterially, they find a way to double, triple, even quadruple bandwidth speed in a system that they previously claimed was absolutely impossible to improve. Though I haven't seen any additional "normal speed" capacity before cap. The future and new headache-free, inexpensive, and blazingly fast download AND upload speeds are just around the corner for all of us who depend upon satellite internet.
@MrBuster wrote:
- That request they put out asking for user input about work/education related sites they are having trouble with would imply they are intending to give these sites extra priority -- throttling them would be very counter productive to the entire purpose of the effort. After all, they are not putting all this is place to roll out a bunch of new plans with crazy limits and glowing names, right?
Or they could be trying to find out which sites are more problematic, and why, in order to make various tweaks to the system for those sites to better work.
@grizzle wrote:...
In terms of Teams, Zoom, and media streaming, I have found everything works best when running through a VPN. Without the VPN, I have had some services, websites, and apps that would take extremely long times to load, or simply timeout. Upload speeds when trying to share out files were non-existent, and again many times timeout. Once I began using a VPN, speeds seemed to balance out and "work better" - at least on my two computers. Unfortunately all my other home devices cannot run through VPN, so continue to be excessively slow or non-functional due to timeouts.
I gave Team a try without running a VPN just to get an idea if I would see a difference, and I must say Teams was amazing this morning as well. Of course, this is the morning, and it is generally less busy, but judging by the latency graph there seemed to be a bit more going on this morning. Yesterday it felt like a ghost town with the latency measures riding near minimum for satellite for me all morning.
Some years ago, I saw a website where a knowledgeable fellow shared a formula to calculate bandwidth from point A to point B given a number of values for variables to plug in -- like the latency and size of the TCP window (how much data the other site will push your way without getting an acknowledgement) Of course, as MarkJFine alluded to, satellite gateways have some complications like compression and some kind of super cache so that they can keep the stream of data moving your way since the lag of going over the satellite can cause really poor performance if the server at the other side is stingy with how much they will send without getting that ack. As Mark mentioned, with the VPN on, it is pretty hard be able to leverage caching and compression so VPN with satellite is generally regarded as more punishing to your available bandwidth than for non-satellite.
Anyway, that fellow advocated for estimating bandwidth and being more sparing in the use of real bandwidth tests in order to conserve bandwidth. He had some pithy statement -- I probably am getting this wrong -- but it was something like: It is better to estimate the bandwidth than to run a bandwidth test to know the bandwidth -- because when you run a bandwidth test you know your available bandwidth is always 0. Somehow my paraphrase seems way more verbose and has less impact....
Perhaps others will chime in with their results with Teams with VPN and without VPN. It seemed good either way for me.
Here's what the support page has: https://support.hughesnet.com/en/faq/internet/can-i-run-vpn-over-hughesnet
Of note: "HughesNet Technical Support does not provide help with configuring or troubleshooting problems associated with VPN clients."
Mileage varies widely when it comes to VPNs. They work for some and not at all for others.
No word on when/if the permanent snooze function will return, but once we find out we'll let you know.
-Liz
Just out of curiosity, and this is not meant in a condescending manner or anything of the like, but where are you getting your information concerning the following?
1. The bandwidth per video stream/download to known recreational video sites was roughly cut in half
2. Before these measures, a video stream with the VDS turned on would be capped around 5.5Mbps in non-congested times, and about half that during prime time (perhaps depending on the beam).
Edit: Please disregard. Reading on I see it was already answered.