dslreports logo
 
    All Forums Hot Topics Gallery
spc
uniqs
32

Gamer831
@direcway.com

Gamer831 to Doc Lithius

Anon

to Doc Lithius

Re: [Networking] Online Gaming on HughesNet

Has anyone tested out the new plans for gaming? HughesNet released the Express 200,300,500 they have 512kbps and 1024 kbps of upload speeds
zeddlar
join:2007-04-09
Jay, OK

zeddlar

Member

Well I am on the power 200 or the express 200 plan, not sure because I upgraded from the small business package and not sure whether they recommisioned me as a small business or a residential customer but the plans are the same speeds and FAP either way and I recieve my plan speeds or better pretty much 24 hours a day. The FAP is advertised at 400 MB but I get 550 MB. Once in a while during prime time my speeds fall to 1.3 to 1.6 MB but not every day.



Doc Lithius
join:2009-08-19
Rock, MI

Doc Lithius

Member

You know something? If it wasn't for the price, it might be worth my time to upgrade to one of the modern plans. That's a pretty decent connection speed, right there! But then again... is it any more stable? Rather, does it have any less jitter than the old plans? ("Jitter", for those who don't know, basically means "inconsistent ping results" such as "750ms -> 912ms -> 891ms -> 519ms -> 1024ms" vs. "600ms -> 605ms -> 591ms -> 600ms -> 599ms".)
Lightwell
join:2010-10-21
US

Lightwell

Member

Ya im curious about this as well. But im not sure if i could convince myself to upgrade or just stick it out until an alternative is offered here.
zeddlar
join:2007-04-09
Jay, OK

zeddlar

Member

Still has the jitter, I will post some pings tomorrow, 2 am here and I am beat.
zeddlar

zeddlar

Member

Here are those pings not sure what is up, these are the worst pings i have ever gotten.

Pinging testmy.net [174.120.187.140] with 32 bytes of data:
Reply from 174.120.187.140: bytes=32 time=1393ms TTL=47
Reply from 174.120.187.140: bytes=32 time=1847ms TTL=47
Reply from 174.120.187.140: bytes=32 time=1128ms TTL=47
Reply from 174.120.187.140: bytes=32 time=1118ms TTL=47
Reply from 174.120.187.140: bytes=32 time=1238ms TTL=47
Reply from 174.120.187.140: bytes=32 time=1118ms TTL=47
Reply from 174.120.187.140: bytes=32 time=1238ms TTL=47
Reply from 174.120.187.140: bytes=32 time=1118ms TTL=47
Reply from 174.120.187.140: bytes=32 time=1238ms TTL=47
Reply from 174.120.187.140: bytes=32 time=1218ms TTL=47

Pinging any-fp.wa1.b.yahoo.com [98.137.149.56] with 32 bytes of data:
Reply from 98.137.149.56: bytes=32 time=1216ms TTL=51
Reply from 98.137.149.56: bytes=32 time=1028ms TTL=51
Reply from 98.137.149.56: bytes=32 time=1228ms TTL=51
Reply from 98.137.149.56: bytes=32 time=1228ms TTL=51
Reply from 98.137.149.56: bytes=32 time=1128ms TTL=51
Reply from 98.137.149.56: bytes=32 time=1228ms TTL=51
Reply from 98.137.149.56: bytes=32 time=1128ms TTL=51
Reply from 98.137.149.56: bytes=32 time=1238ms TTL=51
Reply from 98.137.149.56: bytes=32 time=1748ms TTL=51
Reply from 98.137.149.56: bytes=32 time=1841ms TTL=51

Ping statistics for 98.137.149.56:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1028ms, Maximum = 1841ms, Average = 1301ms