Network & Routing
Detect MOAS hijacks, audit RPKI coverage, and profile an ASN — runnable workflows and Cypher recipes for routing teams.
Network & Routing Documentation
BGP tooling tells you a prefix has two origins; it doesn't tell you whether either origin is authorized, or whether the announcing network has a history. RPKI checkers validate routes in isolation, and reputation data lives somewhere else entirely. WhisperGraph keeps live announcements, BGP adjacency, MOAS conflicts, RPKI ROAs, and threat verdicts on the same graph, so one query returns a prefix's origin conflicts, its ROA coverage, and the standing of every network involved.
The graph also carries the physical layer behind the routing table: the facilities, internet exchanges, and submarine-cable landings a network sits in. An ASN profile can go from announced prefixes to BGP peers to actual buildings without leaving the query.
Run it
These guided workflows run in the browser against the live graph. Every step shows the Cypher it executes, and you can rerun each on your own prefix or ASN. Anonymous runs are capped at 2 traversal hops; a free API key raises that to 3.
| Workflow | What it does |
|---|---|
| Route-Health Checker | A prefix or ASN in, a BGP/RPKI health card out: MOAS conflicts, ROA coverage, announcement status, footprint. |
| Enrich an ASN | One ASN in: its announced prefixes, RPKI ROA coverage, BGP peers, and the facilities and exchanges where it is present. |
| Trace a BGP hijack to its exposed domains | From an ASN or prefix, find route-origin conflicts and RPKI gaps, then the hostnames and orgs exposed on those prefixes. |
| Audit an ASN's routing hygiene | Grade an ASN on multi-origin conflicts and RPKI ROA coverage across its announced prefixes. |
| Map upstream-transit dependency | Origin ASNs, how many BGP upstreams each has, single-homed networks, and the common-mode transit carriers an org funnels through. |
| RPKI ROA expiry watch | The ROAs that authorize a network's routes, flagging the ones expiring soon and the over-permissive maxLength entries. |
| Cluster Tor exit exposure | Every IP an ASN routes that operates a Tor exit node, clustered by prefix, announced prefix, and country. |
Recipes
BGP & RPKI collects the copy-paste queries behind these workflows: MOAS detection, RPKI authorization checks, peering triage, origin history, and physical footprint. The reusable pivots that cross into other layers (hostname to IP to prefix to ASN and back) live in Cross-Layer Patterns, and the routing labels, edges, and prefix flags are documented in the Graph Schema.