Please PING this IP

Rod

Rod

Administrator
Staff member
Joined
Jan 4, 2001
Messages
10,775
Location
5D
First Name
Todd
Please post your ping results for this IP: 204.157.9.189
Also, please post your location.

If you don't know what that means, don't worry about it, just ignore this topic. :)

Thanks,
Rod
 
Round trip time to 204.157.9.189: 34 ms
Round trip time to 204.157.9.189: 34 ms
Round trip time to 204.157.9.189: 34 ms
Round trip time to 204.157.9.189: 34 ms
Round trip time to 204.157.9.189: 34 ms
Round trip time to 204.157.9.189: 34 ms
Round trip time to 204.157.9.189: 34 ms
Round trip time to 204.157.9.189: 34 ms
Timed out

From Bayern Germany (DSL 2000)

*edit* try 2 with a different ping tool...

Pinging 204.157.9.189 [204.157.9.189]:

Ping #1: Got reply from 204.157.9.189 in 1.6ms [TTL=59]
Ping #2: Got reply from 204.157.9.189 in 1.4ms [TTL=59]
Ping #3: Got reply from 204.157.9.189 in 1.6ms [TTL=59]
Ping #4: Got reply from 204.157.9.189 in 1.4ms [TTL=59]

Done pinging 204.157.9.189!
 
Cox Cable in Omaha

Pinging 204.157.9.189 with 32 bytes of data:

Reply from 204.157.9.189: bytes=32 time=65ms TTL=51
Reply from 204.157.9.189: bytes=32 time=66ms TTL=51
Reply from 204.157.9.189: bytes=32 time=65ms TTL=51
Reply from 204.157.9.189: bytes=32 time=66ms TTL=51

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

asgard:~ andrew$ ping 204.157.9.189
PING 204.157.9.189 (204.157.9.189): 56 data bytes
64 bytes from 204.157.9.189: icmp_seq=0 ttl=55 time=15.652 ms
64 bytes from 204.157.9.189: icmp_seq=1 ttl=55 time=15.716 ms
64 bytes from 204.157.9.189: icmp_seq=2 ttl=55 time=15.744 ms
64 bytes from 204.157.9.189: icmp_seq=3 ttl=55 time=15.686 ms
64 bytes from 204.157.9.189: icmp_seq=4 ttl=55 time=15.567 ms
64 bytes from 204.157.9.189: icmp_seq=5 ttl=55 time=15.610 ms
64 bytes from 204.157.9.189: icmp_seq=6 ttl=55 time=15.670 ms
64 bytes from 204.157.9.189: icmp_seq=7 ttl=55 time=15.609 ms
64 bytes from 204.157.9.189: icmp_seq=8 ttl=55 time=15.625 ms
64 bytes from 204.157.9.189: icmp_seq=9 ttl=55 time=15.625 ms
64 bytes from 204.157.9.189: icmp_seq=10 ttl=55 time=15.735 ms
64 bytes from 204.157.9.189: icmp_seq=11 ttl=55 time=15.613 ms
64 bytes from 204.157.9.189: icmp_seq=12 ttl=55 time=15.581 ms
64 bytes from 204.157.9.189: icmp_seq=13 ttl=55 time=15.691 ms
64 bytes from 204.157.9.189: icmp_seq=14 ttl=55 time=15.653 ms
64 bytes from 204.157.9.189: icmp_seq=15 ttl=55 time=15.661 ms
64 bytes from 204.157.9.189: icmp_seq=16 ttl=55 time=15.624 ms
64 bytes from 204.157.9.189: icmp_seq=17 ttl=55 time=15.615 ms
64 bytes from 204.157.9.189: icmp_seq=18 ttl=55 time=15.556 ms
64 bytes from 204.157.9.189: icmp_seq=19 ttl=55 time=15.602 ms
64 bytes from 204.157.9.189: icmp_seq=20 ttl=55 time=15.609 ms
64 bytes from 204.157.9.189: icmp_seq=21 ttl=55 time=15.601 ms
64 bytes from 204.157.9.189: icmp_seq=22 ttl=55 time=15.589 ms
64 bytes from 204.157.9.189: icmp_seq=23 ttl=55 time=15.639 ms
64 bytes from 204.157.9.189: icmp_seq=24 ttl=55 time=15.703 ms
^C
--- 204.157.9.189 ping statistics ---
25 packets transmitted, 25 packets received, 0% packet loss
round-trip min/avg/max/stddev = 15.556/15.639/15.744/0.050 ms
 
Time Warner Cable - Liberty, MO (just East of KC).

Pinging 204.157.9.189 with 32 bytes of data:

Reply from 204.157.8.189: bytes=32 time=50ms TTL=50
Reply from 204.157.8.189: bytes=32 time=52ms TTL=50
Reply from 204.157.8.189: bytes=32 time=50ms TTL=50
Reply from 204.157.8.189: bytes=32 time=49ms TTL=50
 
Bellsouth DSL Atlanta GA

Pinging 204.157.9.189 with 32 bytes of data:

Reply from 204.157.9.189: bytes=32 time=54ms TTL=55
Reply from 204.157.9.189: bytes=32 time=52ms TTL=55
Reply from 204.157.9.189: bytes=32 time=52ms TTL=55
Reply from 204.157.9.189: bytes=32 time=52ms TTL=55

Ping statistics for 204.157.9.189:
Packets: Sent = 4, Received = 4, Lost = 0 (0% los
Approximate round trip times in milli-seconds:
Minimum = 52ms, Maximum = 54ms, Average = 52ms
 
Bellsouth DSL Miami Beach FL

Pinging 204.157.9.189 with 32 bytes of data:

Reply from 204.157.9.189: bytes=32 time=45ms TTL=55
Reply from 204.157.9.189: bytes=32 time=45ms TTL=55
Reply from 204.157.9.189: bytes=32 time=45ms TTL=55
Reply from 204.157.9.189: bytes=32 time=44ms TTL=55

Ping statistics for 204.157.9.189:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 44ms, Maximum = 45ms, Average = 44ms
 
From Ashburn Virginia:
PING 204.157.9.189: 56 data bytes
64 bytes from unknown189.9.157.204.defenderhosting.com (204.157.9.189): icmp_seq=0. time=4. ms
64 bytes from unknown189.9.157.204.defenderhosting.com (204.157.9.189): icmp_seq=1. time=4. ms
64 bytes from unknown189.9.157.204.defenderhosting.com (204.157.9.189): icmp_seq=2. time=3. ms
64 bytes from unknown189.9.157.204.defenderhosting.com (204.157.9.189): icmp_seq=3. time=3. ms
64 bytes from unknown189.9.157.204.defenderhosting.com (204.157.9.189): icmp_seq=4. time=3. ms
64 bytes from unknown189.9.157.204.defenderhosting.com (204.157.9.189): icmp_seq=5. time=3. ms
64 bytes from unknown189.9.157.204.defenderhosting.com (204.157.9.189): icmp_seq=6. time=4. ms
64 bytes from unknown189.9.157.204.defenderhosting.com (204.157.9.189): icmp_seq=7. time=4. ms
64 bytes from unknown189.9.157.204.defenderhosting.com (204.157.9.189): icmp_seq=8. time=3. ms
64 bytes from unknown189.9.157.204.defenderhosting.com (204.157.9.189): icmp_seq=9. time=4. ms
64 bytes from unknown189.9.157.204.defenderhosting.com (204.157.9.189): icmp_seq=10. time=4. ms
64 bytes from unknown189.9.157.204.defenderhosting.com (204.157.9.189): icmp_seq=11. time=5. ms
64 bytes from unknown189.9.157.204.defenderhosting.com (204.157.9.189): icmp_seq=12. time=4. ms
64 bytes from unknown189.9.157.204.defenderhosting.com (204.157.9.189): icmp_seq=13. time=3. ms
64 bytes from unknown189.9.157.204.defenderhosting.com (204.157.9.189): icmp_seq=14. time=3. ms
64 bytes from unknown189.9.157.204.defenderhosting.com (204.157.9.189): icmp_seq=15. time=4. ms
64 bytes from unknown189.9.157.204.defenderhosting.com (204.157.9.189): icmp_seq=16. time=4. ms
64 bytes from unknown189.9.157.204.defenderhosting.com (204.157.9.189): icmp_seq=17. time=3. ms
64 bytes from unknown189.9.157.204.defenderhosting.com (204.157.9.189): icmp_seq=18. time=4. ms
^C
----204.157.9.189 PING Statistics----
19 packets transmitted, 19 packets received, 0% packet loss
round-trip (ms) min/avg/max = 3/3/5

Do you need a traceroute?
 
Pinging 204.157.9.189 with 32 bytes of data:

Reply from 204.157.9.189: bytes=32 time=50ms TTL=55
Reply from 204.157.9.189: bytes=32 time=50ms TTL=55
Reply from 204.157.9.189: bytes=32 time=50ms TTL=55
Reply from 204.157.9.189: bytes=32 time=50ms TTL=55

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

Louisville, KY
 
junkman_56 said:
----204.157.9.189 PING Statistics----
19 packets transmitted, 19 packets received, 0% packet loss
round-trip (ms) min/avg/max = 3/3/5

Do you need a traceroute?
[snapback]265456[/snapback]​
Click to expand...
I was thinking the same thing until I realized that a tracert doesnt do him much good. How we get to him is pretty much out of his control. Just the TTL and avg round trip seems like enough info, unless there are mulitple persons with packet loss.

-E
 
From Harrisburg, PA

ping 204.157.9.189

Pinging 204.157.9.189 with 32 bytes of data:

Reply from 204.157.9.189: bytes=32 time=15ms TTL=5
Reply from 204.157.9.189: bytes=32 time=14ms TTL=5
Reply from 204.157.9.189: bytes=32 time=14ms TTL=5
Reply from 204.157.9.189: bytes=32 time=13ms TTL=5

Ping statistics for 204.157.9.189:
Packets: Sent = 4, Received = 4, Lost = 0 (0%
Approximate round trip times in milli-seconds:
Minimum = 13ms, Maximum = 15ms, Average = 14ms
 
Pinging 204.157.9.189 with 32 bytes of data:

Reply from 204.157.9.189: bytes=32 time=72ms TTL=51
Reply from 204.157.9.189: bytes=32 time=71ms TTL=51
Reply from 204.157.9.189: bytes=32 time=70ms TTL=51
Reply from 204.157.9.189: bytes=32 time=73ms TTL=51

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

Hutchinson KS
 
Just in case you wanted more:

Pinging 204.157.9.189 with 32 bytes of data:

Reply from 204.157.9.189: bytes=32 time=36ms TTL=51
Reply from 204.157.9.189: bytes=32 time=34ms TTL=51
Reply from 204.157.9.189: bytes=32 time=35ms TTL=51
Reply from 204.157.9.189: bytes=32 time=35ms TTL=51
Reply from 204.157.9.189: bytes=32 time=35ms TTL=51
Reply from 204.157.9.189: bytes=32 time=35ms TTL=51
Reply from 204.157.9.189: bytes=32 time=35ms TTL=51
Reply from 204.157.9.189: bytes=32 time=35ms TTL=51
Reply from 204.157.9.189: bytes=32 time=34ms TTL=51
Reply from 204.157.9.189: bytes=32 time=34ms TTL=51

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

From Miami, FL
 
Optimum Online, Nassau County (LI), NY

via Windows:

Pinging 204.157.9.189 with 32 bytes of data:

Reply from 204.157.9.189: bytes=32 time=16ms TTL=55
Reply from 204.157.9.189: bytes=32 time=16ms TTL=55
Reply from 204.157.9.189: bytes=32 time=15ms TTL=55
Reply from 204.157.9.189: bytes=32 time=16ms TTL=55

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

via Cyberkit:

Ping - Thursday, December 22, 2005 08:11:36
Generated by CyberKit Version 2.5
Copyright © 1996-2000 by Luc Neijens

Address: 204.157.9.189 - 204.157.9.189
Number of Packets: 3
Packet size: 64
Timeout: 15
Delay: 1000
Resolve Addresses: Yes
Don't Fragment: No

#1 unknown189.9.157.204.defenderhosting.com (204.157.9.189): Echo Reply, ttl=55, 20 ms
#2 unknown189.9.157.204.defenderhosting.com (204.157.9.189): Echo Reply, ttl=55, 10 ms
#3 unknown189.9.157.204.defenderhosting.com (204.157.9.189): Echo Reply, ttl=55, 11 ms

Statistics: Out 3, in 3, loss 0%, times (min/avg/max) 10/13/20 ms
 
From Finland

ping 204.157.9.189

Pinging 204.157.9.189 with 32 bytes of data:

Reply from 204.157.9.189: bytes=32 time=134ms TTL=55
Reply from 204.157.9.189: bytes=32 time=130ms TTL=55
Reply from 204.157.9.189: bytes=32 time=130ms TTL=55
Reply from 204.157.9.189: bytes=32 time=183ms TTL=55

Ping statistics for 204.157.9.189:
Packets: Sent = 4, Received = 4, Lost = 0 (0%
Approximate round trip times in milli-seconds:
Minimum = 130ms, Maximum = 183ms, Average = 144ms
 
Hey Rod,

From a shell account in California:

$ ping 204.157.9.189
PING 204.157.9.189 (204.157.9.189): 56 data bytes
64 bytes from 204.157.9.189: icmp_seq=0 ttl=50 time=69.851 ms
64 bytes from 204.157.9.189: icmp_seq=1 ttl=50 time=68.955 ms
64 bytes from 204.157.9.189: icmp_seq=2 ttl=50 time=69.009 ms
64 bytes from 204.157.9.189: icmp_seq=3 ttl=50 time=68.853 ms
64 bytes from 204.157.9.189: icmp_seq=4 ttl=50 time=69.393 ms
64 bytes from 204.157.9.189: icmp_seq=5 ttl=50 time=70.276 ms

From home in Boston:

Pinging 204.157.9.189 with 32 bytes of data:

Reply from 204.157.9.189: bytes=32 time=22ms TTL=47
Reply from 204.157.9.189: bytes=32 time=20ms TTL=46
Reply from 204.157.9.189: bytes=32 time=20ms TTL=47
Reply from 204.157.9.189: bytes=32 time=21ms TTL=47

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

Let me know if you want traceroutes.
 
From Central Ohio

Pinging 204.157.9.189 with 32 bytes of data:

Reply from 204.157.9.189: bytes=32 time=36ms TTL=50
Reply from 204.157.9.189: bytes=32 time=37ms TTL=50
Reply from 204.157.9.189: bytes=32 time=37ms TTL=50
Reply from 204.157.9.189: bytes=32 time=37ms TTL=50

Ping statistics for 204.157.9.189:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 36ms, Maximum = 37ms, Average = 36ms
 
From Port Washington, New York:

Pinging 204.157.9.189 with 32 bytes of data:

Reply from 204.157.9.189: bytes=32 time=12ms TTL=52
Reply from 204.157.9.189: bytes=32 time=12ms TTL=52
Reply from 204.157.9.189: bytes=32 time=14ms TTL=52
Reply from 204.157.9.189: bytes=32 time=14ms TTL=52

Ping statistics for 204.157.9.189:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 12ms, Maximum = 14ms, Average = 13ms
 
Target: 204.157.9.189
Date: 12/22/2005 (Thursday), 8:43:21 AM
Nodes: 14


Node Data
Node Net Reg IP Address Location Node Name
1 - - 192.168.123.111 Kitchener ACPIC
2 1 - 192.168.123.250 Unknown
3 2 - 64.230.197.33 Montréal
4 3 - 64.230.239.237 Kitchener
5 4 - 64.230.240.234 Kitchener
6 5 - 64.230.242.54 North York
7 6 - 64.230.242.93 North York
8 7 1 206.108.103.114 Chicago core2-chicago23-pos0-0.in.bellnexxia.net
9 8 - 64.230.203.150 Montréal rtp628550rts
10 9 2 63.218.5.9 Chicago ge2-3.br02.chc01.pccwbtn.net
11 9 2 63.218.44.50 39.044N, 77.489W pos4-1.br02.ash01.pccwbtn.net
12 9 2 63.218.94.6 39.044N, 77.489W dtg.ge9-11.br02.ash01.pccwbtn.net
13 10 3 204.157.0.143 38.894N, 77.444W eqash40.defenderhosting.com
14 11 3 204.157.9.189 38.894N, 77.444W unknown189.9.157.204.defenderhosting.com


Packet Data
Node High Low Avg Tot Lost
1 0 0 0 1 0
2 0 0 0 1 0
3 36 36 36 1 0
4 32 32 32 1 0
5 23 23 23 1 0
6 23 23 23 1 0
7 38 38 38 1 0
8 44 44 44 1 0
9 44 44 44 1 0
10 44 44 44 1 0
11 74 74 74 1 0
12 77 77 77 1 0
13 91 91 91 1 0
14 71 71 71 1 0


Network Data
Network id#: 1

OrgName: Internet Assigned Numbers Authority
OrgID: IANA
Address: 4676 Admiralty Way, Suite 330
City: Marina del Rey
StateProv: CA
PostalCode: 90292-6695
Country: US

Network id#: 2
Bell Canada BELLCANADA-5 (NET-64-228-0-0-1)
64.228.0.0 - 64.231.255.255
Bell Advanced Communications Inc. BEL100704-CA (NET-64-230-192-0-1)
64.230.192.0 - 64.230.255.255

Network id#: 3
Bell Canada BELLCANADA-5 (NET-64-228-0-0-1)
64.228.0.0 - 64.231.255.255
Bell Advanced Communications Inc. BEL100704-CA (NET-64-230-192-0-1)
64.230.192.0 - 64.230.255.255

Network id#: 4
Bell Canada BELLCANADA-5 (NET-64-228-0-0-1)
64.228.0.0 - 64.231.255.255
Bell Advanced Communications Inc. BEL100704-CA (NET-64-230-192-0-1)
64.230.192.0 - 64.230.255.255

Network id#: 5
Bell Canada BELLCANADA-5 (NET-64-228-0-0-1)
64.228.0.0 - 64.231.255.255
Bell Advanced Communications Inc. BEL100704-CA (NET-64-230-192-0-1)
64.230.192.0 - 64.230.255.255

Network id#: 6
Bell Canada BELLCANADA-5 (NET-64-228-0-0-1)
64.228.0.0 - 64.231.255.255
Bell Advanced Communications Inc. BEL100704-CA (NET-64-230-192-0-1)
64.230.192.0 - 64.230.255.255

Network id#: 7

OrgName: Bell Advanced Communications Inc.
OrgID: BAC-14
Address: 350-181 Bay Street
City: Toronto
StateProv: ON
PostalCode: M5J-2T3
Country: CA

Network id#: 8
Bell Canada BELLCANADA-5 (NET-64-228-0-0-1)
64.228.0.0 - 64.231.255.255
Bell Advanced Communications Inc. BEL100704-CA (NET-64-230-192-0-1)
64.230.192.0 - 64.230.255.255

Network id#: 9

OrgName: Beyond The Network America, Inc.
OrgID: BNA-42
Address: Reston Executive Center
Address: 12100 Sunset Hills Road, Suite 300
City: Reston
StateProv: VA
PostalCode: 20190
Country: US

Network id#: 10
AGIS ALERON-204-157 (NET-204-157-0-0-1)
204.157.0.0 - 204.157.255.255
Defender Technologies Group, LLC DEFENDER-204-157-0-0-24 (NET-204-157-0-0-2)
204.157.0.0 - 204.157.0.255

Network id#: 11
AGIS ALERON-204-157 (NET-204-157-0-0-1)
204.157.0.0 - 204.157.255.255
Defender Technologies Group, LLC DEFENDER-204-157-9-0-24 (NET-204-157-9-0-1)
204.157.9.0 - 204.157.9.255
 
From the Gulf coast of FL.

Pinging 204.157.9.189 with 32 bytes of data:

Reply from 204.157.9.189: bytes=32 time=34ms TTL=52
Reply from 204.157.9.189: bytes=32 time=32ms TTL=52
Reply from 204.157.9.189: bytes=32 time=33ms TTL=52
Reply from 204.157.9.189: bytes=32 time=33ms TTL=52

Ping statistics for 204.157.9.189:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 32ms, Maximum = 34ms, Average = 33ms
 
You must log in or register to reply here.
Top