Search:  

 
 
   All ForumsHot TopicsGallery






how-to block ads


 
Forums » Satellite Connectivity » WildBlue Satellite » Service is even worse now!(Didn't know it was possible)
Search Topic:
Uniqs:
893
Share Topic:
RSS topic:
toggle:
flat / full
normal / watch
Posting:
Post a:
Post a:
« [NEWS] Wild Blue To Demonstrate 18Mbps Satellite  
AuthorAll Replies


Siryak

join:2005-11-26
·WildBlue

Service is even worse now!(Didn't know it was possible)

Anyone else noticing their service going even farther down hill here lately? I thought the 1100 pings where bad. This is just ridiculous. I can browse faster with dial-up.

Pinging google.com [209.85.171.100] with 32 bytes of data:

Reply from 209.85.171.100: bytes=32 time=1444ms TTL=233
Reply from 209.85.171.100: bytes=32 time=2091ms TTL=233
Reply from 209.85.171.100: bytes=32 time=2083ms TTL=233
Reply from 209.85.171.100: bytes=32 time=2125ms TTL=233
Reply from 209.85.171.100: bytes=32 time=2075ms TTL=233
Reply from 209.85.171.100: bytes=32 time=1679ms TTL=233
Reply from 209.85.171.100: bytes=32 time=1609ms TTL=233
Reply from 209.85.171.100: bytes=32 time=2080ms TTL=233
Reply from 209.85.171.100: bytes=32 time=2106ms TTL=233
Reply from 209.85.171.100: bytes=32 time=1623ms TTL=233

Ping statistics for 209.85.171.100:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1444ms, Maximum = 2125ms, Average = 1891ms


Island Jeff

join:2005-07-18
·WildBlue
·TDS

Still the same double-hop-only network latency here (Winnipeg gateway)

ping -n 10 -w 2000 google.com

Pinging google.com [74.125.45.100] with 32 bytes of data:

Reply from 74.125.45.100: bytes=32 time=1670ms TTL=237
Reply from 74.125.45.100: bytes=32 time=1239ms TTL=237
Reply from 74.125.45.100: bytes=32 time=1234ms TTL=237
Reply from 74.125.45.100: bytes=32 time=1298ms TTL=237
Reply from 74.125.45.100: bytes=32 time=1275ms TTL=237
Reply from 74.125.45.100: bytes=32 time=1281ms TTL=237
Reply from 74.125.45.100: bytes=32 time=1199ms TTL=237
Reply from 74.125.45.100: bytes=32 time=1278ms TTL=237
Reply from 74.125.45.100: bytes=32 time=1240ms TTL=237
Reply from 74.125.45.100: bytes=32 time=1427ms TTL=237

Ping statistics for 74.125.45.100:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1199ms, Maximum = 1670ms, Average = 1314ms
--
Very happy TDS DSL user | Wildblue in Lake Michigan

William
Premium
join:2007-09-22
Washougal, WA


2 edits
reply to Siryak
Seattle gateway.

Pinging google.com [209.85.171.100] with 32 bytes of data:

Request timed out.
Reply from 209.85.171.100: bytes=32 time=1418ms TTL=239
Reply from 209.85.171.100: bytes=32 time=1241ms TTL=239
Reply from 209.85.171.100: bytes=32 time=1237ms TTL=239
Reply from 209.85.171.100: bytes=32 time=1519ms TTL=239
Reply from 209.85.171.100: bytes=32 time=1120ms TTL=239
Reply from 209.85.171.100: bytes=32 time=1398ms TTL=239
Reply from 209.85.171.100: bytes=32 time=1480ms TTL=239
Reply from 209.85.171.100: bytes=32 time=1198ms TTL=239
Reply from 209.85.171.100: bytes=32 time=1200ms TTL=239

Ping statistics for 209.85.171.100:
Packets: Sent = 10, Received = 9, Lost = 1 (10% loss),
Approximate round trip times in milli-seconds:
Minimum = 1120ms, Maximum = 1519ms, Average = 1312ms

===========================================================

Pinging dslreports.com [209.123.109.175] with 32 bytes of data:

Reply from 209.123.109.175: bytes=32 time=780ms TTL=47
Reply from 209.123.109.175: bytes=32 time=1199ms TTL=47
Reply from 209.123.109.175: bytes=32 time=1316ms TTL=47
Reply from 209.123.109.175: bytes=32 time=1479ms TTL=47
Reply from 209.123.109.175: bytes=32 time=1252ms TTL=47
Reply from 209.123.109.175: bytes=32 time=1346ms TTL=47
Reply from 209.123.109.175: bytes=32 time=1359ms TTL=47
Reply from 209.123.109.175: bytes=32 time=1359ms TTL=47
Reply from 209.123.109.175: bytes=32 time=1398ms TTL=47
Reply from 209.123.109.175: bytes=32 time=1279ms TTL=47

Ping statistics for 209.123.109.175:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 780ms, Maximum = 1479ms, Average = 1276ms

===========================================================
My website.

Pinging wmcintosh.com [66.206.84.40] with 32 bytes of data:

Reply from 66.206.84.40: bytes=32 time=1226ms TTL=48
Reply from 66.206.84.40: bytes=32 time=1232ms TTL=48
Reply from 66.206.84.40: bytes=32 time=1239ms TTL=48
Reply from 66.206.84.40: bytes=32 time=1359ms TTL=48
Reply from 66.206.84.40: bytes=32 time=727ms TTL=48
Reply from 66.206.84.40: bytes=32 time=1183ms TTL=48
Reply from 66.206.84.40: bytes=32 time=1579ms TTL=48
Reply from 66.206.84.40: bytes=32 time=1399ms TTL=48
Reply from 66.206.84.40: bytes=32 time=1478ms TTL=48
Reply from 66.206.84.40: bytes=32 time=1123ms TTL=48

Ping statistics for 66.206.84.40:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 727ms, Maximum = 1579ms, Average = 1254ms


Earth Signal
Earthsignal
Premium
join:2002-10-03
Burlington, IA
·WildBlue

reply to Siryak
Winnipeg Gateway

C:\Documents and Settings\Ron>ping -n 20 -w 8000 12.213.112.60

Pinging 12.213.112.60 with 32 bytes of data:

Reply from 12.213.112.60: bytes=32 time=1121ms TTL=57
Reply from 12.213.112.60: bytes=32 time=1238ms TTL=57
Reply from 12.213.112.60: bytes=32 time=1202ms TTL=57
Reply from 12.213.112.60: bytes=32 time=2840ms TTL=57
Reply from 12.213.112.60: bytes=32 time=1295ms TTL=57
Reply from 12.213.112.60: bytes=32 time=1157ms TTL=57
Reply from 12.213.112.60: bytes=32 time=1079ms TTL=57
Reply from 12.213.112.60: bytes=32 time=1172ms TTL=57
Reply from 12.213.112.60: bytes=32 time=1309ms TTL=57
Reply from 12.213.112.60: bytes=32 time=1480ms TTL=57
Reply from 12.213.112.60: bytes=32 time=1119ms TTL=57
Reply from 12.213.112.60: bytes=32 time=1320ms TTL=57
Reply from 12.213.112.60: bytes=32 time=1127ms TTL=57
Reply from 12.213.112.60: bytes=32 time=1190ms TTL=57
Reply from 12.213.112.60: bytes=32 time=1200ms TTL=57
Reply from 12.213.112.60: bytes=32 time=1287ms TTL=57
Reply from 12.213.112.60: bytes=32 time=1118ms TTL=57
Reply from 12.213.112.60: bytes=32 time=1122ms TTL=57
Reply from 12.213.112.60: bytes=32 time=1117ms TTL=57
Reply from 12.213.112.60: bytes=32 time=1312ms TTL=57

Ping statistics for 12.213.112.60:
Packets: Sent = 20, Received = 20, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1079ms, Maximum = 2840ms, Average = 1290ms
--
Ron ~ Wildblue Select Pak since 01-2006, Anik F2 Beam 26, service through NRTC, Dell XPS, 2Gig Ram, XP Pro, Router DD-WRT- WRT54GL, Laptop, XP home

mrpepsi

join:2006-05-22
·WildBlue

reply to Siryak
Pinging google.com [209.85.171.100] with 32 bytes of data:

Reply from 209.85.171.100: bytes=32 time=2986ms TTL=237
Reply from 209.85.171.100: bytes=32 time=1829ms TTL=237
Reply from 209.85.171.100: bytes=32 time=2034ms TTL=237
Reply from 209.85.171.100: bytes=32 time=1825ms TTL=237

Ping statistics for 209.85.171.100:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1825ms, Maximum = 2986ms, Average = 2168ms

If I hadn't seen a screenshot I took from the days of 600ms pings on Wildblue, I'd think it was all just a dream....
--
Wildblue
Cheyenne : Beam 34


Island Jeff

join:2005-07-18
Related?
»www.wildblue.cc/wbforums/showthr···ost75019


N4ST
Jim
Premium
join:2005-11-25
Jersey, VA
·WildBlue

reply to Siryak

Pinging google.com [74.125.45.100] with 32 bytes of data:

Reply from 74.125.45.100: bytes=32 time=1709ms TTL=238
Reply from 74.125.45.100: bytes=32 time=1512ms TTL=238
Reply from 74.125.45.100: bytes=32 time=1419ms TTL=238
Reply from 74.125.45.100: bytes=32 time=757ms TTL=238
Reply from 74.125.45.100: bytes=32 time=3047ms TTL=238
Reply from 74.125.45.100: bytes=32 time=1316ms TTL=238
Reply from 74.125.45.100: bytes=32 time=2482ms TTL=238
Reply from 74.125.45.100: bytes=32 time=812ms TTL=238
Reply from 74.125.45.100: bytes=32 time=1366ms TTL=238
Reply from 74.125.45.100: bytes=32 time=1627ms TTL=238

Ping statistics for 74.125.45.100:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 757ms, Maximum = 3047ms, Average = 1604ms
--
Anik F2 | WildBlue Pro Pak | Beam 37 | Laredo NOC | Since Nov 2005 | Linksys WRT54GX-v2| Windows XP | Homebrew PC
-
Forums » Satellite Connectivity » WildBlue Satellite« [NEWS] Wild Blue To Demonstrate 18Mbps Satellite  


Sunday, 06-Dec 09:33:00 Terms of Use | Privacy Policy | Hosting by www.nac.net - DSL,Hosting & Co-lo | feedback | contact
over 10 years online! © 1999-2009 dslreports.com.republican-creole
page compression OFF
Most commented news this week
· [163] Comcast Releasing Promised Usage Meter
· [147] Avast Antivirus Has Gone Mad
· [128] Comcast Makes NBC Universal Acquisition Official
· [126] The Bandwidth Hog Does Not Exist
· [105] Graduate Student Unveils Sprint's GPS Sharing With Feds
· [101] Google Invades ISP, OpenDNS Turf With Google Public DNS
· [85] FCC Ponders Moving From PSTN To IP Voice
· [82] Latest Consumer Reports Survey Not Kind To AT&T
· [81] New Bill Aims To Limit ETFs
· [75] Sprint Defuses GPS Privacy Media Bomb
Most people now reading
· Wife might have to work in.... Iowa for a few months!!! [General Questions]
· [DNS] Google's public DNS... performance increases? [Comcast HSI]
· Problems with rlslog.net? [TekSavvy]
· Windows 7 boot manager editing questions [Microsoft Help]
· Bulb for garage door opener [Home Repair & Improvement]
· [Newsgroups] Newzleech down? [Filesharing Software]
· False positive in Avast! or is it real? [Security]
· Connecting to Google Voice Via SIP [VOIP Tech Chat]
· [WotLK] Stats required to tank heroics? [World of Warcraft]
· Is Usenet targettable under ACTA? [TekSavvy]