BGP and ASN Data
Explore announced prefixes for an ASN, split them by IPv4 and IPv6, and get a fast operational view of how large the routed footprint looks.
Pulls a usable list of announced prefixes for the ASN.
Separates families and shows how much of each is being announced.
Useful for peering reviews, troubleshooting, route hygiene, and infra research.
Examples
This tool queries announced prefix data and ASN whois-style details, then summarizes them for routing and planning workflows.
ASN prefix visibility is useful for peering, incident response, asset inventory, and understanding a network’s routed footprint.
This is a routing-data summary, not a live BGP control plane monitor. Propagation and policy can still vary by vantage point.
A clean ASN prefix explorer helps compare providers, validate expected announcements, and document address ownership quickly.
Announced-prefix data reflects what a network originates into routing, but it is still a summary view rather than a complete real-time BGP perspective.
This page groups prefixes by family, counts unique entries, and estimates address quantities from prefix length. It is most useful as a planning, documentation, and quick-research tool.
No. It shows announced origin prefixes associated with the ASN, not every transit path or routing policy outcome.
BGP data depends on collection point, timing, deduplication, and the upstream data source, so small differences are normal.
Yes. Many networks originate both families, and the split often reflects deployment maturity or service footprint.
Not always. Prefix granularity, traffic engineering, deaggregation, and address family mix all affect the count.