Average Ping Value

I know that the ideal value when pinging a site should be as close to 0 ms as possible.
However, what is a good value both on the LAN and connecting to sites on the internet?
What is the warning sign that the connection has problems - 100ms 1000ms?


Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

It depends on the size and complexity of the LAN but usually a ping time of around 10ms or less is normal for a small LAN.  As for the internet, it depends on the server you are connecting to and it's geographical location, but a good internet ping time is 100ms or less.  For halfway round the globe, maybe 300ms.  These times greatly increase if you are on 56K dial-up though. (300-1000ms)

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
As slartibartfarst just said, it depends...
At work we have very fast LAN, with newest technology and fiber conections etc.. What ever computer you ping from what ever computer in there, you "always" get <10ms. But when you are pinging over the internet, you will never know where your ip-packages travel, so the echo reply will probably be slower than this. 100ms or less is good.
It all depends on the ISP and the connection. Some ISP's will guarantee a response time < 75ms end-to-end, some guarantees are meaningless because they only guarantee the latency "within their network", not end-end

Consistency is probably a more important sign of trouble. If you get pings that fluctuate between 50ms one ping, next ping 287ms, next ping 398ms, next ping 72ms. This could be a sign of upstream issues that you probably can't control, but could be trouble to any applications that are delay sensitive.
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

markg1Author Commented:
What about tracert?
Does the no more than 100ms per hop hold true?
I would say yes, each hob should not be more than 100ms from one....
IHMO, not necessarily. Traceroute works differently than ping. Not all routers in the path will respond to the icmp packets so the timeout values are included in the response times.
Remember also that ICMP traffic is lowest priority through most of the routers in the link, so poor ping times may not translate into poor application performance.
I agree with Lmoore.  Latency is not necessarily the most important factor.  Jitter, varience in the latency, can have a greater impact on most applications than pure latency.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.