Your Postbot Will Hit GFY Fast at OC3 Networks
 

My new server with OC3 just came online. Very impressive, OC3. :thumbsup

alpha# ping gfy.com
PING gfy.com (64.255.175.11): 56 data bytes
64 bytes from 64.255.175.11: icmp_seq=0 ttl=53 time=13.226 ms
64 bytes from 64.255.175.11: icmp_seq=1 ttl=53 time=12.621 ms
64 bytes from 64.255.175.11: icmp_seq=2 ttl=53 time=12.436 ms
64 bytes from 64.255.175.11: icmp_seq=3 ttl=53 time=12.506 ms
64 bytes from 64.255.175.11: icmp_seq=4 ttl=53 time=12.372 ms
64 bytes from 64.255.175.11: icmp_seq=5 ttl=53 time=12.541 ms
64 bytes from 64.255.175.11: icmp_seq=6 ttl=53 time=12.790 ms
64 bytes from 64.255.175.11: icmp_seq=7 ttl=53 time=12.340 ms
64 bytes from 64.255.175.11: icmp_seq=8 ttl=53 time=12.445 ms
64 bytes from 64.255.175.11: icmp_seq=9 ttl=53 time=12.484 ms
64 bytes from 64.255.175.11: icmp_seq=10 ttl=53 time=12.593 ms
64 bytes from 64.255.175.11: icmp_seq=11 ttl=53 time=13.127 ms
64 bytes from 64.255.175.11: icmp_seq=12 ttl=53 time=12.538 ms
64 bytes from 64.255.175.11: icmp_seq=13 ttl=53 time=12.393 ms
64 bytes from 64.255.175.11: icmp_seq=14 ttl=53 time=12.631 ms
64 bytes from 64.255.175.11: icmp_seq=15 ttl=53 time=12.336 ms
64 bytes from 64.255.175.11: icmp_seq=16 ttl=53 time=12.455 ms
64 bytes from 64.255.175.11: icmp_seq=17 ttl=53 time=12.490 ms
64 bytes from 64.255.175.11: icmp_seq=18 ttl=53 time=12.536 ms
64 bytes from 64.255.175.11: icmp_seq=19 ttl=53 time=12.456 ms
64 bytes from 64.255.175.11: icmp_seq=20 ttl=53 time=12.802 ms
64 bytes from 64.255.175.11: icmp_seq=21 ttl=53 time=13.796 ms
64 bytes from 64.255.175.11: icmp_seq=22 ttl=53 time=12.487 ms
64 bytes from 64.255.175.11: icmp_seq=23 ttl=53 time=12.533 ms

--- gfy.com ping statistics ---
24 packets transmitted, 24 packets received, 0% packet loss
round-trip min/avg/max/stddev = 12.336/12.622/13.796/0.326 ms

alpha# traceroute gfy.com
traceroute to gfy.com (64.255.175.11), 64 hops max, 40 byte packets
1 oc3-colo-lax.oc3networks.com (66.63.160.1) 0.449 ms 0.427 ms 0.411 ms
2 66.63.162.81 (66.63.162.81) 0.505 ms 0.417 ms 0.327 ms
3 204.8.22.33 (204.8.22.33) 10.743 ms 10.838 ms 10.728 ms
4 peakwebconsulting.ge3-8.5.br01.sjo01.pccwbtn.net (63.218.7.22) 11.936 ms 12.030 ms 11.716 ms
5 rtr-1-2.colo.jupiterhosting.com (64.255.167.10) 12.401 ms 12.393 ms 12.499 ms
6 * * *
^C
alpha#

just dont keep doing that....that could be considered something... :winkwink:

madawgz is the resident denial of service expert

respect

Hey, they werent 2 meg packets and I didnt flood... :error

Its a damn fast network, I am impressed. Its even better than my Kansas City stuff and that was pretty damn good.

All I can say: OC3 rocks!

Bummmmmmmp

preety nice

Oc3?That is slow connection.Try oc96 and then you will see real speed hehe

let's see, they are both in california and im sure they share a similar provider.... durr...

watch this!

root@virtual2 [~]# ping theplanet.com
PING theplanet.com (70.87.6.11) 56(84) bytes of data.
64 bytes from www.theplanet.com (70.87.6.11): icmp_seq=0 ttl=247 time=6.33 ms
64 bytes from www.theplanet.com (70.87.6.11): icmp_seq=1 ttl=247 time=6.50 ms

--------------

root@virtual2 [~]# ping xtube.com (main site hosted at ev1servers)
PING xtube.com (209.85.10.120) 56(84) bytes of data.
64 bytes from gphou2-209-85-10-120.ev1.net (209.85.10.120): icmp_seq=0 ttl=58 time=1.41 ms
64 bytes from gphou2-209-85-10-120.ev1.net (209.85.10.120): icmp_seq=1 ttl=58 time=1.50 ms
64 bytes from gphou2-209-85-10-120.ev1.net (209.85.10.120): icmp_seq=2 ttl=58 time=1.48 ms

i bet if you were at jupiter hosting it would be even faster.

it's not a big deal. you are on the same backbone... only two routers in the middle... that's very similar to being in the same LAN... i didn't say oc3 is bad, i've never used them...

good speed