[ripe-db-requirements-tf] Geolocation in the RIPE database
- Previous message (by thread): [ripe-db-requirements-tf] IRT Query Statistics
- Next message (by thread): [ripe-db-requirements-tf] Notes from 18 February 2020 Meeting
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Edward Shryane
eshryane at ripe.net
Mon Mar 2 12:45:13 CET 2020
Hi all, Here are some statistics for geolocation in the RIPE database. 25% of respondents in the recent survey use the RUPE database for geolocation. Background reading on geolocation in the RIPE database: https://www.ripe.net/manage-ips-and-asns/db/tools/geolocation-in-the-ripe-database https://labs.ripe.net/Members/denis/geolocation-prototype-for-ripe-database * There are 24,408 inetnum objects with a geoloc: attribute (with 7,731 distinct values). 25 different organisations are responsible for 51% of inetnums with a geoloc: attribute. * There are 516,354 inet6num objects with a geoloc: attribute (with 1,045 distinct values). 1 single organisation is responsible for 99% of inet6nums with a geoloc: attribute. * 127,105 occurrences of "51.507351 -0.127758" (London) * 130,175 occurrences of "40.712784 -74.005941" (New York) * 255,998 occurrences of "34.052235 -118.243683" (Los Angeles) There is no special query flag for geolocation - the geoloc: attribute will be included if present in any matching inetnum or inet6num. Let me know if you have any questions or would like more details. Regards Ed Shryane RIPE NCC
- Previous message (by thread): [ripe-db-requirements-tf] IRT Query Statistics
- Next message (by thread): [ripe-db-requirements-tf] Notes from 18 February 2020 Meeting
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]