Could anyone ping this ip for me, I need as many results as possible

66.232.17.130

Thanks

C:\>ping 66.232.17.130

Pinging 66.232.17.130 with 32 bytes of data:

Reply from 66.232.17.130: bytes=32 time=110ms TTL=246
Reply from 66.232.17.130: bytes=32 time=120ms TTL=246
Reply from 66.232.17.130: bytes=32 time=111ms TTL=246
Reply from 66.232.17.130: bytes=32 time=110ms TTL=246

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

C:\>

This is what I am getting, I'm trying for more results

C:\>ping -n 15 66.232.17.130

Pinging 66.232.17.130 with 32 bytes of data:

Reply from 66.232.17.130: bytes=32 time=134ms TTL=229
Reply from 66.232.17.130: bytes=32 time=130ms TTL=229
Reply from 66.232.17.130: bytes=32 time=130ms TTL=229
Reply from 66.232.17.130: bytes=32 time=125ms TTL=229
Reply from 66.232.17.130: bytes=32 time=130ms TTL=229
Reply from 66.232.17.130: bytes=32 time=130ms TTL=229
Request timed out.
Reply from 66.232.17.130: bytes=32 time=130ms TTL=229
Reply from 66.232.17.130: bytes=32 time=130ms TTL=229
Request timed out.
Request timed out.
Reply from 66.232.17.130: bytes=32 time=130ms TTL=229
Reply from 66.232.17.130: bytes=32 time=130ms TTL=229
Request timed out.
Reply from 66.232.17.130: bytes=32 time=130ms TTL=229

Ping statistics for 66.232.17.130:
Packets: Sent = 15, Received = 11, Lost = 4 (26% loss),
Approximate round trip times in milli-seconds:
Minimum = 125ms, Maximum = 134ms, Average = 129ms

From Australia: :rolleyes:

C:\>ping 66.232.17.130

Pinging 66.232.17.130 with 32 bytes of data:

Reply from 66.232.17.130: bytes=32 time=250ms TTL=235
Reply from 66.232.17.130: bytes=32 time=250ms TTL=235
Reply from 66.232.17.130: bytes=32 time=234ms TTL=235
Reply from 66.232.17.130: bytes=32 time=234ms TTL=235

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

In addition to my report you can get multiple ping results from:
http://www.tracert.com/cgi-bin/ping.pl
(check off the last three US based sites)

I'd say there is nothing special about the network access of the IP address you provided. Most perform better. Traceroute from here provides some clues as to why.

From Vancouver BC via DSL

bsd# ping 66.232.17.130
PING 66.232.17.130 (66.232.17.130): 56 data bytes
64 bytes from 66.232.17.130: icmp_seq=0 ttl=237 time=112.513 ms
64 bytes from 66.232.17.130: icmp_seq=1 ttl=237 time=111.314 ms
64 bytes from 66.232.17.130: icmp_seq=2 ttl=237 time=111.013 ms
64 bytes from 66.232.17.130: icmp_seq=3 ttl=237 time=110.116 ms
64 bytes from 66.232.17.130: icmp_seq=4 ttl=237 time=111.105 ms
64 bytes from 66.232.17.130: icmp_seq=5 ttl=237 time=111.637 ms
64 bytes from 66.232.17.130: icmp_seq=6 ttl=237 time=110.817 ms
64 bytes from 66.232.17.130: icmp_seq=7 ttl=237 time=113.465 ms
64 bytes from 66.232.17.130: icmp_seq=8 ttl=237 time=112.268 ms
64 bytes from 66.232.17.130: icmp_seq=11 ttl=237 time=111.224 ms
64 bytes from 66.232.17.130: icmp_seq=14 ttl=237 time=111.234 ms
64 bytes from 66.232.17.130: icmp_seq=17 ttl=237 time=111.197 ms
64 bytes from 66.232.17.130: icmp_seq=18 ttl=237 time=110.852 ms
64 bytes from 66.232.17.130: icmp_seq=19 ttl=237 time=110.512 ms
64 bytes from 66.232.17.130: icmp_seq=20 ttl=237 time=110.343 ms

64 bytes from 66.232.17.130: icmp_seq=21 ttl=237 time=110.154 ms
^C
--- 66.232.17.130 ping statistics ---
22 packets transmitted, 16 packets received, 27% packet loss
round-trip min/avg/max/stddev = 110.116/111.235/113.465/0.865 ms

Note the packet loss. That was also noted from two other locations in the US

FROM www.his.com TO 66.232.17.130.

PING 66.232.17.130 (66.232.17.130): 56 data bytes
64 bytes from 66.232.17.130: icmp_seq=0 ttl=239 time=99.341 ms
64 bytes from 66.232.17.130: icmp_seq=1 ttl=239 time=97.489 ms
64 bytes from 66.232.17.130: icmp_seq=2 ttl=239 time=97.672 ms
64 bytes from 66.232.17.130: icmp_seq=3 ttl=239 time=97.603 ms

--- 66.232.17.130 ping statistics ---
5 packets transmitted, 4 packets received, 20% packet loss
round-trip min/avg/max = 97.489/98.026/99.341 ms

Pinging from Iserv Co. (Grand Rapids, MI)

PING 66.232.17.130 (66.232.17.130): 56 data bytes
64 bytes from 66.232.17.130: icmp_seq=0 ttl=240 time=99.6 ms
64 bytes from 66.232.17.130: icmp_seq=1 ttl=240 time=82.1 ms
64 bytes from 66.232.17.130: icmp_seq=2 ttl=240 time=90.0 ms
64 bytes from 66.232.17.130: icmp_seq=3 ttl=240 time=132.0 ms

--- 66.232.17.130 ping statistics ---
5 packets transmitted, 4 packets received, 20% packet loss
round-trip min/avg/max = 82.1/100.9/132.0 ms

Yep, I just used that link you provided, very useful,



PING 66.232.17.130 (66.232.17.130): 56 data bytes
64 bytes from 66.232.17.130: icmp_seq=0 ttl=226 time=99.005 ms
64 bytes from 66.232.17.130: icmp_seq=1 ttl=226 time=98.087 ms
64 bytes from 66.232.17.130: icmp_seq=2 ttl=226 time=97.987 ms
64 bytes from 66.232.17.130: icmp_seq=4 ttl=226 time=98.162 ms

--- 66.232.17.130 ping statistics ---
5 packets transmitted, 4 packets received, 20% packet loss
round-trip min/avg/max/stddev = 97.987/98.310/99.005/0.406 ms

Can you tell me what the problem is here as my site is so slow

Use that same tool to compare to some others...

Here's one example:

www.datapipe.com - note that you will be pinging two servers, one on each coast.

FROM www.his.com TO www.datapipe.com.

PING www.datapipe.com (66.70.68.254): 56 data bytes
64 bytes from 66.70.68.254: icmp_seq=0 ttl=245 time=8.555 ms
64 bytes from 66.70.68.254: icmp_seq=1 ttl=245 time=9.18 ms
64 bytes from 66.70.68.254: icmp_seq=2 ttl=245 time=9.511 ms
64 bytes from 66.70.68.254: icmp_seq=3 ttl=245 time=9.129 ms
64 bytes from 66.70.68.254: icmp_seq=4 ttl=245 time=9.661 ms

--- www.datapipe.com ping statistics ---
5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max = 8.555/9.207/9.661 ms

Pinging 66.232.17.130 with 32 bytes of data:

Reply from 66.232.17.130: bytes=32 time=50ms TTL=237
Reply from 66.232.17.130: bytes=32 time=60ms TTL=237
Reply from 66.232.17.130: bytes=32 time=60ms TTL=237
Reply from 66.232.17.130: bytes=32 time=60ms TTL=237

Ping statistics for 66.232.17.130:
Packets: Sent = 4, Received = 4, Lost = 0 (0% lo
Approximate round trip times in milli-seconds:
Minimum = 50ms, Maximum = 60ms, Average = 57ms

From my home computer using Road Runner with Time Warner Cable in central Texas:

$ ping 66.232.17.130
PING 66.232.17.130 (66.232.17.130) from 24.26.203.165 : 56(84) bytes of data.
64 bytes from 66.232.17.130: icmp_seq=0 ttl=236 time=58.483 msec
64 bytes from 66.232.17.130: icmp_seq=1 ttl=236 time=59.743 msec
64 bytes from 66.232.17.130: icmp_seq=2 ttl=236 time=59.968 msec
64 bytes from 66.232.17.130: icmp_seq=3 ttl=236 time=59.968 msec

--- 66.232.17.130 ping statistics ---
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max/mdev = 58.483/59.540/59.968/0.663 ms



From my server in the Ardent Communications data center in McLean, Virginia:

# ping 66.232.17.130
PING 66.232.17.130 (66.232.17.130) from 206.161.201.2 : 56(84) bytes of data.
64 bytes from 66.232.17.130: icmp_seq=0 ttl=242 time=35.365 msec
64 bytes from 66.232.17.130: icmp_seq=1 ttl=242 time=34.363 msec
64 bytes from 66.232.17.130: icmp_seq=2 ttl=242 time=34.586 msec
64 bytes from 66.232.17.130: icmp_seq=3 ttl=242 time=34.591 msec

--- 66.232.17.130 ping statistics ---
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max/mdev = 34.363/34.726/35.365/0.402 ms



Not bad if you ask me.

From Singapore, in my lab, using an ATM connection:

C:\>ping 66.232.17.130

Pinging 66.232.17.130 with 32 bytes of data:

Reply from 66.232.17.130: bytes=32 time=384ms TTL=232
Reply from 66.232.17.130: bytes=32 time=419ms TTL=232
Reply from 66.232.17.130: bytes=32 time=435ms TTL=232
Reply from 66.232.17.130: bytes=32 time=436ms TTL=232

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

:eek:

Pinging 66.232.17.130 with 32 bytes of data:

Reply from 66.232.17.130: bytes=32 time=1137ms TTL=236
Reply from 66.232.17.130: bytes=32 time=558ms TTL=236
Reply from 66.232.17.130: bytes=32 time=572ms TTL=236
Reply from 66.232.17.130: bytes=32 time=379ms TTL=236

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

D:\Documents and Settings\Administrator>

:bawling: Gotta love that Centurytel DSL line. :bawling:

From a real connection:


64 bytes from 66.232.17.130: icmp_seq=28 ttl=240 time=61.094 msec
64 bytes from 66.232.17.130: icmp_seq=29 ttl=240 time=63.913 msec
64 bytes from 66.232.17.130: icmp_seq=30 ttl=240 time=61.759 msec
64 bytes from 66.232.17.130: icmp_seq=31 ttl=240 time=60.815 msec
64 bytes from 66.232.17.130: icmp_seq=32 ttl=240 time=61.132 msec
64 bytes from 66.232.17.130: icmp_seq=33 ttl=240 time=61.035 msec

From Michigan on a Cable modem connection:

C:\>ping 66.232.17.130

Pinging 66.232.17.130 with 32 bytes of data:

Reply from 66.232.17.130: bytes=32 time=108ms TTL=233
Reply from 66.232.17.130: bytes=32 time=130ms TTL=233
Reply from 66.232.17.130: bytes=32 time=110ms TTL=233
Reply from 66.232.17.130: bytes=32 time=114ms TTL=233

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

Thanks guys, but all seems to be working now.

Thankyou