Real-time views of Peerings, based on the AS filters you have setup. The ASes in this table are configured in Setup | AS Filters, and appear in the column "Configured AS".
Each table row represents an AS level Peering, which is inferred based on the next hop in the AS Path. Click on each row to reveal the sources (Code BGP Monitors, RIS Live peers or your own routers) that have seen each Peering, along with their geolocation information. Click on any column to sort the data.
Data Sources (#) indicates the total number of peers that have seen each Peering.
Data Sources (%) shows the ratio of peers that have seen each Peering to the total number of active peers that could potentially see it.
Use the table filters to filter Routes based on all available fields.
Show Columns to hide unwanted data columns.
Download CSV to export the data in CSV format.
Share to copy a URL of the current Peerings view.
We form the real-time view of the AS-level Peerings seen on the BGP update paths we collect from the various data services. Note that these are filtered resources according to the AS filters. I.e., we show the peerings that are seen on the data and are related to configured AS filters (meaning that one side of the peering is a configured AS). If we receive a BGP announcement with the following AS path: "3 2 1", then we will extract two peerings starting from the rightmost side: 1-2 and 2-3. Out of those, we show the ones that have configured AS filters on one side.
Peerings have the following fields:
Configured AS, e.g.,
Neighbor AS, e.g.,
Data Sources (#)as the total number of data sources that have seen the AS.
Data Sources (%)as the ratio of data sources that have seen the AS divided by all the active data sources.
Peering information can be filtered based on all these fields. Data Source (# or %) min-max filters are supported. The filtered table can be exported to CSV. It can also be shared in a URL form with other Code BGP Platform users.
Finally, each Peering row is expandable and exhibits an inner table with all data sources that see the peering. The inner data source table can be filtered (and CSV-exported) based on the following fields:
Data Service, e.g.,
Route Collector, e.g.,
RRC13(applies only to
RIS Livedata service)
22.214.171.124(that is the IP address of the interface of the monitor peer router)
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.