Real-time views of Autonomous Systems (ASes), based on the AS filters you have setup. The ASes in this table are configured in Setup | AS Filters.
Each table row represents an AS. Click on a row to reveal the sources (Code BGP Monitors, RIS Live peers or your own routers) that have seen each AS, 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 Prefix.
Data Sources (%) shows the ratio of peers that have seen each AS 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 Autonomous Systems view.
We form the real-time view of the ASes 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 ASes that are seen on the data and are configured as AS filters. If we receive a BGP announcement with the following AS path: "3 2 1", then we will extract three ASes: 1, 2 and 3. Out of those, we show the ones that are also configured AS filters.
ASes have the following fields:
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.
AS 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 AS row is expandable and exhibits an inner table with all data sources that see the AS. 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)
188.8.131.52(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.