Real-time views of Routes, based on the AS and prefix filters you have set up. The Routes in this table either originate from the AS(es) you have configured in Setup | AS Filters, or they contain the prefixes you configured in Setup | Prefix Filters, regardless of which AS originates them.
Each table row represents a Route, which includes the Prefix, AS Path, RPKI Status, and the timestamp of the last update related to that Route. Click on each row to display the sources (Code BGP Monitors, RIS Live peers, or your own routers) that have seen each Route, as well as their geolocation information.
Use the table filters to filter Routes based on all available fields. Note that the Prefix and AS Path filter fields support POSIX regular expressions.
Show Columns to hide unwanted data columns or reveal additional ones (
Download CSV to export the data in CSV format.
Share to copy a URL of the current Routes view.
We form the real-time view of the routes (to 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
Any configuration in data services) or the Prefix filters. If we receive a BGP announcement towards prefix
184.108.40.206/24, we show the corresponding route if any of the following conditions hold:
- The prefix is announced by an AS filter and the corresponding data services are configured for
- The path to the prefix contains an AS filter in any location and the corresponding data services are configured for
- The prefix is an exact-match of a sub-prefix of a Prefix filter.
Note that routes essentially "connect" prefixes and ASes logically, and are more generic than raw BGP updates. When a route is withdrawn, it is removed from the table. If all routes leading to a certain prefix are withdrawn, the prefix is also withdrawn (and deleted from the table). The same holds for ASes and peerings; if all routes containing a certain AS or peering are withdrawn, the corresponding entities are deleted from the tables.
Routes have the following fields:
Prefixin CIDR format, e.g.,
Origin ASas the AS originating the prefix, e.g.,
Neighbor ASas the next hop in the path. E.g., if the path to a certain prefix is
2 1, then
1is the origin AS and
2the neighbor. Note that for simplicity we consider the neighbors in self-sourced routes (e.g., routes with a single-hop AS path stemming from a directly connected BGP router), as the origin AS.
AS Pathas an ordered blank-separated list of ASes, with the origin AS on the rightmost side and the monitor AS on the leftmost side.
RPKI Statusas the RPKI status of the route. Can be:
Last Updateas the last BGP update timestamp related to the route (note that multiple BGP updates for the same route can be received).
Data Sources (#)as the total number of data sources that have seen the route.
Data Sources (%)as the ratio of data sources that have seen the route divided by all the active data sources.
Hidden fields include:
First Detectedas the timestamp of the first detection of the corresponding route by the system.
Route information can be filtered based on all these fields (incl. the hidden ones). Data Source (# or %) min-max filters are supported.
Note that routes can be filtered on
AS path with fully compliant POSIX regular expressions.
Here are some examples for AS path filtering:
- All routes passing via AS890:
- All routes where AS890 is present:
(^890\s)|(^890$)|(\s890$)|(\s890\s)(note that an AS can be origin, monitor or intermediary)
- All routes where AS890 is monitor:
- All routes originated by AS891 passing via its upstream AS890:
Moreover, routes can be filtered on
Prefix with fully compliant POSIX regular expressions.
Here are some examples for prefix filtering:
- All routes to /24s that are sub-prefixes of
- All routes to sub-prefixes of
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 Route row is expandable and exhibits an inner table with all data sources that see the route. 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)
220.127.116.11(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.