Inspect announced prefixes, upstreams, and route status.
Review recently changed routes and propagation delays.
A BGP prefix lookup helps you move from a public ASN or prefix to routing visibility, path context, and announcement clues. The existing form stays untouched, but the new content makes it clearer what kind of evidence the page provides and what it does not provide.
Enter an AS number if you want to review what a network is visibly announcing, or enter a specific prefix if you want to inspect its public routing context. View and range options narrow the perspective without changing the meaning of the underlying routing data.
The tool reads public routing information and summarizes prefixes, AS paths, and status indicators. Because BGP is observed through collectors, not from every router on the Internet, the result should be treated as a strong public visibility signal rather than absolute global truth.
Enter AS15169 to review the public prefixes associated with that autonomous system. The result table can show announced prefixes, visible AS paths, status, and when the route was observed. If you search for a prefix instead, the page focuses the same public routing context around that specific block.
Use BGP prefix lookup during propagation checks, route leak review, ownership verification, incident triage, and peering research. It is especially helpful when a prefix appears misrouted and you need to understand which network is visibly originating it.
Public routing data varies by collector coverage and update timing. A missing route can mean withdrawal, limited visibility, policy filtering, or collector delay. Treat the output as informational and confirm major decisions with additional routing sources.
It shows announced prefixes, AS path context, visibility signals, and status information for a public ASN or prefix when the data source provides it.
Yes. You can start with an AS number to review its public routes or with a specific IPv4 or IPv6 prefix to inspect its visible path information.
BGP visibility depends on route collectors, observation points, and update timing, so different sources can show slightly different perspectives of the same event.
No. Public BGP visibility is a strong routing signal, but it does not by itself prove end to end application reachability or data plane performance.
It is useful during propagation checks, hijack review, ownership validation, peering research, and route change investigations.
The output is informational and based on public routing views. Collector coverage, policy, and delay can affect what you see, especially during fast moving events.
Start with network identity and then move into prefix visibility.
Compare registry ownership with public routing observations.
Review whether announced space overlaps your internal planned ranges.