Recommended Tests

Wildblue's new satt is up but they say it won't go online officially till june according to several dealers and even when it does you will have to specificly ask to be moved to one of the new beams and it will cost you a service call so it will take till closer to the end of the year for current users to see any real change. I just dumped wildblue and invested in a hughesnet small buissness system and package with the .98 dish and 2 watt transmitter. I also have the HN7000S modem so I will run and post some pings for those that were interested. Keep in mind it is overcast skies here and spitting snow and there is a light crust of snow on the dish.

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Me>ping www.yahoo.com

Pinging www.yahoo.com [69.147.114.210] with 32 bytes of data:

Reply from 69.147.114.210: bytes=32 time=773ms TTL=48
Reply from 69.147.114.210: bytes=32 time=712ms TTL=49
Reply from 69.147.114.210: bytes=32 time=722ms TTL=49
Reply from 69.147.114.210: bytes=32 time=672ms TTL=48

Ping statistics for 69.147.114.210:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 672ms, Maximum = 773ms, Average = 719ms

C:\Documents and Settings\Me>ping www.pcpitstop.com

Pinging www.pcpitstop.com [64.29.201.21] with 32 bytes of data:

Reply from 64.29.201.21: bytes=32 time=698ms TTL=243
Reply from 64.29.201.21: bytes=32 time=676ms TTL=243
Reply from 64.29.201.21: bytes=32 time=676ms TTL=243
Reply from 64.29.201.21: bytes=32 time=656ms TTL=243

Ping statistics for 64.29.201.21:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 656ms, Maximum = 698ms, Average = 676ms

C:\Documents and Settings\Me>ping www.testmy.net

Pinging www.testmy.net [67.18.179.85] with 32 bytes of data:

Reply from 67.18.179.85: bytes=32 time=660ms TTL=48
Reply from 67.18.179.85: bytes=32 time=719ms TTL=48
Reply from 67.18.179.85: bytes=32 time=699ms TTL=48
Reply from 67.18.179.85: bytes=32 time=678ms TTL=48

Ping statistics for 67.18.179.85:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 660ms, Maximum = 719ms, Average = 689ms

C:\Documents and Settings\Me>
My download speed is suppose to be 1.5 but with the cloud cover and snow it has been running from 300 to 700 but upload stays constant at 280 to 290 and the pings have never been worse than these.

Ty, I have been using this speed test forever and figured I might could help someone along the way if I joined the forums so I decided to give it a shot.

Welcome to the forums zeddlar. Any and ALL information is always welcome. From what I can see it looks like Hughesnet's pings have improved quite a bit over the past year. Now if they could just straighten out those nasty peak time slowdowns.

There I added A sig and filled out a bit of other stuff, I will add more laters. 

No suspicion at all.
 I don't believe any are throttling as all believe. I remember reading somewhere and that (throttling) was an assumption that someone came up with and everyone jumped on it. There has to be control over the system and that is where FAP came in and has been there as long as i can remember. The other control is the limit on what your system is allowed to do (your monthly package) but to get these rates it probably had to be developed on an uncrowded frequency before being implemented. So just like a highway that at times is almost empty your speed will be good and when traffic picks up speeds drop. And if you want more speed you need to change to another highway that can handle it (a higher package).

As far as ping times, there is the distance traveled and nothing can be done to change that except get off satellite. Throttling pings, I don't think so, that data pack of a ping is extremely small. I believe that these "back to normal pings" that you say WildBlue is getting are more than likely the same that they had when the customer base on a beam was low.

I think there are many assumptions and thoughts that more should be given for the price of satellite internet. But that is probably due to maybe having had or using a land based broadband and then using satellite, there is no comparison, they are totally different. Myself having had a phone line at one time and then with nothing else but the satellite will not make that throttling assumption. I get near the package claim, (up to or more) but when traffic gets heavy it slows down like everyone else's. I have learned to work with it, calling tech support and talking to someone that probably has never even installed a system doesn't cut it for me. Besides they have no control on your PC and what lurks inside of it to slow your connection down, the system works.

EDIT: Whoops this is a hughesnet forum Nice pings for sat guys.

I didnt realize this was a hughesnet forum guys, sorry about that