rir_prefix_overview
Fetch hierarchical IP prefix data including current holder, announcement status, parent blocks, and child assignments to analyze network ownership and routing.
Instructions
Fetch a rich hierarchical overview of an IP prefix.
IP address space is organized in a tree structure:
A /8 contains 256 /16s, each /16 contains 256 /24s, and so on.
'Less-specific' = the parent block this prefix was carved from.
'More-specific' = smaller blocks assigned within this prefix.
Think of it like a real estate map: Less-specific = the city block (containing your property) The prefix itself = your land parcel More-specific = subdivisions within your parcel
This tool fetches all three layers in parallel (3 RIPE Stat API calls simultaneously) and returns a unified view including:
Current holder and announcement status
Which ASN(s) are announcing it (multiple = potential hijack)
All less-specific (parent) prefixes up the tree
All more-specific (child) prefixes within the block
Combine with rir_check_rpki to validate the announcing ASN. Results are cached for 1 hour.
Args: params (PrefixOverviewInput): - prefix (str): IP prefix in CIDR notation (e.g. '1.1.1.0/24') - response_format (str): 'markdown' (default) or 'json'
Returns: str: Holder info, BGP status, and full prefix hierarchy table. JSON schema: { "prefix": str, "holder": str, "rir": str, "country": str, "announced": bool, "announcing_asns": [str], "allocation_status": str, "related_prefixes": [{"prefix": str, "relationship": str, "holder": str, "origin_asn": str}], "errors": [str] }
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| params | Yes |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |