how-to block ads
|
 Review by jm 
UPDATED: 255 days ago
member for 6.1 years, 1961 visits, last login: 54 days ago
 Graceville,Jackson,FL
 Contract price not specified.
 "Speeds pretty good"
 "TERRIBLE LATENCY.. 1100MS OR HIGHER!!!"
 "If you're out in the middle of nowhere, then I would might recommend WB."
| Pre Sales information:
Install Co-ordination:
Connection reliability:
Tech Support:
Mail,DNS,News:
Value for money:
(ratings match consensus)
|
9/20/05
I had my WB installed on 9-1-05. The installer was late by 2 hours because they got held up at the previous install, it wasn't a big deal but a call from them would have been nice. I did call the installers office, they were quick to tell me that he was delayed.
Once on site they were pretty quick to run the cable and setup the dish. Total on site time was no more than 1:15.
Speed have been as promised, 1mb/200k.
:::.. Download Stats ..:::
Connection is:: 1030 Kbps about 1 Mbps (tested with 2992 kB)
Download Speed is:: 126 kB/s
Tested From:: »testmy.net/ (server2)
Test Time:: Tue Sep 20 2005 11:27:47 GMT-0500 (Central Daylight Time)
Bottom Line:: 18X faster than 56K 1MB download in 8.13 sec
Diagnosis: 90% + Okay : running at 97.35 % of your hosts average (210.140)
Validation Link:: »testmy.net/stats/id-2VWMNYRD5
:::.. Upload Stats ..:::
Connection is:: 184 Kbps about 0.2 Mbps (tested with 1013 kB)
Upload Speed is:: 22 kB/s
Tested From:: »testmy.net/ (server2)
Test Time:: Tue Sep 20 2005 11:29:40 GMT-0500 (Central Daylight Time)
Bottom Line:: 3X faster than 56K 1MB upload in 46.55 sec
Diagnosis: 90% + Okay : running at 100 % of your hosts average (210.140)
Validation Link:: »testmy.net/stats/id-CQZAN6JYH
Pings Have been as expected.
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\>ping -n 10 yahoo.com
Pinging yahoo.com [66.94.234.13] with 32 bytes of data:
Reply from 66.94.234.13: bytes=32 time=993ms TTL=46
Reply from 66.94.234.13: bytes=32 time=629ms TTL=46
Reply from 66.94.234.13: bytes=32 time=631ms TTL=46
Reply from 66.94.234.13: bytes=32 time=629ms TTL=46
Reply from 66.94.234.13: bytes=32 time=626ms TTL=46
Reply from 66.94.234.13: bytes=32 time=661ms TTL=46
Reply from 66.94.234.13: bytes=32 time=613ms TTL=46
Reply from 66.94.234.13: bytes=32 time=696ms TTL=46
Reply from 66.94.234.13: bytes=32 time=626ms TTL=46
Reply from 66.94.234.13: bytes=32 time=622ms TTL=46
Ping statistics for 66.94.234.13:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 613ms, Maximum = 993ms, Average = 672ms
Currently I am sharing my connection thru a Linksys wireless router with total of three pcs.
******************************************************
3/24/2006
Speeds are still good as promised.
I had an ongoing issue for about 3 months. Problem was with the mobo in my modem. It had some short in it or something, if you moved the modem it would lose power. Normally this wasn't an issue as you rarely have to move the modem. It only became an issue when my beam would go down. I would then have to power cycle my modem and router. Once I determined that the issue was not on my end I would call WB support. They would report that the beam is down. I would say ok, but I have a problem with my modem, which loses power. Their response would always be "we can't escalate because its a known beam issue". Which under normal circumstances would be fine, but I knew this was a problem with the modem. Usually I didn't push it with them, and just went along.
I did get the call escalated 3 times. The first time it got escalated, 2 days later one of their support guys called me and canceled the call to my local NRTC. He explained that it was a beam issue, so they wouldn't be replacing the modem. I tried explaining that I DID have a modem issue however. But he wasn't listening. The second, they local guy came out and replaced the Tria. I told him that the problem was with the modem. He said we'll see what happens with this new tria. The third time I got the call escalated and finally had the modem replaced. This was just this week. The escalation took place like 3 weeks ago, but I had to leave town for work.
Now I can move the modem without it losing power.
:::.. Download Stats ..:::
Connection is:: 1062 Kbps about 1.1 Mbps (tested with 2992 kB)
Download Speed is:: 130 kB/s
Tested From:: »testmy.net (main)
Test Time:: 2006/03/24 - 9:40pm
Bottom Line:: 19X faster than 56K 1MB Download in 7.88 sec
Tested from a 2992 kB file and took 23.078 seconds to complete
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.1) Gecko/20060111 Firefox/1.5.0.1
Diagnosis: May need help : running at only 88.94 % of your hosts average (wildblue.net)
Validation Link:: »testmy.net/stats/id-OMQ2JTCYG
:::.. Upload Stats ..:::
Connection is:: 140 Kbps about 0.1 Mbps (tested with 1496 kB)
Upload Speed is:: 17 kB/s
Tested From:: »testmy.net (main)
Test Time:: 2006/03/24 - 9:44pm
Bottom Line:: 2X faster than 56K 1MB Upload in 60.24 sec
Tested from a 1496 kB file and took 87.84 seconds to complete
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.1) Gecko/20060111 Firefox/1.5.0.1
Diagnosis: Looks Great : 16.67 % faster than the average for host (wildblue.net)
Validation Link:: »testmy.net/stats/id-6GUBZ1K45
C:\Documents and Settings\>ping -n 10 google.com
Pinging google.com [72.14.207.99] with 32 bytes of data:
Reply from 72.14.207.99: bytes=32 time=1166ms TTL=236
Reply from 72.14.207.99: bytes=32 time=1025ms TTL=236
Reply from 72.14.207.99: bytes=32 time=742ms TTL=236
Reply from 72.14.207.99: bytes=32 time=832ms TTL=236
Reply from 72.14.207.99: bytes=32 time=770ms TTL=236
Reply from 72.14.207.99: bytes=32 time=669ms TTL=236
Reply from 72.14.207.99: bytes=32 time=795ms TTL=236
Reply from 72.14.207.99: bytes=32 time=845ms TTL=236
Reply from 72.14.207.99: bytes=32 time=749ms TTL=236
Reply from 72.14.207.99: bytes=32 time=707ms TTL=236
**********************************************************
2-25-09
Speeds have been good, BUT....
My latency is TERRIBLE!!
I now average 1100ms or higher. Below are a few samples of pings and speeds. Every time I call WB they just blow me off. Their answer is "there is latency associated with satellite"... Like no kidding! My issue is that latency has doubled from when I 1st got the service.
I have to use remote desktop applications alot for my work, and the latency makes it unbearable. Almost like being on dialup.
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\jose>ping -n 10 google.com
Pinging google.com [209.85.171.100] with 32 bytes of data:
Reply from 209.85.171.100: bytes=32 time=1202ms TTL=235
Reply from 209.85.171.100: bytes=32 time=1953ms TTL=235
Reply from 209.85.171.100: bytes=32 time=1227ms TTL=235
Reply from 209.85.171.100: bytes=32 time=1433ms TTL=235
Reply from 209.85.171.100: bytes=32 time=2597ms TTL=235
Reply from 209.85.171.100: bytes=32 time=4159ms TTL=235
Reply from 209.85.171.100: bytes=32 time=1435ms TTL=235
Reply from 209.85.171.100: bytes=32 time=1339ms TTL=235
Reply from 209.85.171.100: bytes=32 time=1217ms TTL=235
Reply from 209.85.171.100: bytes=32 time=1126ms TTL=235
Ping statistics for 209.85.171.100:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1126ms, Maximum = 4159ms, Average = 1768ms
C:\Documents and Settings\jose>ping -n 10 google.com
Pinging google.com [74.125.67.100] with 32 bytes of data:
Reply from 74.125.67.100: bytes=32 time=1077ms TTL=239
Reply from 74.125.67.100: bytes=32 time=1227ms TTL=239
Reply from 74.125.67.100: bytes=32 time=1843ms TTL=239
Reply from 74.125.67.100: bytes=32 time=1227ms TTL=239
Reply from 74.125.67.100: bytes=32 time=1226ms TTL=239
Reply from 74.125.67.100: bytes=32 time=1331ms TTL=239
Reply from 74.125.67.100: bytes=32 time=1227ms TTL=239
Reply from 74.125.67.100: bytes=32 time=2969ms TTL=239
Reply from 74.125.67.100: bytes=32 time=1228ms TTL=239
Reply from 74.125.67.100: bytes=32 time=1331ms TTL=239
Ping statistics for 74.125.67.100:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1077ms, Maximum = 2969ms, Average = 1468ms
1554/47
1548/74
1584/125
1543/95
Followup comments:  darkmagic
join:2009-02-17
Waterville, VT | Re sounds like wb isn't much better than hughes. | |
| 
Earth Signal
Earthsignal
Premium
join:2002-10-03
Burlington, IA | The latency changed in 2007 The latency changed in 2007 and your just now noticing it? | |
| |
jm
join:2003-09-21
Graceville, FL | Re: The latency changed in 2007 I noticed it along time ago, its just to the point where it is unbearable now. | |
| | | |
| Forums » comments on review of WildBlue |
|
|
WildBlue
(16)
(42)
(34)