Than you both - we'll check if such a measurement can be used as an indication that the probe's network is "strange" and see if we can apply a tag to mark them. Regards, Robert On Wed, Aug 6, 2025 at 12:41 AM William Kanieski via ripe-atlas < ripe-atlas@ripe.net> wrote:
Hi, Malte.
Thank you for your quick response and for bringing these measurements to my attention. Conducting traceroutes to an unannounced public IP address is a very clever way to filter out proxies that may respond on its behalf, and seems much more effective than just checking the first hops. I will periodically check the traceroute measurement for evidence of other anomalous probes, and will make note of the probes you mentioned as well when conducting my experiments.
Regards,
William Kanieski
On Mon, Aug 4, 2025 at 9:12 PM Malte Tashiro via ripe-atlas < ripe-atlas@ripe.net> wrote:
Hi William,
adding to this, there are also three probes (63018, 1000963, 1011609) with the same problem. See this [0] measurement, which targets an IP that is not announced on BGP on purpose [1]. All probes with replies have some issue.
Best, Malte
[0] https://atlas.ripe.net/measurements/40072013/results [1] https://github.com/RIPE-Atlas-Community/ripe-atlas-tips-and-tricks/wiki/nonD... ----- To unsubscribe from this mailing list or change your subscription options, please visit: https://mailman.ripe.net/mailman3/lists/ripe-atlas.ripe.net/ As we have migrated to Mailman 3, you will need to create an account with the email matching your subscription before you can change your settings. More details at: https://www.ripe.net/membership/mail/mailman-3-migration/
----- To unsubscribe from this mailing list or change your subscription options, please visit: https://mailman.ripe.net/mailman3/lists/ripe-atlas.ripe.net/ As we have migrated to Mailman 3, you will need to create an account with the email matching your subscription before you can change your settings. More details at: https://www.ripe.net/membership/mail/mailman-3-migration/