About lighthope1

Mostly then its a matter of price? No, it's a combination of data and price. Would 50g @ $10 be reasonable?  Enjoyable, yes.  But reasonable? I'm sure HughesNet would love to be on the opposite end.  3g for $100.  Of course, they'd be out of business in a month. So, as a reasonable human being, I'm attempting to combine what I feel is an adequate value for my money. 50g for $100 is an acceptable value to me. 30g for $100 is not. ... View more

What are your expectations for a satellite internet connection? Exactly what I said in the OP. 50gig Anytime/50gig Bonus - $100/mo 40gig Anytime/50gig Bonus - $90/mo ... View more

Those numbers are pretty stingy. ... View more

I didn't ask what they were. I asked opinions on what they should be. ... View more

Don't use Zonealarm.  Why pay for something when there are free alternatives that work just as well? I use Comodo Internet Security  www.comodo.com    It's free, it includes both firewall and antivirus, and I've never had anything get through. ... View more

Another week with no unusual latency issues.  (The odd spike that lasts for a short time is not considered unusual.) I think we can consider this issue resolved. ... View more

Latency has been normal for the last several days.  There has been a few times when it shot up, but this happens infrequently and only last for a couple minutes. ... View more

Last three days, latency has been fairly decent, though last night it did start to go up to 1600 just as I was finishing up.  Don't know if it would have continued higher. Should I continue updating this?  By the lack of response, I really am under the impression that Hughesnet doesn't care. I wonder how quickly they'd respond if there was an issue with payment collection?  I bet they'd work really fast to resolve that. For any inconvenience, I will be adding a service credit to your account. The promised credit did not appear. ... View more

14K latency tonight.  That's FOURTEEN *THOUSAND* milliseconds. 6.5K at the gateway. Either there is something wrong with the modem or the gateway.  Look there. I have noticed that, when running a traceroute, it can take quite a long time to get the address.  Sometimes longer than the ping time.  Don't know if that is significant. ... View more

Hughesnet never said anything about an overloaded beam, so I won't presume that. Also, while those ping times seem "normal," the timeout are not. Latency has been better the last 24 hours, hence the delay in my reply.  I am attempting to post results when things are bad as normal results aren't helpful. While a 6k lag spike could be a temporary thing, the other results are too often to be just anomalies. ... View more

No I am not.  i do not host anything. ... View more

This next test seems to be all over the place. Tracing route to google.com [172.217.4.110] over a maximum of 30 hops:   1    <1 ms    <1 ms    <1 ms  192.168.1.1   2     1 ms    <1 ms     1 ms  100.107.182.129   3   726 ms  1070 ms  1081 ms  72.171.194.52   4     *     2871 ms   591 ms  72.171.196.58   5   643 ms   635 ms   724 ms  198.233.75.217   6   606 ms   921 ms     *     67.14.8.86   7  2445 ms   676 ms   722 ms  216.111.90.126   8   593 ms   582 ms   586 ms  108.170.243.225   9   668 ms     *     2192 ms  108.170.233.111  10   642 ms   629 ms   614 ms  172.217.4.110 Trace complete. Notice the timeouts coupled with other low pings. Here is the associated gateway test Packet Loss: 0.00% Average Delay: 1335.00 ms Minimum Delay: 910.00 ms Maximum Delay: 2030.00 ms IP Gateway: RAP43HNSIGW72C001Adv Nothing else was running. Half the internet is unusable for me with these problems.  I think my rates should be cut in half until it is fixed. ... View more

This next test seems to be all over the place. Tracing route to google.com [172.217.4.110] over a maximum of 30 hops:   1    <1 ms    <1 ms    <1 ms  192.168.1.1   2     1 ms    <1 ms     1 ms  100.107.182.129   3   726 ms  1070 ms  1081 ms  72.171.194.52   4     *     2871 ms   591 ms  72.171.196.58   5   643 ms   635 ms   724 ms  198.233.75.217   6   606 ms   921 ms     *     67.14.8.86   7  2445 ms   676 ms   722 ms  216.111.90.126   8   593 ms   582 ms   586 ms  108.170.243.225   9   668 ms     *     2192 ms  108.170.233.111  10   642 ms   629 ms   614 ms  172.217.4.110 Trace complete. Notice the timeouts coupled with other low pings. Here is the associated gateway test Packet Loss: 0.00% Average Delay: 1335.00 ms Minimum Delay: 910.00 ms Maximum Delay: 2030.00 ms IP Gateway: RAP43HNSIGW72C001Adv Nothing else was running. Half the internet is unusable for me with these problems.  I think my rates should be cut in half until it is fixed. ... View more

Another test. Tracing route to google.com [172.217.4.110] over a maximum of 30 hops:   1    <1 ms    <1 ms    <1 ms  192.168.1.1   2     1 ms    <1 ms    <1 ms  100.107.182.129   3  1853 ms   559 ms   584 ms  72.171.194.52   4   609 ms   616 ms   639 ms  72.171.196.58   5   794 ms  1000 ms   749 ms  198.233.75.217   6   826 ms  1242 ms  1078 ms  67.14.8.86   7  1289 ms  1590 ms  1249 ms  216.111.90.126   8   802 ms  1313 ms  1064 ms  108.170.243.225   9  1267 ms  1058 ms  1315 ms  108.170.233.111  10  1019 ms  1288 ms  1431 ms  172.217.4.110 Packet Loss: 0.00% Average Delay: 1381.00 ms Minimum Delay: 890.00 ms Maximum Delay: 1790.00 ms Gateway latency is increasing, so the tracert is increasing as well. ... View more

During all tests, I make sure that nothing else is running.  There may have been something during the 30% packet loss run, which is why I retested it. ... View more

Here is a tracert to 8.8.8.8, which is supposedly a good address to use when testing google.com Tracing route to 8.8.8.8 over a maximum of 30 hops   1    <1 ms    <1 ms    <1 ms  192.168.1.1   2     1 ms     1 ms    <1 ms  100.107.182.129   3   795 ms  1370 ms  1320 ms  72.171.194.52   4  1331 ms  2160 ms   612 ms  72.171.196.58   5   890 ms  1073 ms  1066 ms  198.233.75.217   6  2705 ms  2161 ms  1614 ms  67.14.8.86   7  1138 ms  1058 ms  1095 ms  216.111.90.126   8  1028 ms  1081 ms  1066 ms  209.85.244.1   9  1103 ms  2488 ms  1078 ms  72.14.237.133  10  1834 ms   635 ms  1080 ms  72.14.232.70  11  1073 ms  1088 ms  1082 ms  72.14.234.81  12     *        *        *     Request timed out.  13   875 ms   798 ms   682 ms  8.8.8.8 For fairness, here is one to google.com, whatever that translated to. Tracing route to google.com [172.217.4.110] over a maximum of 30 hops:   1    <1 ms    <1 ms    <1 ms  192.168.1.1   2    <1 ms     1 ms     1 ms  100.107.182.129   3   649 ms  1325 ms  1330 ms  72.171.194.52   4  1370 ms  1326 ms  1324 ms  72.171.196.58   5  1366 ms  2070 ms   716 ms  198.233.75.217   6   611 ms   707 ms   768 ms  67.14.8.86   7   862 ms   699 ms   733 ms  216.111.90.126   8   733 ms   738 ms   705 ms  108.170.243.225   9  1185 ms  1079 ms   762 ms  108.170.233.111  10   839 ms  1070 ms   779 ms  172.217.4.110 Here is the gateway test when I ran this, so you can see what the current state is.  Obviously, more problems with the gateway would result in higher times for the tracert Packet Loss: 0.00% Average Delay: 919.00 ms Minimum Delay: 610.00 ms Maximum Delay: 1290.00 ms IP Gateway: RAP43HNSIGW72C001Adv This is an unusually good run.  Give it about 20 minutes and let's see if it changes. ... View more

My problem doesn't seem to be of real interest to them. ... View more

Another two Gateway tests Packet Loss: 30.00% Average Delay: 6231.43 ms Minimum Delay: 5020.00 ms Maximum Delay: 6600.00 ms IP Gateway: RAP43HNSIGW72C001Adv Packet Loss: 0.00% Average Delay: 4249.00 ms Minimum Delay: 2880.00 ms Maximum Delay: 5910.00 ms IP Gateway: RAP43HNSIGW72C001Adv The packet loss above seems an anomaly.  But SIX SECOND DELAY getting to the gateway ... View more

I reported this problem more than three months ago (two months for this thread alone) and still nothing? Glad to see my problem is such a high priority for Hughesnet. As noted above, there is an issue with the Gateway as there is very high latency to it. I'd report this to the BBB, but they are useless and you're a monopoly in my area, so I guess I just have to suck it up and live with it.  Too bad for me, huh?  Where else am I going to go? ... View more

I know it's Christmas, but here is my Gateway test for today: Packet Loss: 0.00% Average Delay: 2312.00 ms Minimum Delay: 560.00 ms Maximum Delay: 3890.00 ms IP Gateway: RAP43HNSIGW72B002Adv Outrageous, huh? Web response test: Server Selected: Chicago Ping Time: 6610 ms Download Time 2.4 seconds Speed test: Server Selected: Chicago Ping Time: 3854 ms Download: 28.22 Upload: 0.05 Upload seems a bit slow, doesn't it? ... View more

Here are the primetime traceroutes Tracing route to 67.14.122.6 over a maximum of 30 hops   1    <1 ms    <1 ms    <1 ms  192.168.1.1   2     1 ms    <1 ms    <1 ms  100.107.182.9   3   626 ms  1346 ms  1419 ms  72.171.194.52   4   901 ms  1401 ms  1299 ms  72.171.196.58   5   688 ms   615 ms  1465 ms  198.233.75.217   6     *        *        *     Request timed out.   7     *        *        *     Request timed out.   8  1756 ms   778 ms   730 ms  67.14.122.6 Trace complete. Tracing route to 67.14.122.6 over a maximum of 30 hops   1    <1 ms    <1 ms    <1 ms  192.168.1.1   2     1 ms    <1 ms    <1 ms  100.107.182.9   3  2097 ms   627 ms  1099 ms  72.171.194.52   4  1412 ms  1247 ms  1291 ms  72.171.196.58   5  1864 ms  1597 ms  1250 ms  198.233.75.217   6     *        *        *     Request timed out.   7     *        *        *     Request timed out.   8  1054 ms  1342 ms  1346 ms  67.14.122.6 Trace complete. ... View more

I just ran it again. Tue Dec 20 02:10:55 2016 Packet Loss: 0.00% Average Delay: 1278.00 ms Minimum Delay: 940.00 ms Maximum Delay: 1920.00 ms IP Gateway: RAP43HNSIGW72C001Adv ... View more

Oh, I found the gateway test. Tue Dec 20 01:45:47 2016 Packet Loss: 0.00% Average Delay: 1087.00 ms Minimum Delay: 550.00 ms Maximum Delay: 2320.00 ms IP Gateway: RAP43HNSIGW72C001Adv 2320 ms delay. ... View more

Just for giggles do a gateway test from the modems SSC Huh?  You'll have to walk me through that. then ping google. That I did.  Here are two ping tests for Google. Pinging 8.8.8.8 with 32 bytes of data: Reply from 8.8.8.8: bytes=32 time=870ms TTL=47 Reply from 8.8.8.8: bytes=32 time=924ms TTL=47 Reply from 8.8.8.8: bytes=32 time=999ms TTL=47 Reply from 8.8.8.8: bytes=32 time=1275ms TTL=47 Ping statistics for 8.8.8.8:     Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds:     Minimum = 870ms, Maximum = 1275ms, Average = 1017ms Pinging 8.8.8.8 with 32 bytes of data: Reply from 8.8.8.8: bytes=32 time=619ms TTL=47 Reply from 8.8.8.8: bytes=32 time=976ms TTL=47 Reply from 8.8.8.8: bytes=32 time=2111ms TTL=47 Reply from 8.8.8.8: bytes=32 time=925ms TTL=47 Ping statistics for 8.8.8.8:     Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds:     Minimum = 619ms, Maximum = 2111ms, Average = 1157ms Highest result was 2111 ms. ... View more

Here are my results. Tracing route to 67.14.122.6 over a maximum of 30 hops   1    <1 ms    <1 ms    <1 ms  192.168.1.1   2     1 ms    <1 ms    <1 ms  100.107.182.9   3  1643 ms   817 ms  1032 ms  72.171.194.52   4  1310 ms  1606 ms  1270 ms  72.171.196.58   5  1409 ms   826 ms   616 ms  198.233.75.217   6     *        *        *     Request timed out.   7     *        *        *     Request timed out.   8  1032 ms  2120 ms   738 ms  67.14.122.6 Trace complete. Six times I got a timeout and 6 times response took over 1000ms with a max of 2120ms. I think I'll try running this again during primetime and see if there is a difference. Here are the ping times. Pinging 67.14.122.6 with 32 bytes of data: Reply from 67.14.122.6: bytes=32 time=645ms TTL=59 Reply from 67.14.122.6: bytes=32 time=986ms TTL=59 Reply from 67.14.122.6: bytes=32 time=1313ms TTL=59 Reply from 67.14.122.6: bytes=32 time=1354ms TTL=59 Ping statistics for 67.14.122.6:     Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds:     Minimum = 645ms, Maximum = 1354ms, Average = 1074ms And a second try. Pinging 67.14.122.6 with 32 bytes of data: Reply from 67.14.122.6: bytes=32 time=652ms TTL=59 Reply from 67.14.122.6: bytes=32 time=1345ms TTL=59 Request timed out. Reply from 67.14.122.6: bytes=32 time=683ms TTL=59 Ping statistics for 67.14.122.6:     Packets: Sent = 4, Received = 3, Lost = 1 (25% loss), Approximate round trip times in milli-seconds:     Minimum = 652ms, Maximum = 1345ms, Average = 893ms Notice the timeout. ... View more

8322ms latency tonight. I would be embarrassed to be giving that kind of service, but then that's just me. One day, a competitor will come to our area, and I will remember this incident. ... View more

Trace a traceroute. ... View more