What is a good ping result?

I pining a server but dont know what I should be looking for can someone help me.. What is a good result


Thanks

Well, to tell ya the truth, I can't tell you. There are so many factors that will change your ping results. How away the server is from you, how many hops it takes, what your ISP is like, internet congestion. Some of them will change the speed of your site, other's will not.

However, when I ping a website 55ms is usually pretty good. That's with an aDSL Line. Cable users may get lower pings or higher. A T-1 should get about 20 ms.

I get an average of 44ms and I'm on a T3

I would say <200 is ok (unless it's a games server ;) ) but your ping does depend on location to the target server.

http://whreviews.com/testing-speed.htm says ...


It's all in the time measurement. A ping time of under 200ms is very good, 200 to 400ms is average and 400ms and above are poor ping times. However, poor ping times do not always indicate a problem. If you are pinging servers that are very far away (pinging a server located in USA from a computer located in Australia), poor ping times are normal even for a good connection.
CC.

ping is only one factor in a list of many that affect a server's performance.

:) Hi There,
In short below 400ms is good but you want to aim for below 200 and most importantly no packet losses.

For my Comcast connection to most of the datacenters I have tried in the US, I can range anywhere from 18-50 ms with about 25 being average.

Wooooooooooow

Thanks guys for the info, this helps alot.

Thanks again.

Originally posted by milljea
What is a good ping result?

I pining a server but dont know what I should be looking for can someone help me.. What is a good result


Thanks
This


C:\Documents and Settings\XP>ping 127.0.0.1

Pinging 127.0.0.1 with 32 bytes of data:

Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128

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

:D

MCI T-1's we get about 5ms ping from a 30km distance from a customer location.

To Yahoo from our Office:

Pinging yahoo.com [66.218.71.198] with 32 bytes of data:

Reply from 66.218.71.198: bytes=32 time=87ms TTL=243
Reply from 66.218.71.198: bytes=32 time=85ms TTL=243
Reply from 66.218.71.198: bytes=32 time=86ms TTL=243
Reply from 66.218.71.198: bytes=32 time=85ms TTL=243

Pinging google.com [216.239.37.99] with 32 bytes of data:

Reply from 216.239.37.99: bytes=32 time=25ms TTL=50
Reply from 216.239.37.99: bytes=32 time=24ms TTL=50
Reply from 216.239.37.99: bytes=32 time=24ms TTL=50
Reply from 216.239.37.99: bytes=32 time=24ms TTL=50

It really depends, the host might have 1mbit connection non burstable pings could be <10ms however download speeds would be poor if your using broadband. I would not use ping as a suitable way of testing a provider.

I believe a constant stable ping would be best. Of course, the lower it is, better it would be.

yah the lower the better but if your going to find out the ping then you should try it with 56k cuse there are a lot of people still using it.

--- tweakers.net ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3026ms
rtt min/avg/max/mdev = 1.054/1.261/1.560/0.189 ms

:D

[edit] This is on a 1000mbit server located in Amsterdam, Netherlands.

A good ping time I think is <10ms. Good old localhost... :emlaugh: