RIS Raw Data

This page is out of date and has been archived. The new page on this topic can be found here.

This page links to the raw data collected by the RRCs stored in MRT format. This format is described in RFC6396. These files can be read using bgpdump, 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.

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

  • All BGP packets received by the collectorThe filenames start with updates and are created every five minutes.

  • The entire BGP routing table of the collector, at 00:00, 08:00, and 16:00 UTC. 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

Use following links to get lists of available files. Files are grouped per month.

  • rrc00.ripe.net multihop collector at RIPE NCC, Amsterdam, collects updates from peers around the world from October 1999.

  • rrc01.ripe.net at LINX and LONAP, London. Collects route updates announced by LINX members from July 2000.  Collects routes announced by LONAP members from March 2018.

  • 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 and NL-IX, Amsterdam. Collects route updates announced by AMS-IX and NL-IX members, from January 2001. Collected route updates announced by GN-IX members from January 2001 until July 2015.

  • 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.

  • rrc18.ripe.net at Barcelona, Spain. Collects route updates announced by the CATNIX members from Nov 2015.

  • rrc19.ripe.net at Johannesburg, South Africa. Collects route updates announced by the NAP Africa JB members from Jan 2016.

  • rrc20.ripe.net at Zurich, Switzerland. Collects route updates announced by the SwissIX members from Nov 2015.

  • rrc21.ripe.net at Paris, France. Collects route updates announced by the FranceIX Paris and Marseille members from Nov 2015.

  • rrc22.ripe.net at Bucharest, Romania. Collects route updates announced by the Interlan members from Jan 2018.

  • rrc23.ripe.net at Singapore. Collects route updates announced by the Equinix SG members from Jan 2018.

  • rrc24.ripe.net multihop collector at LACNIC, Montevideo, Uruguay. Collects routing updates from peers in the LACNIC region from February 2019.

  • rrc25.ripe.net multihop collector at RIPE NCC, Amsterdam, collects routing updates from peers in the RIPE NCC region from February 2021.

  • rrc26.ripe.net at Dubai, UAE. Collects routing data from UAE-IX members since July 2021.

This data is made available to anyone without restrictions. If you copy the data and publish an analysis, please contact ris _at_ ripe _dot_ net with a pointer to the paper or website. We also encourage you to publish an article about your findings on RIPE Labs.

The use of RIS data for commercial purposes is subject to separate terms and conditions, please see RIS Commercial Use.