This is the multi-page printable view of this section. Click here to print.

Return to the regular view of this page.

BGP Sources

Public sources of historical BGP data, generally RIBs and Updates.

1 - Lost Sources of BGP Data

Some sources of BGP RIBs and updates are known to have existed, but no known copy exists. If you have a copy of any of these, please share!

Renesys (2000-2014)

Internet2 backbone (2012-2014?)

2 - Packet Clearinghouse

“Research Packet Clearing House investigates technological, economic, and policy issues in areas related to Internet traffic exchange.

“PCH’s longest-running research project is the Internet Routing Topology Archive, a database of Internet topology measurements begun in 1997. This archive of routing data from all major and many minor Internet provider networks is available to academic and commercial researchers and the operations community, to aid in the understanding of the dynamic nature and topology of the Internet.

“Other topics of ongoing research include the economic impact of local traffic exchange in developing nations, inter-provider notifications and communication, and database schemas for topological data.

“Packet Clearing House facilitates research, instruments the Internet, collects, archives, and disseminates information and data, and creates a climate conducive to analytical examination of all aspects of Internet topology, operational practice, and economics. Although we have collected and maintain the world’s largest database of Internet routing information, we prefer to put researchers in academia together with the data that they need, rather than analyze all the data we collect ourselves - a task beyond the capacity of any one organization. We believe that, by facilitating partnerships between industry and academia and enabling communication between the two communities, we can achieve a more enduring beneficial effect.”

CollectorURLLocationStart DateNotes

3 - RIPE Routing Information 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.”

Terms of Service

CollectorURLLocationStart DateNotes
rrc00https://data.ris.ripe.net/rrc00/RIPE-NCC Multihop, Amsterdam03 Sep 1999
rrc01https://data.ris.ripe.net/rrc01/LINX / LONAP, London27 Jul 2000
rrc02https://data.ris.ripe.net/rrc02/retired24 Mar 2001ends 2 Oct 2008
rrc03https://data.ris.ripe.net/rrc03/AMS-IX / NL-IX, Amsterdam17 Jan 2001
rrc04https://data.ris.ripe.net/rrc04/CIXP, Geneva04 Apr 2001
rrc05https://data.ris.ripe.net/rrc05/VIX, Vienna13 Jun 2001
rrc06https://data.ris.ripe.net/rrc06/DIX-IE / JPIX, Tokyo30 Aug 2001
rrc07https://data.ris.ripe.net/rrc07/Netnod, Stockholm04 Apr 2002
rrc08https://data.ris.ripe.net/rrc08/retired07 May 2002ends 2 Sep 2004
rrc09https://data.ris.ripe.net/rrc09/retired10 May 2003ends 4 Feb 2004
rrc10https://data.ris.ripe.net/rrc10/MIX, Milan10 May 2003
rrc11https://data.ris.ripe.net/rrc11/NYIIX, New York City13 Feb 2004
rrc12https://data.ris.ripe.net/rrc12/DE-CIX, Frankfurt06 Jul 2004
rrc13https://data.ris.ripe.net/rrc13/MSK-IX, Moscow24 May 2005
rrc14https://data.ris.ripe.net/rrc14/PAIX, Palo Alto01 Jan 2005
rrc15https://data.ris.ripe.net/rrc15/PTTMetro, Sao Paulo14 Dec 2005
rrc16https://data.ris.ripe.net/rrc16/NOTA, Miami01 Feb 2008
rrc17unavailable
rrc18https://data.ris.ripe.net/rrc18/Catnix, Barcelona04 Nov 2015
rrc19https://data.ris.ripe.net/rrc19/NAP Africa JB, Johannesburg28 Jan 2016
rrc20https://data.ris.ripe.net/rrc20/SwissIX, Zurich04 Nov 2015
rrc21https://data.ris.ripe.net/rrc21/France-IX, Paris04 Nov 2015
rrc22https://data.ris.ripe.net/rrc22/InterLAN, Bucharest22 Dec 2017RIBs only before 08 Jan 2018
rrc23https://data.ris.ripe.net/rrc23/Equinix SG, Singapore22 Dec 2017RIBs only before 08 Jan 2018
rrc24https://data.ris.ripe.net/rrc24/LACNIC Multihop, Montevideo22 Feb 2019
rrc25https://data.ris.ripe.net/rrc25/RIPE-NCC Multihop, Amsterdam18 Feb 2021
rrc26https://data.ris.ripe.net/rrc26/UAE-IX, Dubai1 Jul 2021

4 - Oregon Routeviews

“The University’s RouteViews project was initially conceived as a tool for Internet operators to obtain real-time information about the global routing system from the perspectives of several different backbones and locations around the Internet. Although other tools handle related tasks, such as the various Looking Glass Collections (see e.g., TRACEROUTE.ORG), they typically either provide only a constrained view of the routing system (e.g., either a single provider or the route server) or they do not provide real-time access to routing data.

“While the RouteViews project was initially motivated by interest on the part of operators in determining how the global routing system viewed their prefixes and/or AS space, there have been many other interesting uses of this RouteViews data. For example, NLANR has used RouteViews data for AS path visualization and to study IPv4 address space utilization (archive). Others have used RouteViews data to map IP addresses to origin AS for various topological studies. CAIDA has used it in conjunction with the NetGeo database in generating geographic locations for hosts, functionality that both CoralReef and the Skitter project support.”

CollectorURLLocationStart DateNotes
route-views2https://archive.routeviews.org/bgpdata
route-views3https://archive.routeviews.org/route-views3/bgpdata
route-views4https://archive.routeviews.org/route-views4/bgpdata
route-views5https://archive.routeviews.org/route-views5/bgpdata
route-views6https://archive.routeviews.org/route-views6/bgpdata
route-views.amsixhttps://archive.routeviews.org/route-views.amsix/bgpdata
route-views.bdixhttps://archive.routeviews.org/route-views.bdix/bgpdata
route-views.bknixhttps://archive.routeviews.org/route-views.bknix/bgpdata
route-views.chicagohttps://archive.routeviews.org/route-views.chicago/bgpdata
route-views.chilehttps://archive.routeviews.org/route-views.chile/bgpdata
route-views.eqixhttps://archive.routeviews.org/route-views.eqix/bgpdata
route-views.flixhttps://archive.routeviews.org/route-views.flix/bgpdata
route-views.gixahttps://archive.routeviews.org/route-views.gixa/bgpdata
route-views.gorexhttps://archive.routeviews.org/route-views.gorex/bgpdata
route-views.ischttps://archive.routeviews.org/route-views.isc/bgpdata
route-views.kixphttps://archive.routeviews.org/route-views.kixp/bgpdata
route-views.jinxhttps://archive.routeviews.org/route-views.jinx/bgpdata
route-views.linxhttps://archive.routeviews.org/route-views.linx/bgpdata
route-views.mwixhttps://archive.routeviews.org/route-views.mwix/bgpdata
route-views.napafricahttps://archive.routeviews.org/route-views.napafrica/bgpdata
route-views.nwaxhttps://archive.routeviews.org/route-views.nwax/bgpdata
route-views.laxhttps://archive.routeviews.org/pacwave.lax/bgpdata
pit.sclhttps://archive.routeviews.org/pit.scl/bgpdata
route-views.phoixhttps://archive.routeviews.org/route-views.phoix/bgpdata
route-views.telxatlhttps://archive.routeviews.org/route-views.telxatl/bgpdata
route-views.widehttps://archive.routeviews.org/route-views.wide/bgpdata
route-views.sydneyhttps://archive.routeviews.org/route-views.sydney/bgpdata
route-views.saopaulohttps://archive.routeviews.org/route-views.saopaulo/bgpdata
route-views2.saopaulohttps://archive.routeviews.org/route-views2.saopaulo/bgpdata
route-views.sghttps://archive.routeviews.org/route-views.sg/bgpdata
route-views.perthhttps://archive.routeviews.org/route-views.perth/bgpdata
route-views.peruhttps://archive.routeviews.org/route-views.peru/bgpdata
route-views.sfmixhttps://archive.routeviews.org/route-views.sfmix/bgpdata
route-views.siexhttps://archive.routeviews.org/route-views.siex/bgpdata
route-views.soxrshttps://archive.routeviews.org/route-views.soxrs/bgpdata
route-views.riohttps://archive.routeviews.org/route-views.rio/bgpdata
route-views.fortalezahttps://archive.routeviews.org/route-views.fortaleza/bgpdata
route-views.uaeixhttps://archive.routeviews.org/route-views.uaeix/bgpdata
route-views.nyhttps://archive.routeviews.org/route-views.ny/bgpdata

“Note: MRT RIB and UPDATE files have internal timestamps in the standard Unix format, however the file names are constructed based on the time zone setting of the collector. The collectors had their time zones set to Pacific Time prior to Feb 3, 2003 at approximately 19:00 UTC. At that time all but one of the existing collectors had their time zones reset to UTC. The one exception was routeviews.eqix which was not reset to UTC until Feb 1, 2006 at approximately 21:00 UTC.”