A 1GB unshaped account. Possible from 1 Nov?

S

Syzygy78

Senior Member
Joined
Jun 26, 2004
Messages
605
Reaction score
23
Location
.
Hey hey!

Are there any ISP's out there that will offer 1GB unshaped accounts from the 1st of Nov 2005?

If so, what will the pricing be?

On a side note... whats better, a VPN or an unshaped ADSL account? Would anyone be kind enough to post say a few ping tests? I would like the following I.P. pinged if possible: 66.94.234.13. Its a yahoo server somewhere on the west coast of the U.S.

Thanks,
Syzygy78
 
Syzygy78 said:
Hey hey!

Are there any ISP's out there that will offer 1GB unshaped accounts from the 1st of Nov 2005?

If so, what will the pricing be?

On a side note... whats better, a VPN or an unshaped ADSL account? Would anyone be kind enough to post say a few ping tests? I would like the following I.P. pinged if possible: 66.94.234.13. Its a yahoo server somewhere on the west coast of the U.S.

Thanks,
Syzygy78
Click to expand...
What's better for what?
 
bwana v.3 said:
What's better for what?
Click to expand...

for latency...

Neio, would you be able to paste your results here if possible?

Thanks,
Syzygy
 
C:\Documents and Settings\**>ping 66.94.234.13 -t

Pinging 66.94.234.13 with 32 bytes of data:

Reply from 66.94.234.13: bytes=32 time=479ms TTL=47
Reply from 66.94.234.13: bytes=32 time=510ms TTL=47
Reply from 66.94.234.13: bytes=32 time=486ms TTL=47
Reply from 66.94.234.13: bytes=32 time=888ms TTL=47
Reply from 66.94.234.13: bytes=32 time=681ms TTL=47
Reply from 66.94.234.13: bytes=32 time=632ms TTL=47
Reply from 66.94.234.13: bytes=32 time=643ms TTL=47
Reply from 66.94.234.13: bytes=32 time=590ms TTL=47
Reply from 66.94.234.13: bytes=32 time=622ms TTL=47
Reply from 66.94.234.13: bytes=32 time=631ms TTL=47
Reply from 66.94.234.13: bytes=32 time=615ms TTL=47
Reply from 66.94.234.13: bytes=32 time=590ms TTL=47
Reply from 66.94.234.13: bytes=32 time=462ms TTL=47

Ping statistics for 66.94.234.13:
Packets: Sent = 13, Received = 13, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 462ms, Maximum = 888ms, Average = 602ms
Control-C
^C
 
PING 66.94.234.13 (66.94.234.13): 56 data bytes
64 bytes from 66.94.234.13: icmp_seq=0 ttl=48 time=447.013 ms
64 bytes from 66.94.234.13: icmp_seq=1 ttl=48 time=441.725 ms
64 bytes from 66.94.234.13: icmp_seq=2 ttl=48 time=447.932 ms
64 bytes from 66.94.234.13: icmp_seq=3 ttl=48 time=445.160 ms
64 bytes from 66.94.234.13: icmp_seq=4 ttl=48 time=441.492 ms
64 bytes from 66.94.234.13: icmp_seq=5 ttl=48 time=445.012 ms
64 bytes from 66.94.234.13: icmp_seq=6 ttl=48 time=443.829 ms
64 bytes from 66.94.234.13: icmp_seq=7 ttl=48 time=444.941 ms
64 bytes from 66.94.234.13: icmp_seq=8 ttl=48 time=446.907 ms
64 bytes from 66.94.234.13: icmp_seq=9 ttl=48 time=442.370 ms

--- 66.94.234.13 ping statistics ---
10 packets transmitted, 10 packets received, 0% packet loss
round-trip min/avg/max/stddev = 441.492/444.638/447.932/2.152 ms

This is shaped
 
thanks ;P

Im also on a shaped account at work. I get the following:

Pinging 66.94.234.13 with 32 bytes of data:

Reply from 66.94.234.13: bytes=32 time=419ms TTL=47
Reply from 66.94.234.13: bytes=32 time=419ms TTL=47
Reply from 66.94.234.13: bytes=32 time=417ms TTL=47
Reply from 66.94.234.13: bytes=32 time=420ms TTL=47
Reply from 66.94.234.13: bytes=32 time=419ms TTL=47
Reply from 66.94.234.13: bytes=32 time=420ms TTL=47
Reply from 66.94.234.13: bytes=32 time=425ms TTL=47
Reply from 66.94.234.13: bytes=32 time=420ms TTL=47
Reply from 66.94.234.13: bytes=32 time=421ms TTL=47
Reply from 66.94.234.13: bytes=32 time=418ms TTL=47

Ping statistics for 66.94.234.13:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 417ms, Maximum = 425ms, Average = 419ms

Id really like to see how a VPN or an unshaped ADSL account performs. If anyone could do a test for me, id really appreciate it! Please make a note if its through a VPN or if its an unshaped account.

Thanks for the results!

Syzygy
 
Our unshaped vpn:

PING 66.94.234.13 (66.94.234.13): 56 data bytes
64 bytes from 66.94.234.13: icmp_seq=0 ttl=48 time=318.073 ms
64 bytes from 66.94.234.13: icmp_seq=1 ttl=48 time=323.191 ms
64 bytes from 66.94.234.13: icmp_seq=2 ttl=48 time=315.259 ms
64 bytes from 66.94.234.13: icmp_seq=3 ttl=48 time=320.137 ms
64 bytes from 66.94.234.13: icmp_seq=4 ttl=48 time=316.823 ms
64 bytes from 66.94.234.13: icmp_seq=5 ttl=48 time=316.552 ms
64 bytes from 66.94.234.13: icmp_seq=6 ttl=48 time=316.135 ms
64 bytes from 66.94.234.13: icmp_seq=7 ttl=48 time=321.117 ms
64 bytes from 66.94.234.13: icmp_seq=8 ttl=48 time=315.086 ms
64 bytes from 66.94.234.13: icmp_seq=9 ttl=48 time=318.922 ms
64 bytes from 66.94.234.13: icmp_seq=10 ttl=48 time=322.156 ms
64 bytes from 66.94.234.13: icmp_seq=11 ttl=48 time=320.012 ms
64 bytes from 66.94.234.13: icmp_seq=12 ttl=48 time=318.347 ms
--- 66.94.234.13 ping statistics ---
13 packets transmitted, 13 packets received, 0% packet loss
round-trip min/avg/max/stddev = 315.086/318.601/323.191/2.508 ms



Depending on time of day, international go via different international gateways, so at best of time that would be between 250-270ms.
 
erm, these pings are all http pings, right? wont these pings be greatly different if used on different ports?

*EDIT* I obviously am refering to the shaped accounts. I assume Clipse's unshaped vpn stuff will be constant no matter what port.
 
yep icmp is unshaped on shaped/unshaped networks, so ingame on shaped it would be alot higher, in the thousands I presume.
 
with loads of packet loss, which is the real killer of online gaming...
 
Clipse said:
Our unshaped vpn:

PING 66.94.234.13 (66.94.234.13): 56 data bytes
64 bytes from 66.94.234.13: icmp_seq=0 ttl=48 time=318.073 ms
64 bytes from 66.94.234.13: icmp_seq=1 ttl=48 time=323.191 ms
64 bytes from 66.94.234.13: icmp_seq=2 ttl=48 time=315.259 ms
64 bytes from 66.94.234.13: icmp_seq=3 ttl=48 time=320.137 ms
64 bytes from 66.94.234.13: icmp_seq=4 ttl=48 time=316.823 ms
64 bytes from 66.94.234.13: icmp_seq=5 ttl=48 time=316.552 ms
64 bytes from 66.94.234.13: icmp_seq=6 ttl=48 time=316.135 ms
64 bytes from 66.94.234.13: icmp_seq=7 ttl=48 time=321.117 ms
64 bytes from 66.94.234.13: icmp_seq=8 ttl=48 time=315.086 ms
64 bytes from 66.94.234.13: icmp_seq=9 ttl=48 time=318.922 ms
64 bytes from 66.94.234.13: icmp_seq=10 ttl=48 time=322.156 ms
64 bytes from 66.94.234.13: icmp_seq=11 ttl=48 time=320.012 ms
64 bytes from 66.94.234.13: icmp_seq=12 ttl=48 time=318.347 ms
--- 66.94.234.13 ping statistics ---
13 packets transmitted, 13 packets received, 0% packet loss
round-trip min/avg/max/stddev = 315.086/318.601/323.191/2.508 ms



Depending on time of day, international go via different international gateways, so at best of time that would be between 250-270ms.
Click to expand...

/me has ping envy

Thats a nice ping ;p Thanks for posting that info Clipse.

Anyone on an unshaped ADSL package that could try a test?

Many thanks,
Syzygy
 
Pinging 66.94.234.13 with 32 bytes of data:

Reply from 66.94.234.13: bytes=32 time=394ms TTL=44
Reply from 66.94.234.13: bytes=32 time=390ms TTL=44
Reply from 66.94.234.13: bytes=32 time=372ms TTL=44
Reply from 66.94.234.13: bytes=32 time=414ms TTL=44
Reply from 66.94.234.13: bytes=32 time=410ms TTL=44
Reply from 66.94.234.13: bytes=32 time=356ms TTL=44
Reply from 66.94.234.13: bytes=32 time=384ms TTL=44
Reply from 66.94.234.13: bytes=32 time=387ms TTL=44
Reply from 66.94.234.13: bytes=32 time=390ms TTL=44
Reply from 66.94.234.13: bytes=32 time=370ms TTL=44
Reply from 66.94.234.13: bytes=32 time=366ms TTL=44
Reply from 66.94.234.13: bytes=32 time=388ms TTL=44
Reply from 66.94.234.13: bytes=32 time=433ms TTL=44
Reply from 66.94.234.13: bytes=32 time=369ms TTL=44
Reply from 66.94.234.13: bytes=32 time=401ms TTL=44
Reply from 66.94.234.13: bytes=32 time=503ms TTL=44

Ping statistics for 66.94.234.13:
Packets: Sent = 16, Received = 16, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 356ms, Maximum = 503ms, Average = 395ms

This is from the Internet Solutions 256kbps Diginet line at work during lunchhour (worst time to test)
 
Last edited:
Saix Unshaped:

Pinging 66.94.234.13 with 32 bytes of data:

Reply from 66.94.234.13: bytes=32 time=351ms TTL=47
Reply from 66.94.234.13: bytes=32 time=344ms TTL=47
Reply from 66.94.234.13: bytes=32 time=373ms TTL=47
Reply from 66.94.234.13: bytes=32 time=344ms TTL=47
Reply from 66.94.234.13: bytes=32 time=351ms TTL=47
Reply from 66.94.234.13: bytes=32 time=344ms TTL=47
Reply from 66.94.234.13: bytes=32 time=343ms TTL=47
Reply from 66.94.234.13: bytes=32 time=346ms TTL=47

Ping statistics for 66.94.234.13:
Packets: Sent = 8, Received = 8, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 343ms, Maximum = 373ms, Average = 349ms


VPN Unshaped (previous was latency at busiest time of day, this is latency at best time of day):

PING 66.94.234.13 (66.94.234.13): 56 data bytes
64 bytes from 66.94.234.13: icmp_seq=0 ttl=46 time=263.530 ms
64 bytes from 66.94.234.13: icmp_seq=1 ttl=46 time=266.247 ms
64 bytes from 66.94.234.13: icmp_seq=2 ttl=46 time=256.183 ms
64 bytes from 66.94.234.13: icmp_seq=3 ttl=46 time=279.936 ms
64 bytes from 66.94.234.13: icmp_seq=4 ttl=46 time=261.664 ms
64 bytes from 66.94.234.13: icmp_seq=5 ttl=46 time=284.389 ms
64 bytes from 66.94.234.13: icmp_seq=6 ttl=46 time=257.928 ms
--- 66.94.234.13 ping statistics ---
7 packets transmitted, 7 packets received, 0% packet loss
round-trip min/avg/max/stddev = 256.183/267.125/284.389/10.071 ms
 
Pinging 66.94.234.13 with 32 bytes of data:

Reply from 66.94.234.13: bytes=32 time=536ms TTL=47
Reply from 66.94.234.13: bytes=32 time=467ms TTL=47
Reply from 66.94.234.13: bytes=32 time=444ms TTL=47
Reply from 66.94.234.13: bytes=32 time=442ms TTL=47
Reply from 66.94.234.13: bytes=32 time=440ms TTL=47
Reply from 66.94.234.13: bytes=32 time=440ms TTL=47
Reply from 66.94.234.13: bytes=32 time=531ms TTL=47
Reply from 66.94.234.13: bytes=32 time=481ms TTL=47
Reply from 66.94.234.13: bytes=32 time=547ms TTL=47
Reply from 66.94.234.13: bytes=32 time=453ms TTL=47
Reply from 66.94.234.13: bytes=32 time=520ms TTL=47
Reply from 66.94.234.13: bytes=32 time=471ms TTL=47
Reply from 66.94.234.13: bytes=32 time=487ms TTL=47
Reply from 66.94.234.13: bytes=32 time=456ms TTL=47
Reply from 66.94.234.13: bytes=32 time=458ms TTL=47
Reply from 66.94.234.13: bytes=32 time=442ms TTL=47
Reply from 66.94.234.13: bytes=32 time=452ms TTL=47
Reply from 66.94.234.13: bytes=32 time=444ms TTL=47
Reply from 66.94.234.13: bytes=32 time=561ms TTL=47

Ping statistics for 66.94.234.13:
Packets: Sent = 19, Received = 19, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 440ms, Maximum = 561ms, Average = 477ms

This is frm my DSL192 account at home using a shaped 20gig account from Imaginet also during lunchhour (got nothing to do with anything, but I was connected via remote desktop and also downloading some stuff)
 
thx Clipse... those are some awesome pings there!!!

thanks alot for the tests... seems like the VPN is most certainly the way to go!

awesome...

Syzygy
 
ping on ISDN from home...

Pinging 66.94.234.13 with 32 bytes of data:

Reply from 66.94.234.13: bytes=32 time=347ms TTL=54
Reply from 66.94.234.13: bytes=32 time=349ms TTL=54
Reply from 66.94.234.13: bytes=32 time=348ms TTL=54
Reply from 66.94.234.13: bytes=32 time=350ms TTL=54
Reply from 66.94.234.13: bytes=32 time=356ms TTL=54
Reply from 66.94.234.13: bytes=32 time=348ms TTL=54
Reply from 66.94.234.13: bytes=32 time=351ms TTL=54
Reply from 66.94.234.13: bytes=32 time=353ms TTL=54
Reply from 66.94.234.13: bytes=32 time=358ms TTL=54
Reply from 66.94.234.13: bytes=32 time=351ms TTL=54

Ping statistics for 66.94.234.13:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 347ms, Maximum = 358ms, Average = 351ms
 
Sorry, I just HAD to post my Sentech 128k pings :D

Pinging 66.94.234.13 with 32 bytes of data:

Request timed out.
Reply from 66.94.234.13: bytes=32 time=681ms TTL=49
Reply from 66.94.234.13: bytes=32 time=540ms TTL=49
Reply from 66.94.234.13: bytes=32 time=559ms TTL=49
Request timed out.
Request timed out.
Reply from 66.94.234.13: bytes=32 time=681ms TTL=49
Reply from 66.94.234.13: bytes=32 time=539ms TTL=49
Reply from 66.94.234.13: bytes=32 time=557ms TTL=49
Request timed out.
Reply from 66.94.234.13: bytes=32 time=681ms TTL=49
Reply from 66.94.234.13: bytes=32 time=540ms TTL=49
Reply from 66.94.234.13: bytes=32 time=579ms TTL=49
Reply from 66.94.234.13: bytes=32 time=678ms TTL=49
Reply from 66.94.234.13: bytes=32 time=556ms TTL=49
Reply from 66.94.234.13: bytes=32 time=535ms TTL=49
Reply from 66.94.234.13: bytes=32 time=665ms TTL=49

Ping statistics for 66.94.234.13:
Packets: Sent = 17, Received = 13, Lost = 4 (23% loss),
Approximate round trip times in milli-seconds:
Minimum = 535ms, Maximum = 681ms, Average = 599ms

Just look at that packet loss.
I wonder what they would be like through a VPN...
 
Pinging 66.94.234.13 with 32 bytes of data:

Reply from 66.94.234.13: bytes=32 time=343ms TTL=41
Reply from 66.94.234.13: bytes=32 time=340ms TTL=40
Reply from 66.94.234.13: bytes=32 time=339ms TTL=40
Reply from 66.94.234.13: bytes=32 time=370ms TTL=41

Ping statistics for 66.94.234.13:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 339ms, Maximum = 370ms, Average = 348ms
 
EchoZA said:
Pinging 66.94.234.13 with 32 bytes of data:

Reply from 66.94.234.13: bytes=32 time=343ms TTL=41
Reply from 66.94.234.13: bytes=32 time=340ms TTL=40
Reply from 66.94.234.13: bytes=32 time=339ms TTL=40
Reply from 66.94.234.13: bytes=32 time=370ms TTL=41

Ping statistics for 66.94.234.13:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 339ms, Maximum = 370ms, Average = 348ms
Click to expand...

Are you using Nukecap?

Those Sentech pings look awful :\

Syzygy
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X