How to deal with inaccurate geocoding of probes
Hi! Inspired by https://perso.telecom-paristech.fr/~drossi/index.php?n=Dataset.Anycast I wanted to detect my Anycast locations using the Atlas probes. The problem is, that my results are only as accurate as the geocoding of the Atlas probes. For example probe #19273 is reported to be somewhere in Kansas. Bit the probe is only 5ms away from my LAX server and also traceroute indicates the probe is in LAX (traceroute to 63.84.150.1). So, now I am seeking some advice how to handle such problems. Is there some tag that indicates "verified location"? Any other ideas? Thanks Klaus
Hi Klaus, On 30/12/15 15:39, Klaus Darilion wrote:
Hi!
Inspired by https://perso.telecom-paristech.fr/~drossi/index.php?n=Dataset.Anycast I wanted to detect my Anycast locations using the Atlas probes.
The problem is, that my results are only as accurate as the geocoding of the Atlas probes.
For example probe #19273 is reported to be somewhere in Kansas.
I guess we're not in Kansas anymore ;)
Bit the probe is only 5ms away from my LAX server and also traceroute indicates the probe is in LAX (traceroute to 63.84.150.1).
So, now I am seeking some advice how to handle such problems. Is there some tag that indicates "verified location"? Any other ideas?
This particular probe has the tag: Auto GeoIP Country which means that we could not determine the location any more accurately than at country level. Originally, this probe was located somewhere in Canada but we noticed it was not there anymore so we automatically moved it closer to where we think it really is. Unfortunately, we could not be more precise than country level which is why we tagged it this way. We are constantly working on ways to improve the automatic geotagging of probes but the best way is still for probe hosts to keep the location of the probe up to date. Regards, Johan ter Beest RIPE Atlas team
Thanks Klaus
participants (2)
-
Johan ter Beest
-
Klaus Darilion