Change Details

Early in the process, we decided we preferred MaxMind's location values over IPoid's. However, there are instances where IPoid has location data and MaxMind doesn't. In those instances, should IPInfo fallback to IPoid's location data? From a technical perspective, MaxMind splits their location data into city/state/country and we record feed data similarly so we would be able to retain the basic-view country vs full-view city level access: ``` MariaDB [ipoid]> select * from actor_data limit 1; +------+-----------+-------------------------------------------+--------------+-------+-----------+------------+--------------+-----------+------------------+-------+--------------+ | pkid | ip | org | client_count | types | conc_city | conc_state | conc_country | countries | location_country | risks | last_updated | +------+-----------+-------------------------------------------+--------------+-------+-----------+------------+--------------+-----------+------------------+-------+--------------+ | 1 | N/A | APNIC and Cloudflare DNS Resolver project | 1 | 1 | Tripoli | Tripoli | LY | 1 | AU | 0 | 1705653487 | +------+-----------+-------------------------------------------+--------------+-------+-----------+------------+--------------+-----------+------------------+-------+--------------+ ```

As of writing, we've deprecated use of the Enterprise MaxMind database in favor of IPoid (Spur). From {T355392}, Spur's database is missing IPs (see other ticket for details) which could be covered by MaxMind's GeoLite2 databases. Historically, we decided to prefer MaxMind's location/asn/isp data over Spur but 1. never wrote in fallback functionality and 2. never returned that data from Spur. However now that we no longer use the Enterprise dataset, we might instead choose to prioritize Spur in all cases and fall back to MaxMind's Asn/City databases when Spur lacks the data( specifically, this is happening when Spur is missing the entire IP object as opposed to just the location/organization data, which it flat out isn't passing back). Acceptance Criteria: - Confirm that GeoLite2 data is being passed through (the handlers already exist but may not be in use) - Implement a fallback to MaxMind data when Spur is missing the data (location from City.mmdb, asn from ASN.mmdb) Bonus Criteria: - Pass back location/org data from Spur (They're already being saved to the database) - Implement Spur as a source for these data points in widgets

Early in the process, we decided we preferred MaxMind's location values over IPoid's. HoweverAs of writing, there are instances where IPoid has locationwe've deprecated use of the Enterprise MaxMind data and MaxMind doesn'tbase in favor of IPoid (Spur). In those instancesFrom {T355392}, should IPInfo fallback to IPoiSpur's database is missing IPs (see other ticket for details) which could be covered by MaxMind's locationGeoLite2 data?abases. From a technical perspective,Historically, we decided to prefer MaxMind's location/asn/isp data over Spur but 1. never wrote in fallback functionality and 2. never returned that data from Spur. MaxMind splits their location data into city/state/country and we record feed data similarly so we would be able to retain the basic-view country vs full-view city level access: ``` MariaDB [ipoid]> select * from actor_data limit 1; +------+-----------+-------------------------------------------+--------------+-------+-----------+------------+--------------+-----------+------------------+-------+--------------+ | pkid | ip | org | client_count | types | conc_city | conc_state | conc_country | countries | location_country | risks | last_updated |However now that we no longer use the Enterprise dataset, we might instead choose to prioritize Spur in all cases and fall back to MaxMind's Asn/City databases when Spur lacks the data( specifically, this is happening when Spur is missing the entire IP object as opposed to just the location/organization data, which it flat out isn't passing back). Acceptance Criteria: +------+-----------+-------------------------------------------+--------------+-------+-----------+------------+--------------+-----------+------------------+-------+--------------+- Confirm that GeoLite2 data is being passed through (the handlers already exist but may not be in use) | 1 | N/A | APNIC and Cloudflare DNS Resolver project | 1 | 1 | Tripoli | Tripoli | LY | 1 | AU | 0 | 1705653487 |- Implement a fallback to MaxMind data when Spur is missing the data (location from City.mmdb, asn from ASN.mmdb) Bonus Criteria: +------+-----------+-------------------------------------------+--------------+-------+-----------+------------+--------------+-----------+------------------+-------+--------------+- Pass back location/org data from Spur (They're already being saved to the database) ```- Implement Spur as a source for these data points in widgets