Skip to main content

Prefixes

Quick summary​

Real-time views of BGP resources, based on the AS and prefix filters you have setup. BGP resources are the prefixes, ASNs, BGP Peerings, Routes and RPKI ROAs that contain the configured AS(es) as origin or anywhere in the AS path, depending on the selected option in "Setup | Data Services", as well as additional prefixes you might have configured.

Each table row represents a BGP resource. Click on each row to reveal the data source(s) used to extract it from. Click on any column to sort the data based on it.

Data Sources (#) display the total number of sources that have seen each BGP resource (Prefix, AS or Peering). Data Sources (%) display the ratio of sources that have seen each BGP resource divided by all the active sources.

Details​

We form the real-time view of the prefixes seen on the BGP updates we collect from the various data services. Note that these are filtered resources according to either the AS filters (originating or being present in paths to prefixes based on Origin or Any configuration in data services) or the Prefix filters. If we receive a BGP announcement towards prefix 38.124.249.0/24, we show it if any of the following conditions hold:

  1. The prefix is announced by an AS filter and the corresponding data services are configured for Origin AS filtering.
  2. The path to the prefix contains an AS filter in any location and the corresponding data services are configured for Any AS filtering.
  3. The prefix is an exact-match of a sub-prefix of a Prefix filter.

Prefixes have the following fields:

  • Prefix in CIDR format, e.g., 38.124.249.0/24
  • Origin AS as the AS originating the prefix, e.g., 10886. Note that multiple ASes may originate a single prefix in a Multiple Origin AS (MOAS) case. In that case they are a blank-separate list of ASes.
  • Data Sources (#) as the total number of data sources that have seen the prefix.
  • Data Sources (%) as the ratio of data sources that have seen the prefix divided by all the active data sources.

Hidden fields include:

  • IP Version (4 for IPv4, 6 for IPv6)
  • Mask Length as the CIDR length of the prefix. E.g., 38.124.249.0/24 has a mask length of 24.

Prefix information can be filtered based on all these fields (incl. the hidden ones). Data Source (# or %) min-max filters are supported.

Note that prefixes can be filtered on Prefix with fully compliant POSIX regular expressions. Here are some examples for prefix filtering:

  • All /24s that are sub-prefixes of 139.91.0.0/16: 139\.91\.(\d+)\.(\d+)\/24
  • All sub-prefixes of 2001:468::/32: 2001\:468

The filtered table can be exported to CSV.

Finally, each Prefix row is expandable and exhibits an inner table with all data sources that see the prefix. The inner data source table can be filtered (and CSV-exported) based on the following fields:

  • Data Service, e.g., RIS Live
  • Route Collector, e.g., RRC13 (applies only to RIS Live data service)
  • IP, e.g., 195.208.209.4 (that is the IP address of the interface of the monitor peer router)
  • ASN, e.g., 41095 (that is the ASN of the monitor peer router)
  • City, e.g., Sao Paulo (that is the city of the location of the interface of the monitor peer router)
  • Country, e.g., Brazil (that is the country of the location of the interface of the monitor peer router)
  • Continent, e.g., South America (that is the continent of the location of the interface of the monitor peer router)

Location information is extracted on a best effort basis based on availability. We use IPmap for this purpose.

Screenshots​

Main tab​

Filters​

Columns​

Data Sources​