RouteViews

RouteViews
Name	RouteViews
Established	1997
Discipline	Network measurement
Country	United States
Institution	University of Oregon

RouteViews is a long-running project that collects and distributes Border Gateway Protocol routing data from operational Autonomous Systems. It provides archived and near-real-time BGP routing information to researchers, network operators, and policy makers, enabling analysis of Internet topology, routing incidents, and interdomain dynamics. The project is operated by academic and research institutions in partnership with network operators and is widely cited in studies conducted by universities, standards organizations, and industry labs.

Overview

RouteViews aggregates Border Gateway Protocol feeds from multiple peering partners, Internet exchange points, and transit providers to produce routing tables and update streams. Its datasets support investigations by researchers at University of Oregon partner labs, analysts at RIPE NCC, engineers at Cisco Systems, and staff at Internet Society chapters. The archive complements measurement efforts by projects such as RIPE Atlas, CAIDA, DNSMON, NANOG, and IETF working groups, and is used alongside repositories like University of Michigan network archives, Los Alamos National Laboratory datasets, and public datasets from Amazon Web Services research programs.

History

The project began in the late 1990s with academic initiatives to observe global interdomain routing after major events such as the rapid commercial expansion of the Internet Assigned Numbers Authority era and the consolidation of routing practices around major providers like Sprint Corporation and AT&T. Early collaborators included researchers from University of Oregon, operators from regional networks like SURFnet, and consortia associated with Merit Network. Over time RouteViews expanded peering to include major transit providers, IXPs such as Equinix, and research networks like ESnet and GÉANT. Key historical analyses using the archive addressed incidents involving routing leaks, prefix hijacks studied in the context of operators such as Level 3 Communications and events recorded near the time of policy shifts influenced by organizations like ICANN and IANA.

Architecture and Data Collection

RouteViews collects BGP data by establishing passive peering sessions with routers operated by universities, content providers, and transit networks. Collector nodes run software compatible with implementations from vendors such as Cisco Systems, Juniper Networks, and open projects like Quagga and BIRD. Data formats follow specifications adopted by standards bodies including the IETF and are stored in formats inspired by tools used by groups at CAIDA and the MIT network research community. The infrastructure leverages time-synchronized servers with clock references traceable to NTP strata and sometimes to GPS receivers. Mirrors and processing nodes have been hosted at academic centers like University of California, San Diego, Carnegie Mellon University, and national labs such as Sandia National Laboratories.

Data Access and Tools

Researchers and operators access RouteViews datasets through FTP archives, rsync mirrors, and query interfaces used by projects like BGPstream and visualization tools built by teams at Google research and the Laboratory for Communication Engineering groups. Analysts combine RouteViews feeds with datasets from RIPE NCC route collectors, the MANRS initiative, and registries managed by ARIN, RIPE, APNIC, LACNIC, and AfriNIC. Tooling ecosystems include parsers and collectors referenced by Scapy-based toolchains, pandas workflows in academic studies at Stanford University, and graphing utilities developed at Princeton University and ETH Zurich. Educational materials leveraging RouteViews have appeared in curricula at University of Washington and workshops at conferences like SIGCOMM and USENIX.

Use Cases and Impact

RouteViews supports a broad set of applications: academic research into Internet topology by groups at University of California, Los Angeles and Columbia University; operational troubleshooting by network operators at CenturyLink and content providers including Netflix and Cloudflare; security research into prefix hijacking incidents investigated by teams at CERT/CC and FireEye; and policy analysis by stakeholders at ICANN and telecommunications regulators. The archive has enabled high-impact publications in venues such as SIGCOMM, IMC, and NDSS, and informed improvements in best current operational practices promulgated at NANOG meetings and by the MANRS community. RouteViews data has been cited in studies of Internet resilience during geopolitical events involving infrastructure operators like NTT Communications and in assessments of content delivery strategies by companies like Akamai Technologies.

Limitations and Criticism

Critiques of RouteViews note sampling bias because collector peers are concentrated among willing partners, which can under-represent regions served by smaller networks or emerging providers such as those predominant in parts of Africa and some Latin America. Comparisons with datasets from RIPE NCC and active measurements from RIPE Atlas highlight complementary strengths and gaps. Other limitations include time resolution and retention policies that differ from commercial telemetry offerings by firms like ThousandEyes and Cisco ThousandEyes, and challenges in attributing routing anomalies without auxiliary data from registries such as ARIN and APNIC. Privacy advocates and legal analysts from institutions like Harvard University and Stanford Law School have discussed the balance between open data and operator confidentiality in the context of publicly archived routing feeds.

Category:Internet measurement projects Category:Border Gateway Protocol