What the Routing page exposes
Cloudflare Radar has added a Routing section that monitors the BGP messages exchanged across the Internet and derives insights on IP prefixes, individual networks, countries, and the Internet as a whole. BGP is the de facto inter-domain routing protocol: intra-domain routing moves packets between servers and routers inside one organization, while inter-domain routing takes over at the network edge to pick the next hop and hand traffic to the corresponding network. The new data lets users inspect the Internet's routing status, check secure routing protocol deployment for a country, spot routing anomalies, and validate IP block reachability, all from globally distributed vantage points.
Statistics at a glance
The "Routing Statistics" block summarizes the size and status of an autonomous system (AS), a country, or the Internet overall. It counts:
- ASes on the Internet or registered in a given country;
- distinct prefixes and the routes toward them in the global routing table, worldwide, by country, or by AS;
- routes categorized by RPKI validation result (valid, invalid, or unknown).
Each figure is broken down by IPv4 and IPv6 so the two protocols can be compared. For an individual network, the page also shows a BGP announcements volume chart for the past week, along with the network name, registration country, estimated user count, and sibling networks.
Anomaly detection
BGP carries known security weaknesses, and the Routing page consolidates the detection results for BGP route leaks and BGP hijacks in one place, showing events for a given network or globally. The BGP Route Leaks table lists detected leak events with the ASes involved, start and end times, and numeric statistics reflecting scale and impact. The BGP Origin Hijacks table lists detected potential origin hijacks; besides ASes, timing and impact, it shows the key evidence behind each event, giving context on why and how likely the event is a hijack.
This release adds a third detection: RPKI Invalid Multiple Origin AS (MOAS). A MOAS is a routing conflict in which multiple networks originate the same IP prefixes at the same time, contrary to best practice recommendations. The system examines recent global routing tables, identifies MOASes, and uses RPKI to single out events whose origins are proven invalid—cases less likely to be legitimate. Operators can then locate anomalies affecting their networks and act on them.
The Routing page is intended as the permanent home for BGP and routing data, with more anomaly detections and pipeline improvements to follow.
Assets and connectivity
Tens of thousands of ASes interconnect to form the Internet, varying in size and geography. Larger networks are generally better connected and act as upstreams; smaller ones are downstream. In an example topology, AS1 announces its prefixes to its upstream providers and the route propagates upward to the large networks AS3 and AS4, then downstream to smaller networks until it reaches AS6.
The page shows which prefixes an AS originates and how ASes interconnect, including prefix lists broken down by RPKI validation status and detected connectivity labeled as upstream, downstream, or peering. Users can search for any ASes upstream, downstream, or peers. For a country, the page lists all networks registered there, sorted by the number of prefixes originated, with search by network name or AS number.
API access and examples
Routing data is served by Cloudflare's developer API and is freely available under the Creative Commons Attribution-NonCommercial 4.0 (CC BY-NC 4.0) license. More APIs are planned as the section grows.
The prefix-to-origin mapping API returns the matching prefix-origin pairs observed in global routing tables, so users can find the networks originating a prefix or all prefixes a network originates. A cURL query for the network(s) behind 1.1.1.0/24 returns JSON showing Cloudflare (AS13335) as a RPKI valid origin, along with meta information such as the query's UTC timestamp and the data_time field for when the dataset was last updated.
The Radar APIs have also been integrated into BGPKIT monocle, an open-source command-line tool for searching BGP messages in public archives, looking up networks by name, and checking RPKI validation for a prefix. With the integration, monocle radar stats [QUERY] and monocle radar pfx2as retrieve routing statistics or prefix-to-origin mappings directly.
| API | Type |
|---|---|
| Get BGP origin hijack events | Anomaly detection |
| Get BGP route leak events | Anomaly detection |
| Get MOASes | Anomaly detection |
| Get BGP routing table stats | Routing information |
| Get prefix-to-origin mapping | Routing information |
| Get all ASes registered in a country | Routing information |
| Get AS-level relationship | Routing information |
curl --request GET \
--url "https://api.cloudflare.com/client/v4/radar/bgp/routes/pfx2as?prefix=1.1.1.0/24" \
--header 'Content-Type: application/json' \
--header "Authorization: Bearer YOUR_TOKEN"
{
"success": true,
"errors": [],
"result": {
"prefix_origins": [
{
"origin": 13335,
"peer_count": 82,
"prefix": "1.1.1.0/24",
"rpki_validation": "Valid"
}
],
"meta": {
"data_time": "2023-07-24T16:00:00",
"query_time": "2023-07-24T18:04:55",
"total_peers": 82
}
}
}


