Well I'm back posting after a move from SoDak (and wonderful 8 meg internet) to Wisconsin (and WISP being my only choice) so I was wondering what you guys are seeing from your wisps as far as latency? my download (although looking pathetic) is above advertised:
 ::::::::::.. Download Stats ..::::::::::
Connection is:: 345 Kbps about 0.3 Mbps (tested with 1013 kB)
Download Speed is:: 42 kB/s
Tested From:: http://testmy.net/ (server1)
Test Time:: Thu Aug 04 2005 10:05:09 GMT-0500 (Central Standard Time)
Bottom Line:: 6X faster than 56K 1MB download in 24.38 sec
Diagnosis: Awesome! 20% + : 44.96 % faster than the average for host (227.212)
Validation Link:: http://testmy.net/stats/id-UYEFB5WHL

I'm paying for a 256K circut.

My upload however is rather pathetic:
::::::::::.. Upload Stats ..::::::::::
Connection is:: 6 Kbps about 0 Mbps (tested with 97 kB)
Upload Speed is:: 1 kB/s
Tested From:: http://testmy.net/ (server1)
Test Time:: Thu Aug 04 2005 10:08:13 GMT-0500 (Central Standard Time)
Bottom Line:: 0X faster than 56K 1MB upload in 1024 sec
Diagnosis: May need help : running at only 8.33 % of your hosts average (227.212)
Validation Link:: http://testmy.net/stats/id-QOEVLFK7Y

I"m not sure why, although I'm getting a better antennae either later today or tomorrow so we'll see if that improves. What distresses me is my ping times!
Pinging testmy.net [67.18.179.85] with 32 bytes of data:

Request timed out.
Reply from 67.18.179.85: bytes=32 time=66ms TTL=48
Reply from 67.18.179.85: bytes=32 time=179ms TTL=48
Reply from 67.18.179.85: bytes=32 time=43ms TTL=48
Reply from 67.18.179.85: bytes=32 time=37ms TTL=48
Request timed out.
Request timed out.
Reply from 67.18.179.85: bytes=32 time=289ms TTL=48
Reply from 67.18.179.85: bytes=32 time=192ms TTL=48
Reply from 67.18.179.85: bytes=32 time=190ms TTL=48
Reply from 67.18.179.85: bytes=32 time=153ms TTL=48
Reply from 67.18.179.85: bytes=32 time=133ms TTL=48
Request timed out.
Reply from 67.18.179.85: bytes=32 time=90ms TTL=48
Reply from 67.18.179.85: bytes=32 time=167ms TTL=48
Request timed out.
Reply from 67.18.179.85: bytes=32 time=93ms TTL=48
Reply from 67.18.179.85: bytes=32 time=60ms TTL=48
Reply from 67.18.179.85: bytes=32 time=38ms TTL=48
Reply from 67.18.179.85: bytes=32 time=82ms TTL=48
Reply from 67.18.179.85: bytes=32 time=63ms TTL=48
Reply from 67.18.179.85: bytes=32 time=56ms TTL=48
Reply from 67.18.179.85: bytes=32 time=89ms TTL=48
Reply from 67.18.179.85: bytes=32 time=98ms TTL=48
Reply from 67.18.179.85: bytes=32 time=45ms TTL=48
Reply from 67.18.179.85: bytes=32 time=46ms TTL=48
Reply from 67.18.179.85: bytes=32 time=53ms TTL=48
Reply from 67.18.179.85: bytes=32 time=41ms TTL=48
Reply from 67.18.179.85: bytes=32 time=40ms TTL=48

Ping statistics for 67.18.179.85:
    Packets: Sent = 29, Received = 24, Lost = 5 (17% loss),
Approximate round trip times in milli-seconds:
    Minimum = 37ms, Maximum = 289ms, Average = 97ms
This set which i just did is amazingly fast compared to what I was getting up till now (200-500 ms were average)

I think the dropped packets is mostly due to the signal, but we'll find out.. any help?

Chris

yeah, like i said, we're getting a more powerful directional antenne in a week here, so I'm sure the dropping will fix up- the rest of the equipment is top of the line, good stuff so i'm not worried there, just wondering if there are any other WISP users who have ping times to compare.. I've noticed a heavy back-bone reliance.. for instance my website averages 394ms over 100 but testmy averages 120, both are bad enough to not be able to play my favorite games