BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
132.80.0.0/12
Announced exactly
- 132.80.0.0/12AS721United States Department of Defense (DoD)RPKI Not found132.80.0.0
- Registry
- ARIN · United States · Mar 5, 1990
- Delegated block
- 132.80.0.0 – 132.83.255.255
Covering routes
No less-specific route covers it.
More-specific routes
- 132.80.0.0/16AS306United States Department of Defense (DoD)RPKI Not found132.80.0.0
- 132.81.0.0/16AS306United States Department of Defense (DoD)RPKI Not found132.81.0.0
- 132.81.198.0/24AS306United States Department of Defense (DoD)RPKI Not found132.81.198.0
- 132.81.242.0/24AS306United States Department of Defense (DoD)RPKI Not found132.81.242.0
- 132.81.253.0/24AS306United States Department of Defense (DoD)RPKI Not found132.81.253.0
- 132.82.0.0/16AS306United States Department of Defense (DoD)RPKI Not found132.82.0.0
- 132.82.198.0/24AS306United States Department of Defense (DoD)RPKI Not found132.82.198.0
- 132.82.253.0/24AS306United States Department of Defense (DoD)RPKI Not found132.82.253.0
- 132.83.0.0/16AS306United States Department of Defense (DoD)RPKI Not found132.83.0.0
- 132.83.48.0/21AS306United States Department of Defense (DoD)RPKI Not found132.83.48.0
- 132.83.122.0/24AS306United States Department of Defense (DoD)RPKI Not found132.83.122.0
- 132.83.127.0/24AS306United States Department of Defense (DoD)RPKI Not found132.83.127.0
- 132.83.253.0/24AS306United States Department of Defense (DoD)RPKI Not found132.83.253.0
- 132.83.254.0/24AS306United States Department of Defense (DoD)RPKI Not found132.83.254.0
- 132.84.0.0/16AS306United States Department of Defense (DoD)RPKI Not found132.84.0.0
- 132.84.12.0/24AS306United States Department of Defense (DoD)RPKI Not found132.84.12.0
- 132.84.198.0/24AS306United States Department of Defense (DoD)RPKI Not found132.84.198.0
- 132.84.200.0/24AS306United States Department of Defense (DoD)RPKI Not found132.84.200.0
- 132.84.253.0/24AS306United States Department of Defense (DoD)RPKI Not found132.84.253.0
- 132.85.0.0/16AS306United States Department of Defense (DoD)RPKI Not found132.85.0.0
- 132.85.198.0/24AS306United States Department of Defense (DoD)RPKI Not found132.85.198.0
- 132.85.253.0/24AS306United States Department of Defense (DoD)RPKI Not found132.85.253.0
- 132.86.0.0/16AS306United States Department of Defense (DoD)RPKI Not found132.86.0.0
- 132.86.253.0/24AS306United States Department of Defense (DoD)RPKI Not found132.86.253.0
- 132.87.0.0/16AS306United States Department of Defense (DoD)RPKI Not found132.87.0.0
- 132.87.198.0/24AS306United States Department of Defense (DoD)RPKI Not found132.87.198.0
- 132.87.253.0/24AS306United States Department of Defense (DoD)RPKI Not found132.87.253.0
- 132.88.0.0/16AS306United States Department of Defense (DoD)RPKI Not found132.88.0.0
- 132.89.0.0/16AS306United States Department of Defense (DoD)RPKI Not found132.89.0.0
- 132.89.253.0/24AS306United States Department of Defense (DoD)RPKI Not found132.89.253.0
- 132.90.0.0/16AS306United States Department of Defense (DoD)RPKI Not found132.90.0.0
- 132.90.40.0/21AS306United States Department of Defense (DoD)RPKI Not found132.90.40.0
- 132.90.48.0/21AS306United States Department of Defense (DoD)RPKI Not found132.90.48.0
- 132.90.253.0/24AS306United States Department of Defense (DoD)RPKI Not found132.90.253.0
- 132.91.0.0/16AS306United States Department of Defense (DoD)RPKI Not found132.91.0.0
- 132.92.0.0/16AS306United States Department of Defense (DoD)RPKI Not found132.92.0.0
- 132.92.40.0/21AS306United States Department of Defense (DoD)RPKI Not found132.92.40.0
- 132.92.253.0/24AS306United States Department of Defense (DoD)RPKI Not found132.92.253.0
- 132.93.0.0/16AS306United States Department of Defense (DoD)RPKI Not found132.93.0.0
- 132.93.40.0/21AS306United States Department of Defense (DoD)RPKI Not found132.93.40.0
- 132.93.253.0/24AS306United States Department of Defense (DoD)RPKI Not found132.93.253.0
- 132.94.0.0/16AS306United States Department of Defense (DoD)RPKI Not found132.94.0.0
- 132.94.40.0/21AS306United States Department of Defense (DoD)RPKI Not found132.94.40.0
- 132.94.48.0/21AS306United States Department of Defense (DoD)RPKI Not found132.94.48.0
- 132.94.242.0/24AS306United States Department of Defense (DoD)RPKI Not found132.94.242.0
- 132.94.253.0/24AS306United States Department of Defense (DoD)RPKI Not found132.94.253.0
- 132.95.0.0/16AS306United States Department of Defense (DoD)RPKI Not found132.95.0.0
- 132.95.40.0/21AS306United States Department of Defense (DoD)RPKI Not found132.95.40.0
- 132.95.48.0/21AS306United States Department of Defense (DoD)RPKI Not found132.95.48.0
- 132.95.253.0/24AS306United States Department of Defense (DoD)RPKI Not found132.95.253.0
On the internet, routes are announced as prefixes: an autonomous system tells its neighbours via BGP that it can deliver traffic for, say, 49.224.0.0/14. This tool looks a prefix up in our daily copy of the global routing table and shows three things:
- Exact announcements: which AS originates exactly this prefix. More than one origin (a MOAS) is normal for anycast services and some multihomed networks, and suspicious otherwise.
- Covering routes: less-specific announcements that contain it. Traffic follows the most specific route, so a covering route matters if the more-specific one disappears.
- More-specifics: announcements inside it, which may belong to other networks (customers, or a hijack).
Each announced route is also checked against the RPKI: whether a ROA authorises its origin AS.
The table is the view from APNIC’s route collector. Most of the global table is the same from everywhere, but a route that is filtered before it reaches that collector will not appear.
Frequently asked questions
Why is my /24 not listed but a /16 is?
Your addresses are announced as part of the larger block, and no one announces the /24 separately. That is the normal case for most customers of a provider.
What is a more-specific hijack?
Someone announces a longer prefix inside your space. Because routers prefer the most specific route, traffic goes to them. RPKI with a strict max length makes such announcements invalid.
Can I enter a single address?
Yes. The tool then shows the most specific announced route that contains it.