This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/ripe-atlas@ripe.net/
[atlas] How to deal with inaccurate geocoding of probes
- Previous message (by thread): [atlas] Ticket response times
- Next message (by thread): [atlas] How to deal with inaccurate geocoding of probes
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Klaus Darilion
klaus.mailinglists at pernau.at
Wed Dec 30 15:39:29 CET 2015
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
- Previous message (by thread): [atlas] Ticket response times
- Next message (by thread): [atlas] How to deal with inaccurate geocoding of probes
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]