RIPE Database Search

By pressing the "Search" button you explicitly express your agreement with the RIPE Database Terms and Conditions.

RIS Raw Data

This page links to the raw data collected by the RRCs using Quagga routing software, stored in MRT format. This format is described in an IETF draft. These files can be read using libbgpdump, a library written in C by Dan Ardelean, currently maintained by the RIPE NCC. A Python library also exists, PyBGPdump which provides access to MRT files via Python.

All RIS tools handle 32-bit AS numbers, complying with the guidelines set out in the Internet Draft 'Canonical Textual Representation of 4-byte AS Numbers'.

Two sets of files are available for each of the RRC's:

  • All BGP packets, created with the Zebra command "dump bgp all ...". The filenames start with updates and are created every five minutes.

  • The entire BGP routing table, created with the Zebra command "dump bgp routes-mrt ...". These files are created every eight hours, the filenames start with bview.

BGP Timer settings since 23 November 2006:

  • Keepalives:
    • 60 seconds
  • Holddown:
    • 180 seconds

BGP Timer settings between 17 October 2002 and 23 November 2006:

  • Keepalives:
    • 0 (disabled)
  • Holddown:
    • 0 (disabled)

BGP Timer settings before 17 October 2002:

  • Keepalives:
    • 60 seconds
  • Holddown:
    • 180 seconds

Please note that this machine is connected to the Internet over a link that is loaded during Amsterdam office hours. If you want to download a large number of files, please do so at a spread-out rate, preferably at a time outside Amsterdam office hours (08:00 - 18:00 UTC).

Click on a collector to get a list of available files. Files are grouped collector by collector, then month by month.

  • rrc00.ripe.net at RIPE NCC, Amsterdam, collects default free routing updates from peers. From October 1999.

  • rrc01.ripe.net at LINX, London. Collects route updates announced by LINX members. From July 2000.

  • rrc02.ripe.net at SFINX, Paris. Collected route updates announced by SFINX members from March 2001 until October 2008.

  • rrc03.ripe.net at AMS-IX, Amsterdam. Collects route updates announced by AMS-IX members. From January 2001.

  • rrc04.ripe.net at CIXP, Geneva. Collects route updates announced by CIXP members. From April 2001.

  • rrc05.ripe.net at VIX, Vienna. Collects route updates announced by VIX members. From June 2001.

  • rrc06.ripe.net at Otemachi, Japan. Collects route updates announced by JPIX members. From August 2001.

  • rrc07.ripe.net in Stockholm, Sweden. Collects route updates announced by the NETNOD members. From April 2002.

  • rrc08.ripe.net at San Jose (CA), USA. Collected routing updates announced by the MAE-WEST members from May 2002 until September 2004.

  • rrc09.ripe.net at Zurich, Switzerland. Collected route updates announced by the TIX members. From May 2003 to until early Feb 2004.

  • rrc10.ripe.net at Milan, Italy. Collects route updates announced by the MIX members. From Nov 2003.

  • rrc11.ripe.net at New York (NY), USA. Collects route updates announced by the NYIIX members. From Feb 2004.

  • rrc12.ripe.net at Frankfurt, Germany. Collects route updates announced by the DE-CIX members. From Jul 2004.

  • rrc13.ripe.net at Moscow, Russia. Collects route updates announced by the MSK-IX members. From Apr 2005.

  • rrc14.ripe.net at Palo Alto, USA. Collects route updates announced by the PAIX members. From Dec 2004.

  • rrc15.ripe.net at Sao Paulo, Brazil. Collects route updates announced by the PTTMetro-SP members. From Dec 2005.

  • rrc16.ripe.net at Miami, USA. Collects route updates announced by the NOTA members. From Feb 2008.

This data is made available for researchers without restrictions. However, if you copy the data and publish an analysis, please send us a pointer to the paper or website for our analysis page and we will reference it on our list of articles with RIS analysis.