Find out how far away the server is from just Pinging it?

  • Thread starter Thread starter biferi
  • Start date Start date
  • Tags Tags
    Server
Click For Summary

Discussion Overview

The discussion revolves around understanding the Ping command and its implications for estimating the distance to a server based on response times. Participants explore the relationship between ping times, server processing, and network complexities, while also considering packet size adjustments.

Discussion Character

  • Exploratory
  • Technical explanation
  • Debate/contested

Main Points Raised

  • One participant notes that the Ping command returns round-trip times (e.g., 30 ms, 31 ms) but questions how to interpret these times in terms of server distance.
  • Another participant argues that there is no strict correlation between ping times and physical distance due to factors like network nodes and server processing times.
  • A participant suggests that while low ping times indicate fast responses, they do not necessarily reflect distance accurately due to potential server load and shared resources.
  • One reply humorously estimates that under ideal conditions, a 30 ms ping could imply a server distance of about 4500 km, but acknowledges this is a conservative and impractical assumption.
  • Another participant recommends using the Tracert command to analyze the path and time taken through various network hops, emphasizing the complexity of determining actual distances.

Areas of Agreement / Disagreement

Participants express differing views on the relationship between ping times and server distance, with no consensus reached. Some acknowledge the limitations of using ping times for distance estimation, while others explore hypothetical scenarios.

Contextual Notes

Participants highlight that factors such as network topology, server load, and routing configurations complicate the interpretation of ping times in terms of distance.

biferi
Messages
191
Reaction score
0
I am just playing with the Ping command and would like some help understanding it.

I used Ping on Google and 4 Packets of 32 Bytes of Data went out and came back.
And the TTL for eatch Packet was like this

TTL = 30 ms
TTL = 31 ms
TTL = 30 ms
TTL = 29 ms

Now I know that this is how long each Packet took to go and come back.
And it should stay under 50 ms. and anything over something is wrong.

But how do ppeople findout how far away the server is from just Pinging it?

I know 1,000 ms = 1 SEC. so if my Pakets took 31 ms to get to and come back from google does this mean the server is how many MIN. away it is?
 
Computer science news on Phys.org
I doubt there is any strict correlation between the ping number and the distance to the server. It will depend on how many nodes the signal goes through to get there and back and how fast they are.

Also, "should stay under 50ms" is a decent rule of thumb, BUT ... there are many sites that are run off of shared servers, sometimes heavily shared servers, that will rarely give you better than, say, 100ms response time, so it is NOT just a matter of the signal getting there and back, there is also the processing time of the server and that can be slowed down by its load, having nothing to do with the rest of the signal transmission time.
 
Thanks for getting back to me.

But I do want to know google gave me a TTL of 30ms 31ms 3ms 29ms they are all very very low.

so this tells me they all came back fast and had no prablems.

Is there any way to ajust the Size of each Packet from 32 Bytes to whatever you want?
 
Yeah, you'd have to make some crazy assumptions to get an idea of how far away the server is. Just for fun though, let's assume that the line is ideal and the signal travels at the speed of light, and that the server is perfect with no interuptions and doesn't have to go through clusters etc. So from 30ms we can get that the server you have pinged is about 4500 km away, which is 1/9 of the Earth's circumference or like from one side of the U.S to the other. Being an engineer, I would call this a conservative estimate :) or the maximum case. Completely pointless, but interesting.

Btw, 30ms is damm good, from Australia we get 100ms from most servers not in our country.
 
Last edited:
Have a look at the Tracert cmd, it may help you understand where the ping is actually coming from, the time it takes to hop over all the other connections to google or any server in general and then back again. this is why it is generally impossible to determine how far a server is from your current location, not to mention all networks do not just run in straight lines in terms of distance. you could also look into routing as well as its quite interesting where you get pings from depending on switch configuration and what route your computer takes to collect the information.
 

Similar threads

  • · Replies 18 ·
Replies
18
Views
4K
  • · Replies 6 ·
Replies
6
Views
2K
  • · Replies 3 ·
Replies
3
Views
4K
Replies
3
Views
3K
  • · Replies 28 ·
Replies
28
Views
4K
Replies
1
Views
2K
  • · Replies 2 ·
Replies
2
Views
4K
  • · Replies 19 ·
Replies
19
Views
15K
  • · Replies 7 ·
Replies
7
Views
3K
Replies
10
Views
5K