66.232.22.74

&

216.52.184.238


And please, tell me where are you located.

120ms from FastServers

66.232.22.74 256ms
216.52.184.238 206ms

location : Melb, Aus

ping from EU:
66.232.22.74 - 184ms
216.52.184.238 - 211ms
average from 100 packets.

66.232.22.74 - average is 63MS
216.52.184.238 - average 0.300MS

This is from the hostmania/transoptics datacenter.

66.232.22.74 - 103ms
216.52.184.238 - 62ms

Both done from a 768k Verizon DSL line, outside Seattle, WA

Originally posted by apollo
120ms from FastServers

120ms for both ips?

T-Online 768/128k ADSL Line in Germany:

--- 66.232.22.74 ping statistics ---
100 packets transmitted, 100 packets received, 0% packet loss
round-trip min/avg/max/std-dev = 145.388/148.827/202.294/5.856 ms

(second, just to check if these spikes to 202ms are normal, which doesn't seem so, though)

--- 66.232.22.74 ping statistics ---
100 packets transmitted, 100 packets received, 0% packet loss
round-trip min/avg/max/std-dev = 145.480/148.253/161.754/2.044 ms

--- 216.52.184.238 ping statistics ---
100 packets transmitted, 100 packets received, 0% packet loss
round-trip min/avg/max/std-dev = 152.736/155.244/161.681/1.325 ms

RoadRunner Cable - Huntington Beach, California:

Pinging 66.232.22.74 with 32 bytes of data:

Reply from 66.232.22.74: bytes=32 time=93ms TTL=236
Reply from 66.232.22.74: bytes=32 time=88ms TTL=236
Reply from 66.232.22.74: bytes=32 time=87ms TTL=236
Reply from 66.232.22.74: bytes=32 time=87ms TTL=236

Ping statistics for 66.232.22.74:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 87ms, Maximum = 93ms, Average = 88ms
_______________________________________________

Pinging 216.52.184.238 with 32 bytes of data:

Reply from 216.52.184.238: bytes=32 time=66ms TTL=235
Reply from 216.52.184.238: bytes=32 time=67ms TTL=235
Reply from 216.52.184.238: bytes=32 time=65ms TTL=235
Reply from 216.52.184.238: bytes=32 time=64ms TTL=235

Ping statistics for 216.52.184.238:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 64ms, Maximum = 67ms, Average = 65ms

From nc.rr.com:


C:\WINDOWS>ping -n 10 216.52.184.238

Pinging 216.52.184.238 with 32 bytes of data:

Reply from 216.52.184.238: bytes=32 time=54ms TTL=237
Reply from 216.52.184.238: bytes=32 time=48ms TTL=237
Reply from 216.52.184.238: bytes=32 time=46ms TTL=237
Reply from 216.52.184.238: bytes=32 time=47ms TTL=237
Reply from 216.52.184.238: bytes=32 time=50ms TTL=237
Reply from 216.52.184.238: bytes=32 time=48ms TTL=237
Reply from 216.52.184.238: bytes=32 time=49ms TTL=237
Reply from 216.52.184.238: bytes=32 time=49ms TTL=237
Reply from 216.52.184.238: bytes=32 time=48ms TTL=237
Reply from 216.52.184.238: bytes=32 time=48ms TTL=237

Ping statistics for 216.52.184.238:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 46ms, Maximum = 54ms, Average = 48ms




C:\WINDOWS>ping -n 10 66.232.22.74

Pinging 66.232.22.74 with 32 bytes of data:

Reply from 66.232.22.74: bytes=32 time=48ms TTL=235
Reply from 66.232.22.74: bytes=32 time=38ms TTL=235
Reply from 66.232.22.74: bytes=32 time=50ms TTL=235
Reply from 66.232.22.74: bytes=32 time=46ms TTL=235
Reply from 66.232.22.74: bytes=32 time=41ms TTL=235
Reply from 66.232.22.74: bytes=32 time=48ms TTL=235
Reply from 66.232.22.74: bytes=32 time=46ms TTL=235
Reply from 66.232.22.74: bytes=32 time=41ms TTL=235
Reply from 66.232.22.74: bytes=32 time=41ms TTL=235
Reply from 66.232.22.74: bytes=32 time=45ms TTL=235

Ping statistics for 66.232.22.74:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 38ms, Maximum = 50ms, Average = 44ms


-B

Northern Minnesota. (Very close to Canada.)

mncable.net hosted.

Ping statistics for 216.52.184.238:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 64ms, Maximum = 76ms, Average = 68ms

-and-

Ping statistics for 216.52.184.238:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 64ms, Maximum = 76ms, Average = 68ms

C:\>ping 66.232.22.74

Pinging 66.232.22.74 with 32 bytes of data:

Reply from 66.232.22.74: bytes=32 time=63ms TTL=238
Reply from 66.232.22.74: bytes=32 time=32ms TTL=238
Reply from 66.232.22.74: bytes=32 time=32ms TTL=238
Reply from 66.232.22.74: bytes=32 time=32ms TTL=238

Ping statistics for 66.232.22.74:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 32ms, Maximum = 63ms, Average = 39ms

C:\>ping 216.52.184.238

Pinging 216.52.184.238 with 32 bytes of data:

Reply from 216.52.184.238: bytes=32 time=78ms TTL=241
Reply from 216.52.184.238: bytes=32 time=31ms TTL=242
Reply from 216.52.184.238: bytes=32 time=31ms TTL=242
Reply from 216.52.184.238: bytes=32 time=47ms TTL=242

Ping statistics for 216.52.184.238:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 31ms, Maximum = 78ms, Average = 46ms

Border of NYC.

I hope you know that you can't get a lot of information with pings ....

Yes i know FHDAVe, but for the info i want ping is enough! ;)

Here locally (Kentucky). Bellsouth

ping 216.52.184.238

Pinging 216.52.184.238 with 32 bytes of data:

Reply from 216.52.184.238: bytes=32 time=90ms TTL=240
Reply from 216.52.184.238: bytes=32 time=60ms TTL=241
Reply from 216.52.184.238: bytes=32 time=110ms TTL=241
Reply from 216.52.184.238: bytes=32 time=60ms TTL=241

Ping statistics for 216.52.184.238:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 60ms, Maximum = 110ms, Average = 80ms

C:\>ping 66.232.22.74

Pinging 66.232.22.74 with 32 bytes of data:

Reply from 66.232.22.74: bytes=32 time=80ms TTL=235
Reply from 66.232.22.74: bytes=32 time=81ms TTL=235
Reply from 66.232.22.74: bytes=32 time=80ms TTL=235
Reply from 66.232.22.74: bytes=32 time=80ms TTL=235

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

Pinging 66.232.22.74 with 32 bytes of data:

Reply from 66.232.22.74: bytes=32 time=259ms TTL=229
Reply from 66.232.22.74: bytes=32 time=260ms TTL=229
Reply from 66.232.22.74: bytes=32 time=258ms TTL=229
Reply from 66.232.22.74: bytes=32 time=259ms TTL=229

Ping statistics for 66.232.22.74:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss)
Approximate round trip times in milli-seconds:
Minimum = 258ms, Maximum = 260ms, Average = 259ms


Hi guys,

What does ping do? bigger or smaller no. better?

Just another newbie:D

http://alice.eng.level3.net/traceroute/traceroute.cgi

ping results... go there... sweetass place... :D

Ping statistics for 66.232.22.74:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 80ms, Maximum = 90ms, Average = 87ms

Ping statistics for 216.52.184.238:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 30ms, Maximum = 50ms, Average = 40ms

thanks folks!

Originally posted by dominet


120ms for both ips?

Sorry forgot to ping another IP you had in your list. Pinging from FastServers

# ping -c 10 216.52.184.238
PING 216.52.184.238 (216.52.184.238) from 66.220.28.164 : 56(84) bytes of data.
64 bytes from 216.52.184.238: icmp_seq=0 ttl=241 time=51.162 msec
64 bytes from 216.52.184.238: icmp_seq=1 ttl=242 time=49.427 msec
64 bytes from 216.52.184.238: icmp_seq=2 ttl=242 time=49.407 msec
64 bytes from 216.52.184.238: icmp_seq=3 ttl=242 time=49.395 msec
64 bytes from 216.52.184.238: icmp_seq=4 ttl=242 time=49.935 msec
64 bytes from 216.52.184.238: icmp_seq=5 ttl=242 time=49.391 msec
64 bytes from 216.52.184.238: icmp_seq=6 ttl=242 time=49.334 msec
64 bytes from 216.52.184.238: icmp_seq=7 ttl=242 time=49.218 msec
64 bytes from 216.52.184.238: icmp_seq=8 ttl=242 time=49.658 msec
64 bytes from 216.52.184.238: icmp_seq=9 ttl=242 time=49.644 msec

--- 216.52.184.238 ping statistics ---
10 packets transmitted, 10 packets received, 0% packet loss
round-trip min/avg/max/mdev = 49.218/49.657/51.162/0.547 ms

From an Adelphia cable modem (in New Hampshire):

66.232.22.74:
5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max = 100.8/102.7/103.9 ms

216.52.184.238:
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max = 91.4/94.0/99.2 ms

From Palo Alto, Calfornia:

66.232.22.74: 96ms
216.52.184.238: 57ms

From S. SF, CA USA via RCN Cable:

Pinging 66.232.22.74 with 32 bytes of data:

Reply from 66.232.22.74: bytes=32 time=80ms TTL=242
Reply from 66.232.22.74: bytes=32 time=80ms TTL=242
Reply from 66.232.22.74: bytes=32 time=80ms TTL=242
Reply from 66.232.22.74: bytes=32 time=81ms TTL=242

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

--

Pinging 216.52.184.238 with 32 bytes of data:

Reply from 216.52.184.238: bytes=32 time=50ms TTL=242
Reply from 216.52.184.238: bytes=32 time=51ms TTL=243
Reply from 216.52.184.238: bytes=32 time=50ms TTL=243
Reply from 216.52.184.238: bytes=32 time=50ms TTL=243

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

=

Location: Pottstown, Pennsylvania, USA

66.232.22.74
Reply from 66.232.22.74: bytes=32 time=65ms TTL=231
Reply from 66.232.22.74: bytes=32 time=53ms TTL=231
Reply from 66.232.22.74: bytes=32 time=54ms TTL=231


216.52.184.238
Reply from 216.52.184.238: bytes=32 time=50 TTL=233
Reply from 216.52.184.238: bytes=32 time=47 TTL=234
Reply from 216.52.184.238: bytes=32 time=59 TTL=234