Ipmap

Download

ipmap@ripe.net

2 discussions

RIPE IPmap v1.1.0: reverse-dns engine
by Chris Amin 17 May '22

17 May '22

Dear colleagues, In November of last year, we released version 1.0.0 of RIPE IPmap. The main feature of that version was the new latency engine, but we also included a prototype of the “reverse-dns” engine, which used very basic pattern matching of hostnames from PTR to provide location guesses. We are pleased to announce that with v1.1.0 the reverse-dns engine has received a major upgrade, allowing it to provide much better geolocation answers through pattern analysis of the entire IPmap “latency” and “worlds” datasets, with daily analysis performed mostly thanks to the sc_hoiho tool from CAIDA’s scamper toolkit. More information about the new engine, as well as links to information on the sc_hoiho tool and its theoretical underpinnings can be found at: https://ipmap.ripe.net/docs/01.manual/#reverse-dns As well as the new and improved reverse-dns engine, the suggestion system has been improved to better combine results from the various geolocation engines, and the "single-radius" engine has been more closely integrated into the "latency" engine, with both offering basic anycast detection. As always, you can get started with the API with the IPmap docs at: https://ipmap.ripe.net/docs/ Kind regards, Chris Amin RIPE NCC

1 0

Launching RIPE IPmap v1.0.0
by Chris Amin 25 Nov '21

25 Nov '21

Dear colleagues, We are pleased to announce version 1.0.0 of RIPE IPmap, the RIPE NCC’s API for mapping core Internet infrastructure. This release includes various backwards-compatible improvements. The major change is the inclusion of two new engines, which will play a significant part in the further development of RIPE IPmap going forward. First, the latency engine, a passive speed-of-light engine that uses all non-private RIPE Atlas traceroutes over the past seven days to infer upper bounds on locations. The quality of these inferences is improved by internally verifying the locations of RIPE Atlas anchors and probes, which is something that will be fed back into RIPE Atlas in the future. Second, the reverse-dns engine, which uses names from DNS PTR records to guess the locations of IP addresses. This iteration of the engine only makes use of very basic pattern matching and can be seen as a placeholder for more advanced techniques, which will be added in a later release. The API documentation has also been expanded and made easier to read and search. Both the manual and the API reference are available at: https://ipmap.ripe.net/docs/ Finally, the landing page has been relaunched to include better information on the service, as well as an interactive demo which allows you to try out the API and get instant visual feedback. Note: currently there is no web interface for contributing corrections using the "crowdsourced" engine. This is because we are working on improving the crowdsourcing aspect of RIPE IPmap - you can expect more on this in the future. We hope you enjoy all the new features and changes we have made. If you have any questions or feedback, then please let me know either here on the list or by getting in touch with me directly. To get started, visit: https://ipmap.ripe.net/ Kind regards, Chris Amin RIPE NCC

1 0