-
Notifications
You must be signed in to change notification settings - Fork 5
Tools Reference
Herve Hildenbrand edited this page Apr 8, 2026
·
4 revisions
BGP Explorer provides 8 composite tools that Claude uses to investigate routing questions. Each tool returns a summary by default and supports a sections parameter to expand specific areas.
| Tool | Purpose | Key Parameters |
|---|---|---|
search_asn |
Find ASNs by company name | query |
investigate_asn |
Everything about an ASN |
asn, sections, related_asn
|
investigate_prefix |
Everything about a prefix |
prefix, sections, vantage_point
|
check_rpki |
RPKI/ROA/ASPA analysis |
target (ASN or AS path), sections
|
get_routing_history_v2 |
Historical routing and stability |
resource, start_date, end_date, sections
|
investigate_ixp |
IXP presence or details |
target (ASN or IXP name) |
probe_network |
Ping/traceroute from global probes |
target, type, locations
|
run_audit |
DORA/NIS2/MANRS compliance |
asn, framework, output_format
|
Search for ASNs by organization or company name.
Parameters:
| Name | Type | Required | Description |
|---|---|---|---|
query |
string | Yes | Organization name (e.g., "Google", "Cloudflare") |
Features:
- Tries common company name variations automatically
- PeeringDB fallback when RIPE Stat returns no results
Comprehensive ASN investigation. The primary tool for ASN queries.
Parameters:
| Name | Type | Required | Description |
|---|---|---|---|
asn |
integer | Yes | Autonomous System Number |
sections |
list | No | Sections to include (default: ["summary"]) |
related_asn |
integer | No | Check relationship with another ASN |
Sections:
| Section | Description | Data Source |
|---|---|---|
summary |
Name, prefix counts (IPv4/IPv6), upstream/peer/downstream counts | RIPE Stat + Monocle |
connectivity |
Full upstream/peer/downstream lists with visibility % | Monocle |
announcements |
All announced prefixes | RIPE Stat |
contacts |
NOC/abuse/technical contacts | PeeringDB |
resilience |
Resilience score (1-10), transit diversity, IXP presence | Monocle + PeeringDB |
whois |
WHOIS/IRR registration data, route objects | RIPE Stat |
Examples:
investigate_asn(15169) # Summary only
investigate_asn(13335, sections=["connectivity", "resilience"]) # Expanded
investigate_asn(15169, related_asn=174) # Check relationship
Comprehensive prefix investigation. The primary tool for prefix queries.
Parameters:
| Name | Type | Required | Description |
|---|---|---|---|
prefix |
string | Yes | IP prefix in CIDR notation |
sections |
list | No | Sections to include (default: ["summary"]) |
vantage_point |
string | No | RRC collector for looking_glass section |
Sections:
| Section | Description | Data Source |
|---|---|---|
summary |
Origin ASN, visibility, RPKI status, anomaly flags | RIPE Stat |
routing |
Current BGP state with sample AS paths | RIPE Stat |
anomalies |
MOAS, RPKI invalid, low visibility, recent origin changes | RIPE Stat |
paths |
Path diversity, upstream/transit ASNs, prepending detection | RIPE Stat |
collectors |
Per-collector path comparison | RIPE Stat |
looking_glass |
Vantage-point view (uses vantage_point param) |
RIPE Stat LG |
RPKI/ROA/ASPA analysis. Auto-detects mode from target type.
Parameters:
| Name | Type | Required | Description |
|---|---|---|---|
target |
int or string | Yes | ASN (int) for coverage analysis, or AS path string for validation |
sections |
list | No | For ASN mode only (default: ["summary"]) |
ASN Mode (target is integer):
| Section | Description | Data Source |
|---|---|---|
summary |
ROA coverage %, ASPA published? | RIPE Stat + rpki-client |
roa_coverage |
Per-prefix RPKI validation status | RIPE Stat |
roa_guidance |
Missing ROAs, overly permissive maxLength | RIPE Stat + rpki-client |
aspa_status |
ASPA object details, authorized providers | rpki-client |
aspa_guidance |
Published vs inferred upstreams | rpki-client + Monocle |
rov_coverage |
ROV enforcer path coverage | RIPE Stat + ROV DB |
Path Mode (target is string like "3356 174 15169"): Validates the AS path against ASPA objects. Returns per-hop authorization status and valley-free check.
Historical routing data and stability analysis.
Parameters:
| Name | Type | Required | Description |
|---|---|---|---|
resource |
string | Yes | IP prefix or ASN |
start_date |
string | Yes | Start date (YYYY-MM-DD) |
end_date |
string | Yes | End date (YYYY-MM-DD) |
sections |
list | No | Sections to include (default: ["summary"]) |
Sections:
| Section | Description |
|---|---|
summary |
Origin count, stability score, flapping status |
origins |
Origin ASN changes over time |
paths |
AS path changes over time (BGPlay) |
stability |
Detailed stability report with flap detection |
updates |
Raw update activity time series |
IXP presence or details. Auto-detects mode from target type.
Parameters:
| Name | Type | Required | Description |
|---|---|---|---|
target |
int or string | Yes | ASN (int) for presence, or IXP name/ID (string) for details |
- ASN mode: Shows all IXPs where the ASN peers, with speeds and IPs
- IXP mode: Shows IXP details (location, participants) + member network list
Ping or traceroute from globally distributed probes.
Parameters:
| Name | Type | Required | Description |
|---|---|---|---|
target |
string | Yes | IP address or hostname |
type |
string | No |
"ping" (default) or "traceroute"
|
locations |
list | No | Country codes (US, DE), continent codes (EU, NA) |
DORA/NIS2/MANRS compliance audits.
Parameters:
| Name | Type | Required | Description |
|---|---|---|---|
asn |
integer | Yes | ASN to audit |
framework |
string | No |
"dora", "nis2", "manrs", or "all" (default) |
output_format |
string | No |
"text" (default) or "json"
|
The run_audit(framework='manrs') assesses 3 of the 4 MANRS Actions:
| Action | What we measure | What the operator must verify |
|---|---|---|
| Action 1: Filtering | Indirect proxy: ROA coverage + ROV enforcer paths | Enable ROV on all eBGP sessions, apply IRR prefix filters (bgpq4), set max-prefix limits |
| Action 2: Anti-Spoofing | Excluded from scoring — cannot be verified externally | Deploy uRPF/BCP38 on customer-facing interfaces, self-test via CAIDA Spoofer |
| Action 3: Coordination | PeeringDB NOC contacts + WHOIS abuse contact | Ensure contacts are monitored and responsive |
| Action 4: Validation | ROA coverage % + ASPA object published | Create missing ROAs at RIR portal, publish ASPA object |
Limitations:
- Action 1 is assessed via indirect proxy (ROA/ROV coverage) — we cannot verify your actual ingress filters
- Action 2 is excluded from scoring — external verification is impossible
- If
MANRS_API_KEYis set,run_audit(framework='manrs')also fetches official MANRS Observatory data
| Tool | Requires |
|---|---|
investigate_asn (connectivity, resilience sections) |
Monocle |
investigate_asn (contacts section) |
PeeringDB |
investigate_ixp |
PeeringDB |
probe_network |
Globalping |
check_rpki (aspa sections) |
rpki-client console |
run_audit (dora, nis2) |
Monocle + PeeringDB |
run_audit (manrs with Observatory) |
MANRS API key |
All other tools/sections require only RIPE Stat (always available).
- Data Sources - Learn about the underlying data sources
- Examples - See tools in action
- Architecture - Understand the system design