Ping me and report back!

[Marty]

Hey, can everyone please ping 128.253.197.20 and tell me what kind of pings you are getting? Also let me know where you are pinging from. The computer is in Ithaca NY.

Marty

 

[Ladies Man]

first timed out
second/third both 125ms
forth 94ms

i'm in baltimore

 

[shiznut123]

Around 190ms from L.A., California

edit: Second reply was timed out

 

[shiner]

I got a reply in 170ms from a computer named porn_vault.

I'm in Tulsa, OK

 

[Zipperhead]

Pinging 128.253.197.20 with 32 bytes of data:

Reply from 128.253.197.20: bytes=32 time=165ms TTL=107
Reply from 128.253.197.20: bytes=32 time=124ms TTL=107
Reply from 128.253.197.20: bytes=32 time=83ms TTL=107
Request timed out.

Ping statistics for 128.253.197.20:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
Minimum = 83ms, Maximum = 165ms, Average = 93ms

in mass

 

[urbantechie]

Thanks for IP

 

[urbantechie]

<< C:\>ping 128.253.197.20

Pinging 128.253.197.20 with 32 bytes of data:

Reply from 128.253.197.20: bytes=32 time=240ms TTL=101
Reply from 128.253.197.20: bytes=32 time=321ms TTL=101
Reply from 128.253.197.20: bytes=32 time=270ms TTL=101
Reply from 128.253.197.20: bytes=32 time=271ms TTL=101

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

 

[Azraele]

0% packet loss.
Avg round trip in milliseconds: 1421

 

[dopcombo]

hey, i go to cornell as well.

But cos i use lightlink the ping had to go to syracuse and back to your resnet connection..

However, it took me 6 ms to get back to cit.resnet and then 143 to get to your IP
with a large percentage of packets being lost.

Something wrong with your connection or network connection maybe?

Using visualroute ...

 

[SpongeBob]

Average 175ms, on @Home Cable in Detroit MI

 

[Pretender]

Oh, you said PING, not DDos....my bad.

 

[tomcat]

New Hampshire cable:

Reply from 128.253.197.20: bytes=32 time=500ms TTL=113
Reply from 128.253.197.20: bytes=32 time=30ms TTL=113
Reply from 128.253.197.20: bytes=32 time=301ms TTL=113
Reply from 128.253.197.20: bytes=32 time=200ms TTL=113

cornell eh? congrats.

 

[Moonbeam]

Microsoft(R) Windows 98
(C)Copyright Microsoft Corp 1981-1999.

C:\WINDOWS>ping 128.253.197.20

Pinging 128.253.197.20 with 32 bytes of data:

Reply from 128.253.197.20: bytes=32 time=282ms TTL=106
Reply from 128.253.197.20: bytes=32 time=332ms TTL=106
Reply from 128.253.197.20: bytes=32 time=250ms TTL=106
Reply from 128.253.197.20: bytes=32 time=135ms TTL=106

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

C:\WINDOWS>

From San Francisco Peninsula

 

[RGN]

C:\>ping 128.253.197.20

Pinging 128.253.197.20 with 32 bytes of data:

Reply from 128.253.197.20: bytes=32 time=271ms TTL=107
Request timed out.
Reply from 128.253.197.20: bytes=32 time=181ms TTL=107
Reply from 128.253.197.20: bytes=32 time=90ms TTL=107

Ping statistics for 128.253.197.20:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
Minimum = 90ms, Maximum = 271ms, Average = 135ms

C:\>

 

[prodigy]

Average 172ms.

Albany, NY.

 

[FrogDog]

195ms from NS, Canada.

 

[The Stigenator]

C:\>ping 128.253.197.20

Pinging 128.253.197.20 with 32 bytes of data:

Reply from 128.253.197.20: bytes=32 time=467ms TTL=105
Reply from 128.253.197.20: bytes=32 time=276ms TTL=105
Reply from 128.253.197.20: bytes=32 time=372ms TTL=105
Reply from 128.253.197.20: bytes=32 time=386ms TTL=105

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

Glendale, CA

 

[loup garou]

Last Response Time: 115 ms

Highest Response Time: 608 ms
Lowest Response Time: 76 ms
Average Response Time: 191 ms

Total Number of Packets Sent: 22

Dropped/Lost Packets 1
Dropped/Lost Packets %: 4 %

 

[Marty]

Hmmm... those are poorer than I expected. I've also had problems recently with Counterstrike servers; i got terrible pings and so forth. On the same connection I got much better pings only a short while ago. I did play with the cat5 cable, could that be it? Any other suggestions?

I'm going to be running a CS server, which is the reason for my questioning.

Marty

 

[kami]

160ms average, but my pipe is completely full right now (up and down) so it would probably be lower normally.

 

[Pepsi90919]

328 ms
255 ms
200 ms
160 ms
100 ms
74 ms
78 ms
194 ms
No response
287 ms

cogeco@home, ontario.

 

[Howard]

C:\WINDOWS>ping 128.253.197.20

Pinging 128.253.197.20 with 32 bytes of data:

Reply from 128.253.197.20: bytes=32 time=420ms TTL=113
Reply from 128.253.197.20: bytes=32 time=260ms TTL=113
Reply from 128.253.197.20: bytes=32 time=138ms TTL=113
Request timed out.

Ping statistics for 128.253.197.20:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
Minimum = 138ms, Maximum = 420ms, Average = 204ms

C:\WINDOWS>
C:\WINDOWS>

 

[Howard]

DSl

 

[Pretender]

have someone tracert you and see where the majority of the latency is coming from. Assuming the pings jump from a low number (< 100) on one server, to a higher number on the next should tell you where your lag is coming from. If the lag jump occurs on the final hop (reaching your server), then it could very well be the cable you screwed with.

 

[paruhd0x]

I'm in San Diego, California.

Ping statistics for 128.253.197.20:
Packets: Sent = 94, Received = 77, Lost = 17 (18% loss),
Approximate round trip times in milli-seconds:
Minimum = 85ms, Maximum = 555ms, Average = 209ms