# Network & Routing Report

> The full picture of how a network is put together and reaches the internet. Give it a network or address block and get a health card: what it announces, who it peers and buys transit from, whether it leans dangerously on a single upstream, and how well its routes are protected. The one-look report for network engineers assessing reach and resilience.

*Source: https://www.whisper.security/docs/workflows/route-health*

---
## What it solves

Network engineers assessing a network’s resilience usually need to check announcements, peering, RPKI coverage and facility presence separately, and a network that looks fine on one of those axes can still have a single point of failure on another. A health card that reconciles all of them at once is what a BGP looking glass alone doesn’t give you.

## How it uses the graph

Traverses the BGP, RPKI, physical layers of the graph, in 16 steps:

01. **BGP status** _(BGP, RPKI, physical)_ — Reading the prefix's MOAS, anycast and withdrawn flags…
02. **MOAS conflicts** _(BGP, RPKI, physical)_ — Listing ASNs that also announce this prefix…
03. **RIR allocation** _(BGP, RPKI, physical)_ — Reading the prefix's RIR allocation…
04. **Origin history of the block** _(BGP, historical)_ — Reading who has announced this block over time…
05. **RPKI ROA coverage** _(BGP, RPKI, physical)_ — Listing prefixes the ASN's ROAs authorise…
06. **ROAs authorizing the network** _(RPKI)_ — Counting the ROAs that name this network as origin…
07. **Announced prefixes** _(BGP, RPKI, physical)_ — Listing the ASN’s prefixes, the most exposed first…
08. **Facilities & IXes** _(BGP, RPKI, physical)_ — Listing the ASN's facilities and exchanges…
09. **ASN reputation** _(BGP, RPKI, physical)_ — Reading the ASN's rank, customer cone and tags…
10. **ASN identity & registration** _(BGP, RPKI, physical)_ — ASN identity & registration…
11. **Routing posture of every prefix** _(BGP, RPKI)_ — Counting the network’s prefixes by RPKI state…
12. **Hijack and route-leak posture** _(BGP, RPKI)_ — Reading the network’s hijack and route-leak record…
13. **Transit providers, customers and peers** _(BGP)_ — Sorting the network’s BGP neighbours into providers, customers and peers…
14. **Its transit providers** _(BGP)_ — Listing the transit providers, the biggest first…
15. **Upstreams seen on observed AS paths** _(BGP)_ — Reading the networks just before this one on observed AS paths…
16. **Prefix membership hierarchy** _(BGP, RPKI, physical)_ — Prefix membership hierarchy…

## Why each step runs

1. **BGP status.** Establishes the prefix's baseline BGP state: the headline of the health card the rest of the run fills in.
2. **MOAS conflicts.** Enumerates the CONFLICTS_WITH origins behind a MOAS, the concrete competing announcements that signal a hijack or misconfig.
3. **RIR allocation.** Names which registry allocated the block, the authority record against which legitimacy is checked.
4. **Origin history of the block.** Every network that has announced this block, a block covering it or a part of it, with when it was first and last seen and the most peers that saw it. A new origin in the last 30 days is flagged. The read has its own 30 s budget; a read that does not finish says so.
5. **RPKI ROA coverage.** Walks ROA_AUTHORIZES_ORIGIN/PREFIX to show what the network is RPKI-authorised to announce: the basis for valid-vs-invalid routing.
6. **ROAs authorizing the network.** How many RPKI ROAs name this network as the origin, counted over all of them.
7. **Announced prefixes.** The 50 prefixes a hijack could hit most easily (RPKI-invalid, contested, with no ROA, loose), then valid ones, each with its state.
8. **Facilities & IXes.** Maps physical presence via AS_PRESENT_AT and IX_MEMBER, the interconnection context behind the routing posture.
9. **ASN reputation.** Surfaces transit importance (AS-rank, customer cone) and the network’s tags: the reputation read that frames the whole health card.
10. **ASN identity & registration.** Names the network, its home country, the organization that holds the AS number, and how many prefixes it announces: the identity header of the routing card.
11. **Routing posture of every prefix.** Every prefix the ASN announces, counted by RPKI state (valid, no ROA, invalid), by a ROA that would validate a forged more-specific, and by a competing origin.
12. **Hijack and route-leak posture.** The network’s own routing record: the graph’s hijack posture score, origin mismatches and how many are unexplained, route leaks and their types, the bulletproof-hosting reputation score and the overall threat level, with the abuse contact. A blank figure means the graph holds no reading, not zero.
13. **Transit providers, customers and peers.** Every BGP neighbour of the network by what it is to it: a transit provider it buys from, a customer it sells to, a peer, or unclassified when the graph does not say. A network with one transit provider has a single point of failure upstream.
14. **Its transit providers.** The networks this one buys transit from, the best-ranked first, up to 25, with their AS rank and customer cone.
15. **Upstreams seen on observed AS paths.** The network that comes just before this one on the AS paths the graph has observed, counted, from a sample of 400 observed paths. These are observations, not routes: two vantage points are two paths, and the sample is the first 400 the graph returns.
16. **Prefix membership hierarchy.** Lists the sub-prefixes and individual IPs nested inside the prefix, so you can see exactly what address space lives under the block.

[Open the full use-case page, with the live runner](/products/intelligence/use-cases/network-routing/route-health)
