Agreed, how about including this critical information in the description field to get around this, perhaps? -----Original Message----- From: ripe-atlas [mailto:ripe-atlas-bounces@ripe.net] On Behalf Of Martin Winter Sent: 25 February 2015 07:29 To: ripe-atlas@ripe.net Subject: [atlas] Proble locations (Changed because of Geo-IP) So I've noticed that (at least some) probes got the location automatically updated based on Geo IP. However, this is frequently fundamentially broken. One of my probe moved from San Jose, CA to somewhere in the middle of Texas. (Broken Geo-IP location for AT&T DSL users). (The example I talk about is proble #10770) Kind of sad... not sure how many had this happening. Specially as I took care to put the exact lat/lon in the User interface in the past. Now I can only reposition it by dragging on a map - and that seems to be broken as well (at least it fails to save when I try to correct this probes location on Chrome) I wonder how many and why there was a decision to change the location. I think the location were much better before they got force-changed. - Martin Winter