Extremely slow Internet.

Sadly, the big terrestrial companies don't find the rural areas appetising. I'm glad to have satellite internet, otherwise I'd have to move. I have Verizon availability, but there aren't many towers here and so Internet access is substandard (and expensive) and the phone service unreliable. 

I don't know what the signal range is, but I believe anything over 90 is excellent. Maybe someone else will have an actual range.  EDIT: optimal signal strength varies by location, so for some locations 75 would be normal, and for others 100 would be normal. Your signal strength is excellent, though.  

I am still having problems with things but overall things DO seem to be better...

YouTube - Most of the time it seems to work fine and the download % is staying ahead of the video %, but sometimes it just buffers around every 10 seconds or so and the video is unwatchable.

Facebook Messenger - Sometimes when I try to send someone a message it just sits there and never goes through, the little circle that is supposed to turn into a check mark just stays blank, if I try to reload the page the message that I just typed is gone.

Facebook Videos - Posted videos and/or Live streamed videos buffer unendingly and are completely unwatchable.

Twitch - Live streamed videos buffer also unendingly.

Amazon Prime Video - It takes a minute or so to load the video and sometimes I get errors to check my Internet connection or that I have a slow connection and it wants to know if I want to continue waiting?  Once the video loads it buffers every couple of minutes for about ten seconds.

Netflix - Videos take about two minutes to load and then they seem to be ok, once in a while they will buffer for ten seconds or so.

And I understand what someone was saying about the signal taking a 45k mile round trip from me to the satellite to the ground station and back but... radio waves travel at the speed of light which is 186,000 miles per second, the satellite (Echostar 19) is 22,300 miles in orbit with a signal round trip of 44,600 miles which if you do the rough math the round trip is taking something of just under a quarter of a second which corrisponds with the fact that I can ping my Gateway (the Gateway is at the ground station) at 0.4xx ms.

Which brings me back to (I mentioned this in a previous comment)... the problems that I am having are at the ground station AFTER my Gateway, you fix the problems that are going on there and I will magically stop complaining.

Landon_Robinson 

Remember, the latency is round trip.  From you to the sat, then down to the gateway, and onto the net, then back to the gateway, up to the sat and back down to you.  So, it's really four legs of distance travel.  Roughly 89,000 miles, but a little more, being that neither you or the gateway are on the equator, directly under the satellite.  

Unfortunately, problems after the gateway are out of their hands. 

That is true that the distance will be further since neither I or the gateway are directly on the equator, I live somewhat north of the "45th Parallel", but still the round trip of 89,000 miles is going to be something around half a second, but going back to what I was talking about before... if I can ping my gateway at 0.4xx ms the problems should not be on my end.

Latency for satellite internet is about 500-600ms.  That's for the round trip, but that's  not the only thing to influence your experience. You will need to take into account the added issues caused by Internet latency and beam congestion. 

Landon_Robinson wrote:

That is true that the distance will be further since neither I or the gateway are directly on the equator, I live somewhat north of the "45th Parallel", but still the round trip of 89,000 miles is going to be something around half a second, but going back to what I was talking about before... if I can ping my gateway at 0.4xx ms the problems should not be on my end.

 

---

---

Landon_Robinson wrote:

That is true that the distance will be further since neither I or the gateway are directly on the equator, I live somewhat north of the "45th Parallel", but still the round trip of 89,000 miles is going to be something around half a second, but going back to what I was talking about before... if I can ping my gateway at 0.4xx ms the problems should not be on my end.

---

A ping is essentially a singular event and measures the round trip access time for that one event.

Accessing a web site or streaming server just for one access may be several events, depending upon additional content (images, stylesheets, javascript, etc.) and/or secure authentication processes, which in iteself is a multi-access event due to handshaking. So more complex than a ping, and the latency effects are cumulative.

As I am writing this I am waiting on a 13.9 meg video to download and I am downloading it (via Facebook Messenger) because my connection is so slow that the video refuses to play, and it took 11 minutes to download it and another video sent by the same person earlier today was 9-ish megs and took around 5 minutes to download, with a 25 meg connection I should have been able to download both of these in under 5 seconds.

YouTube also refuses to play videos I get about a half second of content and then 10 seconds of buffering, I just had to let the video sit there until it was finally done loading which took around five minutes and then let it play, this video was only 23 seconds long and I have the video quality set as low as it will go.

Netflix has gotten better and now only takes around 30 seconds to start playing instead of waiting two minutes.

Amazon Prime Video is still telling me that I have a slow connection and asking if I want to wait longer? Then it just freezes and nothing loads, I hit Reload and it starts over doing nothing for nearly 10 seconds and then things will finally start playing around 30-45 seconds later.

Pings to my Gateway still look fine but beyond by gateway things are still bad...

traceroute to www.hughesnet.com (34.197.164.140), 30 hops max, 60 byte packets
1 _gateway (192.168.42.1) 0.465 ms 0.446 ms 0.411 ms
2 host-67-45-0-1.hnremote.net (67.45.0.1) 612.213 ms 612.183 ms 612.220 ms
3 host-67-45-5-5.hnremote.net (67.45.5.5) 612.259 ms 612.156 ms 799.056 ms
4 host-67-45-5-4.hnremote.net (67.45.5.4) 799.089 ms 799.054 ms host-67-45-5-33.hnremote.net (67.45.5.33) 799.093 ms
5 4.16.168.17 (4.16.168.17) 799.063 ms 975.644 ms 975.621 ms
6 ae-2-3615.edge1.Dallas2.Level3.net (4.69.209.110) 1019.084 ms 703.975 ms 703.945 ms
7 99.82.183.118 (99.82.183.118) 1044.984 ms 99.82.183.120 (99.82.183.120) 969.599 ms 1498.418 ms
8 * * *
9 * * *
10 * * *

This has been going on for over a month now and I think that I have been patient enough but I need this fixed, so what do I need to do to get this fixed? If I need to get on a jet and fly to Hughesnet and personally talk to someone please let me know and I will make that happen.

Hopefully a rep such as Liz , Remy , or Damian will get involved and provide you with troubleshooting steps. 

Is anyone going to be doing anything because I would really like this resolved, I still cannot watch videos without buffering problems and waiting forever for them to start.

Re-read the replies you got to your original post. You have higher than advertised speeds; the latency you are experiencing is normal for satellite internet; streaming will be difficult if there is congestion on the beam assigned to you; streaming is affected by congestion more than it is by speed, and your speed is more than adequate for streaming.

HN can't change the laws of physics, the current limitations of satellite technology, or force people not to clog your beam with their streaming so you can stream.  You may want to look into PlayOn Cloud, which lets you download material from Netflix, Hulu, and others. Download the files when congestion is slow and then watch the downloaded files whenever you want.