Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I am in Kansas I need to test latency to Oregon. Assuming I don't know anyone in Oregeon or know what hosts are pingable and also in oregeon is there any handy tool for this?

It would be even better if I could select to arbitrary locations and get average latency times on the wire between hosts located in two geopolitcally seperated locations.

share|improve this question
You know that the only thing ping really tests is whether or not ping works, right? – RobM Jun 14 '12 at 18:02
What exactly are "geopolitcally seperated locations"? – joeqwerty Jun 14 '12 at 18:50
up vote 3 down vote accepted

Physical locations don't correlate cleanly with network locations. One carrier might take you from Oregon to Kansas via a single POP on each side and a dedicated circuit that happens to physically run directly between the two sites while another carrier might hand off to an intermediary transit provider that backhauls the traffic to Virginia to hand off to a carrier that routes through Texas to go back up to Kansas. Best of all, either path could be valid at a given time depending on fault and traffic conditions.

share|improve this answer

You can test basic latency with ping, smokeping, iperf, et cetera.

If you don't know what the endpoint you're testing for is, then there's not much point in testing something else entirely. Your traffic could go through a completely different network somewhere and have wildly different results.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.