University of Oregon RouteViews Project
This Product utilizes data provided by RouteViews (www.routeviews.org). Use of this data is subject to the CC BY 4.0 license.
With contributions from network operators and volunteers all over the world, RouteViews collects BGP data by direct peering at Internet Exchange Points (IXPs) or multi-hop peering. Data are archived and made publicly available for download at archive.routeviews.org, lg.routeviews.org, and api.routeviews.org.
How BGPScout uses it: RouteViews MRT route collector dumps are parsed for the global routing table - the prefixes each ASN advertises, and the AS adjacencies observed in AS_PATHs.
RIPE NCC Routing Information Service (RIS)
The RIPE Routing Information Service (RIS) is a RIPE NCC service. With the help of network operators all over the world, RIS employs a globally distributed set of Remote Route Collectors (RRCs), typically located at Internet Exchange Points, to collect and store Internet routing data. Volunteers peer with the RRCs using the BGP protocol and RIS stores the update and withdraw messages. RIS data can be accessed via:
- RIPEstat, the "one-stop shop" for all available information about Internet number resources. RIPEstat uses individual widgets to display routing and other information;
- RIS Live, a real time BGP streaming API allowing server-side filtering of BGP messages by prefix or autonomous system;
- RIS Raw Data, available for each route collector, with state dumps and batches of updates made available periodically;
- RISwhois, that searches the latest RIS data for details of an IP address using a plaintext "whois"-style interface. It is useful when querying RIS data using scripts.
How BGPScout uses it: RIS route collector data contributes to the global routing table BGPScout reports on, alongside RouteViews.
RIPE Atlas
How BGPScout uses it: Traceroute measurements run from RIPE Atlas probes, and the published daily probe metadata archive, which supplies the source country of an Atlas-originated trace. Probe country codes are self-declared by the probe host and are not verified by the RIPE NCC.
CAIDA UCSD PeeringDB Dataset
The CAIDA UCSD PeeringDB Dataset, 2018-03-11 - 2026-07-01, https://www.caida.org/catalog/datasets/peeringdb/
How BGPScout uses it: CAIDA's archive of historical PeeringDB snapshots supplies the interconnection history that PeeringDB's own API cannot - which networks were present at which exchanges and facilities on a given date. The attribution above is required by CAIDA's Acceptable Use Agreement and the date range names exactly the snapshots loaded.
MaxMind GeoLite2
Free IP geolocation data provided by MaxMind, creator of GeoIP®.
This product includes GeoLite Data created by MaxMind, available from https://www.maxmind.com.
How BGPScout uses it: IP-to-location lookups for traceroute hops and announced address space. Geolocation is an estimate, never a measurement of where equipment physically is.
PeeringDB
How BGPScout uses it: Interconnection data - exchange and facility membership, port capacity, network contact and traffic-level fields. All of it is operator self-reported; BGPScout presents it as such and does not treat it as measured.
bgp.tools
How BGPScout uses it: ASN names and the network-category tags (CDN, DDoS mitigation, anycast, RPKI-validating, hosting and others) shown on ASN pages and in search filters.
How BGPScout uses it: Published delegated-extended statistics, transfer logs, RDAP and WHOIS - the allocation and transfer record for every ASN and IP block, and organisation names and addresses where a registry publishes them.
Nic.br and the Brazilian Federal Revenue Service
How BGPScout uses it: LACNIC publishes no organisation address for Brazilian networks. Nic.br's published ASN block file supplies the CNPJ company identifier, which is resolved against the Receita Federal business registry for a registered address. That is a company's fiscal address, which for a large operator may be a head office far from the network, and it is labelled as such wherever it is shown.