Introduction and Goals

While the Route Views project was originally 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 Route Views data. For example, NLANR has used Route Views data for AS path visualization (see also NLANR), and to study IPv4 address space utilization (archive). Others have used Route Views 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.

Other analyses using route-views data include:

• Cyclops A useful system for detecting routing anomalies involving your network.

• BGP::Inspect An indexed subset (5 peers) of routeviews data with a simple query interface.

• A tool for visualizing BGP routing changes

• Geoff Huston's analysis of BGP routing table dynamics

• Sean Mccreary's work on routing table growth

• Bradley Huffaker's analysis of the geographic scope of routing announcements, mapping ASes, announced prefixes, and IPv4 address space to the country that is administratively responsible for routing them.

Services

Host	MFG	BGP Proto	UI	Location
route-views.routeviews.org (route-views.oregon-ix.net)	Cisco	IPv4 uni/multi-cast multi-hop	telnet	U of Oregon, Eugene Oregon, USA
route-views2.routeviews.org	Quagga	IPv4 uni/multi-cast multi-hop	telnet	U of Oregon, Eugene Oregon, USA
route-views3.routeviews.org	Quagga	IPv4 uni/multi-cast multi-hop	telnet	U of Oregon, Eugene Oregon, USA
route-views4.routeviews.org	Quagga	IPv4/IPv6 uni/multi-cast multi-hop	telnet	U of Oregon, Eugene Oregon, USA
route-views6.routeviews.org	Zebra	IPv6 multi-hop	telnet	U of Oregon, Eugene Oregon, USA
route-views.eqix.routeviews.org	Zebra	IPv4/v6 uni/multi-cast non-multi-hop	telnet	Equinix, Ashburn, VA
route-views.isc.routeviews.org	Zebra	IPv4/v6 uni/multi-cast non-multi-hop	telnet	ISC (PAIX), Palo Alto CA, USA
route-views.kixp.routeviews.org	Zebra	IPv4 uni/multi-cast non-multi-hop	telnet	KIXP, Nairobi, Kenya
route-views.linx.routeviews.org	Zebra	IPv4/v6 uni/multi-cast non-multi-hop	telnet	LINX, London, GB
route-views.nwax.routeviews.org	Zebra	IPv4/v6 uni/multi-cast non-multi-hop	telnet	NWAX, Portland, Oregon
route-views.wide.routeviews.org	Zebra	IPv4/6 uni/multi-cast non-multi-hop	telnet	DIXIE (NSPIXP), Tokyo, Japan
route-views.sydney.routeviews.org	Zebra	IPv4/6 uni/multi-cast non-multi-hop	telnet	SYDNEY (SYD1 Equinix), Sydney, Australia
route-views.saopaulo.routeviews.org	Zebra	IPv4/6 uni/multi-cast non-multi-hop	telnet	SAOPAULO (PTT Metro, NIC.br), Sao Paulo, Brazil
route-views.telxatl.routeviews.org	Zebra	IPv4/6 uni/multi-cast non-multi-hop	telnet	TELXATL (TELX Atlanta), Atlanta, Georgia
bgpmon.routeviews.org	BGPMon (Experimental)	See: This Link for more information		Colorado State University Fort Collins, CO
archive.routeviews.org	UO	The data archive Includes asn.routeviews.org zone files	http ftp	U of Oregon, Eugene Oregon, USA
bgplay.routeviews.org	BGPlay	BGP update player	http	U of Oregon, Eugene Oregon, USA
zebra.routeviews.org		BGP Beacon prefix 192.135.183.0		U of Oregon, Eugene Oregon, USA

For more information on BGP beacons, see http://www.psg.com/~zmao/BGPBeacon.html.

There are two sub-domains of TXT reconds in routeviews.org, asn and aspath. asn.routeviews.org maps (resolves) a reversed IPv4 address or prefix (eg: 128.223 -> 223.128.asn.routeviews.org) to the origin AS (and prefix and prefix length) of the best route as seen by route-views2.routeviews.org. aspath.routeviews.org is the same idea, but resolves to the full AS path. This data can be obtained via FTP from ftp.routeviews.org/dnszones/

Prefixes which are not in the BGP RIB at the time that the zones are generated will have the AS or AS path value 4294967295 and the prefix and length will be 0 (zero).

These zones are built twice per-day, 11:45 and 23:45 UTC. These zones are quite large. Reloading these produces a period of a few minutes during which the server will not reply.

Data Archives

Cisco BGP RIBs collected from route-views.routeviews.org (the collector script was written by Sean Mccreary) are available on http://archive.routeviews.org/. The data from 1997 through March 2001 was collected by NLANR/MOAT.

BGP RIBs and updates collected from our Zebra routers in MRT format are available via anonymous ftp (or http) on ftp://archive.routeviews.org/ (see also tools).

More about these data.

Bibliography

Implementation

The Route Views routers, route-views.routeviews.org , use multi-hop BGP sessions (configuration examples) to peer with backbones and other ASes at interesting locations. Route Views uses AS6447 in its peering sessions and routes received from neighbors are never passed on nor used to forward traffic. Finally, route-views.routeviews.org itself does not announce any prefixes.

Tools

Tools for collection and manipulation of Route-Views data.

Current Participants

ASes currently contributing views (thank you!) are listed separately for each Route-Views router with which they peer.

Current Events

Funding Sources

Co-location and transit for route-views.eqix.routeviews.org generously provided by Equinix.

Co-location and transit for route-views.linx.routeviews.org generously provided by the LINX.

Co-location and transit for route-views.isc.routeviews.org (PAIX) generously provided by the Internet Systems Consortium, Inc. (ISC).

Co-location and transit for route-views.wide.routeviews.org generously provided by the WIDE project along with very friendly support from Akira Kato.

Questions or Comments?