Data sources

University of Oregon RouteViews Project

CC BY 4.0 ·www.routeviews.org ·licence terms

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. The vantage points are chosen for geographic and topological spread rather than raw count, because a network that peers regionally is disproportionately visible from a nearby one and invisible from a distant one.

RouteViews vantage points in the build that produced the data now being served (2026-10-11): route-views.chicago, route-views.eqix, route-views.linx, route-views.napafrica, route-views.sydney, route-views.wide, route-views2, route-views2.saopaulo.

What more vantage points do NOT do is turn the result into a peer census. A RIB dump carries only the best path per prefix per collector peer, so an adjacency that is never the best path anywhere - the normal case for settlement-free peering across an exchange route server - is absent from every collector, at any collector count.

RIPE NCC Routing Information Service (RIS)

ripe.net/ris ·commercial use conditions ·Terms of Service

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. RIS collectors are in the AS-adjacency build to add vantage points RouteViews' own set does not have, particularly outside North America and Europe.

RIPE RIS vantage points in the build that produced the data now being served (2026-10-11): rrc00, rrc11, rrc19, rrc24.

What this is not: Neither RouteViews nor RIS labels a relationship. An AS_PATH records that two ASNs were adjacent along an observed route, which conflates transit, settlement-free peering, siblings and misconfigurations - it is not a peering agreement or a customer list, from us or from any other tool built on the same public data.

RIPE Atlas

atlas.ripe.net ·Terms of Service

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.

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.

The CAIDA AS Relationships Dataset, 2026-09-01, https://www.caida.org/catalog/datasets/as-relationships/

How BGPScout uses it: Each network's providers, customers and peers, and the tier shown on network pages, come from CAIDA's monthly inference over public BGP data. The customer cone on those pages is counted from these relationships, month-to-month transit provider changes are read by comparing one month with the next, and the networks CAIDA lists as Internet exchange route servers are labelled as such rather than given a tier. The inference is CAIDA's; BGPScout shows it with this attribution and the month it describes.

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.

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.

How BGPScout uses it: The public list of RING nodes - the shared measurement machines networks host for one another - supplies the line on network pages saying how many nodes a network hosts and in which cities. Where a node's stated data centre carries exactly the same name as a PeeringDB facility in the same city, the facility is linked; otherwise only the city is shown.

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: The record of which networks host CDN caches - Google GGC, Netflix OCA, Meta FNA, Akamai, Microsoft, Apple and AWS CloudFront - shown on ASN pages, on /cdns and in CDN search filters. His methodology identifies cache nodes by the TLS certificate common name presented on port 443.

Published as a research dataset with no stated licence. We are grateful for it, we have not modified the underlying observations, and we will remove or amend this on request.

How BGPScout uses it: Microsoft's own lists of ExpressRoute connectivity providers by peering location, and of Azure Peering Service partners by metro, shown on ASN pages and on the peering program pages. Reformatted by BGPScout. The link from a listed provider to a network is ours, made only where the provider's exact name identifies one network, and is not part of Microsoft's list.

How BGPScout uses it: Google's own lists of Partner Interconnect service providers by metro, and of the colocation facilities where it offers Dedicated Interconnect, shown on ASN pages, facility pages and the peering program pages. Reformatted by BGPScout. The links from a listed provider to a network, and from a listed building to a PeeringDB facility, are ours and are not part of Google's lists.

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.

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.

EMODnet Human Activities, Telecommunication and power cables, Actual Routes. Aggregated by Cogea for the European Commission (European Marine Observation and Data Network). Data originator: Cogea Srl.

EMODnet Human Activities is funded by the European Commission and brings marine data on human activity in EU waters into a single portal. The cables dataset aggregates surveyed routes published by national hydrographic offices - among them SHOM (France), BSH (Germany) and Rijkswaterstaat (Netherlands) - and is updated annually. Validation of each contribution remains with the originating office.

How BGPScout uses it: Surveyed submarine cable routes are drawn as a context layer beneath the observed city-to-city links on the traceroute maps. It is context, not a claim about our measurements: we observe traffic between two cities and never observe which cable carried it, so no link is attributed to a cable. Coverage is European waters only (with some French-territory routes further afield, via SHOM's remit), so a sea with no cable drawn on it is outside the dataset rather than empty. A small number of trans-oceanic links are additionally routed along a plausible cable's own surveyed path, where one lands close to both observed cities - checked against 4,418 trans-oceanic city pairs, this matched 33 (2026-08-22). Those links are drawn dashed and labelled illustrative wherever it is ambiguous between several cables; every other link keeps the plain great-circle path. See the map's own legend for detail - City-to-City Path Segments.

How BGPScout uses it: Route origin authorisations decide whether each announced prefix is RPKI valid, invalid or not covered, and each network's signed provider declaration (ASPA) is shown on its page next to the providers seen in routing data. The objects are published by the address holders through the five Regional Internet Registries' trust anchors; validation is rpki-client's, published daily by Cloudflare.

How BGPScout uses it: IP geolocation, used under licence alongside MaxMind to place traceroute hops and announced address space, and to estimate where CDN caches sit. Geolocation is an estimate, never a measurement of where equipment physically is.

How BGPScout uses it: Country and network for IP addresses, one of the inputs that place traceroute hops and address space.

How BGPScout uses it: Where a network publishes the location of its own address space, that statement is used ahead of estimated geolocation.

How BGPScout uses it: A research ranking of popular websites, used to choose which domains to profile and to show their popularity.

How BGPScout uses it: Public certificate logs, used to discover a domain's hostnames before they are resolved.

How BGPScout uses it: The estimated number of internet users seen from each network, per country, shown on network pages as an estimate with its date.

How BGPScout uses it: Company facts - employees, revenue, industry - for networks whose own Wikidata entry names their AS number.

How BGPScout uses it: Whether an address or prefix appears on this public blocklist, shown in lookups with the date it was first seen and a link to the list's own removal page. Level 3 names whole networks and is shown as a statement about the network, not about one address.

How BGPScout uses it: Whether an address or prefix appears on this public blocklist, shown in lookups with the date it was first seen and a link to the list's own removal page.

How BGPScout uses it: Whether an address or prefix appears on this public blocklist, shown in lookups with the date it was first seen and a link to the list's own removal page.

How BGPScout uses it: Whether an address or prefix appears on this public blocklist, shown in lookups with the date it was first seen and a link to the list's own removal page.

How BGPScout uses it: A live check of whether a single address is listed, with a link to DroneBL's own lookup.

How BGPScout uses it: A live check of whether a single address is listed, with a link to JustSpam's own lookup.

How BGPScout uses it: Marks addresses that are Tor exit relays. This describes how an address is used and never counts as a blocklist listing.

How BGPScout uses it: BGP communities are decoded only with the meaning their owner publishes - currently 40 networks and 19 exchanges. Each definition keeps a link to the page it came from and the date it was read. Where an operator publishes a pattern rather than exact values, it is not expanded or guessed.

How BGPScout uses it: Exchanges that publish their member list in the IX-F export format, and mark it public, supply membership, connection counts and peering-LAN addresses, compared on exchange pages with what PeeringDB lists. Contact details in those exports are never stored.

How BGPScout uses it: Which networks each provider lists in its published partner programs, at which tier and in which metros, shown on program pages and on each listed network's page. The listing is the provider's; BGPScout records when it was read and what changed.

How BGPScout uses it: The published participant list, shown as a participation flag on network pages. Participation is a commitment the network has made; it is not an audit of its routing.

How BGPScout uses it: Traceroute and MTR measurements run from Globalping's community probe network, alongside RIPE Atlas, to widen where paths are measured from.