Web Hosting Talk : Advertising Forums : Community Reviews : Other Reviews : Help ping a site

[DT-Spirit]

Hi, if you have time, can you help me ping a site and tell me your location? Thanks I don't know is it my ISP is slow or the server is slow, that's why I need your help. Please help me ping gamerzplanet.net

THanks..

[Mrdredd]

Reply from 64.191.13.210: bytes=32 time=70ms TTL=46
Reply from 64.191.13.210: bytes=32 time=60ms TTL=46
Reply from 64.191.13.210: bytes=32 time=60ms TTL=46

^ Nocster

Those pings came from South FL

[peersignal]

Reply from 64.191.13.210: bytes=32 time=96ms TTL=49
Reply from 64.191.13.210: bytes=32 time=96ms TTL=49
Reply from 64.191.13.210: bytes=32 time=96ms TTL=49
Reply from 64.191.13.210: bytes=32 time=97ms TTL=49

These are results from Riverside, California.

Regards,
Waylon

[joshiee]

From Burst:

64 bytes from raine.raine-tech.com (64.191.13.210): icmp_seq=1 ttl=63 time=0.527 ms
64 bytes from raine.raine-tech.com (64.191.13.210): icmp_seq=2 ttl=63 time=0.527 ms
64 bytes from raine.raine-tech.com (64.191.13.210): icmp_seq=3 ttl=63 time=0.554 ms
64 bytes from raine.raine-tech.com (64.191.13.210): icmp_seq=4 ttl=63 time=0.499 ms



From So California as well:

Reply from 64.191.13.210: bytes=32 time=153ms TTL=50
Reply from 64.191.13.210: bytes=32 time=244ms TTL=50
Reply from 64.191.13.210: bytes=32 time=174ms TTL=50
Reply from 64.191.13.210: bytes=32 time=213ms TTL=50

Which brings me to the question.. Velostream which ISP are you on? Makes that big of a difference in ping times when we're not too far away..

[The Dude]

I cant ping this either!

There was another user aksing us to ping his site,i couldnt do that either!!!!!

Ne1 else on Earthlink Cable??? Can you ping this??????

I get Request timed out (IS it possible for the ISP to block OUTGOING ping requests???)

The Dude

[peersignal]

Originally posted by joshiee
From Burst:

64 bytes from raine.raine-tech.com (64.191.13.210): icmp_seq=1 ttl=63 time=0.527 ms
64 bytes from raine.raine-tech.com (64.191.13.210): icmp_seq=2 ttl=63 time=0.527 ms
64 bytes from raine.raine-tech.com (64.191.13.210): icmp_seq=3 ttl=63 time=0.554 ms
64 bytes from raine.raine-tech.com (64.191.13.210): icmp_seq=4 ttl=63 time=0.499 ms



From So California as well:

Reply from 64.191.13.210: bytes=32 time=153ms TTL=50
Reply from 64.191.13.210: bytes=32 time=244ms TTL=50
Reply from 64.191.13.210: bytes=32 time=174ms TTL=50
Reply from 64.191.13.210: bytes=32 time=213ms TTL=50

Which brings me to the question.. Velostream which ISP are you on? Makes that big of a difference in ping times when we're not too far away..

I'm not sure who the direct provider is, as I was pinging from a computer on the University of California, Riverside's network here at work.

[DT-Spirit]

Reply from 64.191.13.210: bytes=32 time=109ms TTL=47
Reply from 64.191.13.210: bytes=32 time=111ms TTL=47
Reply from 64.191.13.210: bytes=32 time=135ms TTL=47
Reply from 64.191.13.210: bytes=32 time=138ms TTL=47

I got this myself..
Is this high already?

[anon-e-mouse]

From Central Australia.

Pinging 64.191.13.210 with 32 bytes of data:

Reply from 64.191.13.210: bytes=32 time=371ms TTL=44
Reply from 64.191.13.210: bytes=32 time=371ms TTL=44
Reply from 64.191.13.210: bytes=32 time=370ms TTL=44
Reply from 64.191.13.210: bytes=32 time=371ms TTL=44

Ping statistics for 64.191.13.210:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:

[t c]

From Eastcoast (VA), United States

Pinging gamerzplanet.net [64.191.13.210] with 32 bytes of data:

Reply from 64.191.13.210: bytes=32 time=235ms TTL=50
Reply from 64.191.13.210: bytes=32 time=234ms TTL=50
Reply from 64.191.13.210: bytes=32 time=227ms TTL=50
Reply from 64.191.13.210: bytes=32 time=229ms TTL=50

Ping statistics for 64.191.13.210:
- Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:
- Minimum = 227ms, Maximum = 235ms, Average = 231ms

[Fatty]

From the UK, Scotland:

Reply from 64.191.13.210: bytes=32 time=125ms TTL=50
Reply from 64.191.13.210: bytes=32 time=125ms TTL=50
Reply from 64.191.13.210: bytes=32 time=125ms TTL=50
Reply from 64.191.13.210: bytes=32 time=125ms TTL=50

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

[Scar]

Ping from he.net:
PING gamerzplanet.net (64.191.13.210) : 56(84) bytes of data.
64 bytes from raine.raine-tech.com (64.191.13.210): icmp_seq=0 ttl=53 time=87.086 msec
64 bytes from raine.raine-tech.com (64.191.13.210): icmp_seq=1 ttl=53 time=90.287 msec
64 bytes from raine.raine-tech.com (64.191.13.210): icmp_seq=2 ttl=53 time=86.604 msec
64 bytes from raine.raine-tech.com (64.191.13.210): icmp_seq=3 ttl=53 time=90.772 msec
64 bytes from raine.raine-tech.com (64.191.13.210): icmp_seq=4 ttl=53 time=86.581 msec
--- gamerzplanet.net ping statistics ---
5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max/mdev = 86.581/88.266/90.772/1.863 ms

Ping from romania:
PING gamerzplanet.net (64.191.13.210): 56 octets data
64 octets from 64.191.13.210: icmp_seq=0 ttl=49 time=129.6 ms
64 octets from 64.191.13.210: icmp_seq=1 ttl=49 time=134.4 ms
64 octets from 64.191.13.210: icmp_seq=2 ttl=49 time=136.8 ms
64 octets from 64.191.13.210: icmp_seq=3 ttl=49 time=137.2 ms
64 octets from 64.191.13.210: icmp_seq=4 ttl=49 time=143.0 ms

--- gamerzplanet.net ping statistics ---
5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max = 129.6/136.2/143.0 ms