 1 edit | reply to rkeyes
Re: slowdown in peak hours Use forum search to find my observations of the degrading service over the past several years. I used to think I just ended up with a bum system, but now several of my neighbors have Wildblue as well and suffer from the exact same issues as myself.
We have formed an informal support group. Rather than calling Wildblue and getting inane responses, we work together to figure out whether the problem is us, or them.
Like Friday, I believe, when our beam was down for about 5 hours. Wildblue support had us all rebooting our modems untill we called each other and found out we were all offline.
Very frustrating... |
|
 | said by mrpepsi:Use forum search to find my observations of the degrading service It may be best to have your dish aligned...your previous "stats,"
I don't so much of have prime time slowdowns, as prime time blackouts...
Pinging google.com [209.85.171.100] with 32 bytes of data:
suggest/indicate your TX is not a strong signal at satellite.
During prime time, a weaker receive signal at satellite may not be seen....your ping stats, and your prime time blackouts...suggest this strongly. Notice my ping stats, which are consistent in time responses:
C:\Users\Internet>ping google.com
Pinging google.com [74.125.67.100] with 32 bytes of data:
Reply from 74.125.67.100: bytes=32 time=1163ms TTL=47
Reply from 74.125.67.100: bytes=32 time=1364ms TTL=47
Reply from 74.125.67.100: bytes=32 time=1418ms TTL=47
Reply from 74.125.67.100: bytes=32 time=1310ms TTL=47
Ping statistics for 74.125.67.100:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1163ms, Maximum = 1418ms, Average = 1313ms
|
|
 1 edit | I've had a LOT of time to try and figure out the issues with Wildblue, and in my area there are dozens and dozens of individuals using satellite internet from Wildblue, Hughesnet, Skyway, and Starband.
I've had my signal tested by the installer and Wildblue themselves claim it to be just fine.
The issues with my setup are also mirrored with every one of my neighbors who share the same beam, satellite (Anik) etc. For all of us to experience the same slowdowns at the same times, and outages at the same times, I'm inclined to believe it has to be that we are simply on an overcrowded beam.
I will admit that one of my neighbors is on WB1 and experiences slightly better performance, and has outages at different times from the rest of us. The WB1 pointed neighbor generally has pings of 1800-2000ms during peak and has tested to rarely drop below 50% of the bandwidth he pays for.
My neighbors who have Hughesnet 7000 also have these wild fluctuations between peak and non-peak, though latency rarely averages above 1500ms. My Hughesnet 9000 neighbors are generally the least affected by peak times.
I truly believe that Wildblue can work great if your on a less populated beam. I remember the days of 600ms latency and 110% bandwidth...but for my beam at least...those days are but a vague memory.
So my advice is to check with people in your area who have Wildblue and see how bad it is.
I just hope that at some point in the future 3G or at the very least sub 1000ms latency satellite will be available and affordable (under $100 a month) for all of us. It's incredibly frustrating paying bills during the summer... The kids in my area are all out of school and when I get off work it's peaktime.  -- Wildblue Cheyenne : Beam 34 |
|
 | reply to mrpepsi said by mrpepsi:....my advice is to check with people in your area Two posters over at Wildblue.CC indicate Beam 34 is working OK previously:
Chris: Beam 34 has been fine for me.
and
lhookins: ...having pretty good luck with download speeds on Cheyenne beam 34.
Btw...from one of your previous posts:
Pinging google.com [209.85.171.100] with 32 bytes of data:
I could not get that address to come up...and it appeared to be from state of Washington......it's a Google address....but normally, when you insert numeric IP address into web browswer, something comes up....Also, this IP address "times out." Not a good address to PING....try some other sites to ping, and post your results....
Btw, if you post on Wildblue's Forum, I'm sure they can get to bottom of your problem...as they say there, "And if that doesn't work, PM me with your first/last name and phone number on Monday and I'll take a look at your account." |
|
 2 edits | Edit:
Thanks DrStrangeLove, I had no idea there was an official Wildblue forum. I'll give them a try! |
|