Oct 12, 2020

HughesNet Satellite Internet Tests

I've never been a big fan of satellite ISPs, and the latency tests (last pics) show one of the reasons why. And the rest of this rant are some of the other reasons. 

According to their website FAQ's page, the HughesNet geostationary satellite is 22,000 miles away. The stated max speed is 25 Mbps down and 3 Mbps up. Right.

So, if it takes 10 seconds to get 25 Mb of data (2.5 Mbps), but then 60 minutes to get a second 25 Mb of data (69.4 Kbps), the average speed should not be 1.375 Mbps (data/time)+(data/time) / 2 data sets. The average speed should be 0.135 Mbps, or 135 Kbps (total data / total time fetching that data).

Remember this one from a couple weeks ago? Here's a screen shot while updating a Raspberry Pi. Note the speed. This was a 55 minute download of 84.8 MB, with about 40 minutes of this. Notice it's on the 4th attempt to get the data? Yes, 4th attempt.

Below is a HughesNet speed test. The actual time to complete the 2 MB download was 24 seconds, from the time the progress bar started, to finished. HughesNet states the speed is 1.41 Mbps. Hmm. My math says 2 Mb / 24s = 0.083 Mbps, or 83 Kbps. What kind of math do they use? Do they subtract all latency time, buffering time, break time, lunch time, etc?

Funny. Even so, by their standards, the speed on this run is way into the "crappy speed" zone, even for their crappy 12 Mbps, top-o-the-dial bliss zone. Oh, notice the Ping Time. It didn't even register. Welcome to every evening at my house on satellite.

These are some screen shots of the last 30 days using the Google Wifi app. Here again, calculations must be made only when the status is "active", as opposed to "waiting" or "buffering", or having a file restart 8 times because it thought the connection was completely lost (this happens frequently). These numbers? These are way off from reality. Again, even so, this is pathetic.

  

More good news. We live 2.0 miles east of a brand new fiber optic cable, and 1/2 mile north of a high-speed cable, but the ISP won't bring service this way because they don't want to, unless all the neighbors pay $3,500 each to get it installed (even though they equip subdivisions for free, knowing they will soon have customers).

AT&T has really old telephone lines in our area, and not enough nodes for us all to get a telephone line. They also offer DSL service, but unless one of the neighbors gives up their connection, no hard-line phone or DSL is possible. Who even thinks about being happy with DSL any more? Right?

Okay, back to latency. Is almost 4,000 milliseconds too slow? Who'd of thought? It's slow enough. That, combined with the constant buffering means, "no VPN for you". No VPN, no WIRES-X, nothing that needs any sort of constant, or low latency connection. Nope.

Even something as simple as Netflix must be set to the lowest quality video available, and still there's plenty of time to make the popcorn, while you "watch" the movie. Oh, and if it's Friday, Saturday, or Sunday night... Honey, where did you put the deck of cards? Wanna play 500 Rummy? We got time.

ELON MUSK!!!! Where are you?!?! I hope you're reading this! Where's my STARLINK?!?!

Okay, I'm done. Thanks for listening to my stupid rant. So, let's get on the radio! No LATENCY there!

Ha! ...just havin' fun!



No comments:

Post a Comment