BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
143.73.0.0/16
Announced exactly
- 143.73.0.0/16AS721United States Department of Defense (DoD)RPKI Not found143.73.0.0
- Registry
- ARIN · United States · Mar 26, 1990
- Delegated block
- 143.73.0.0 – 143.73.255.255
Covering routes
No less-specific route covers it.
More-specific routes
- 143.73.0.0/22AS1540Headquarters, USAISCRPKI Not found143.73.0.0
- 143.73.21.0/24AS1540Headquarters, USAISCRPKI Not found143.73.21.0
- 143.73.28.0/24AS1501Headquarters, USAISCRPKI Not found143.73.28.0
- 143.73.29.0/24AS1501Headquarters, USAISCRPKI Not found143.73.29.0
- 143.73.30.0/23AS1540Headquarters, USAISCRPKI Not found143.73.30.0
- 143.73.30.0/24AS1540Headquarters, USAISCRPKI Not found143.73.30.0
- 143.73.31.0/24AS1540Headquarters, USAISCRPKI Not found143.73.31.0
- 143.73.35.0/24AS1501Headquarters, USAISCRPKI Not found143.73.35.0
- 143.73.37.0/24AS1540Headquarters, USAISCRPKI Not found143.73.37.0
- 143.73.38.0/24AS1501Headquarters, USAISCRPKI Not found143.73.38.0
- 143.73.49.0/24AS1501Headquarters, USAISCRPKI Not found143.73.49.0
- 143.73.50.0/24AS1501Headquarters, USAISCRPKI Not found143.73.50.0
- 143.73.51.0/24AS1501Headquarters, USAISCRPKI Not found143.73.51.0
- 143.73.53.0/24AS1501Headquarters, USAISCRPKI Not found143.73.53.0
- 143.73.55.0/24AS1501Headquarters, USAISCRPKI Not found143.73.55.0
- 143.73.56.0/24AS1501Headquarters, USAISCRPKI Not found143.73.56.0
- 143.73.57.0/24AS1501Headquarters, USAISCRPKI Not found143.73.57.0
- 143.73.58.0/24AS1501Headquarters, USAISCRPKI Not found143.73.58.0
- 143.73.62.0/24AS1501Headquarters, USAISCRPKI Not found143.73.62.0
- 143.73.63.0/24AS1501Headquarters, USAISCRPKI Not found143.73.63.0
- 143.73.64.0/24AS1501Headquarters, USAISCRPKI Not found143.73.64.0
- 143.73.65.0/24AS1501Headquarters, USAISCRPKI Not found143.73.65.0
- 143.73.69.0/24AS1501Headquarters, USAISCRPKI Not found143.73.69.0
- 143.73.70.0/24AS1501Headquarters, USAISCRPKI Not found143.73.70.0
- 143.73.71.0/24AS1501Headquarters, USAISCRPKI Not found143.73.71.0
- 143.73.72.0/24AS1501Headquarters, USAISCRPKI Not found143.73.72.0
- 143.73.76.0/24AS1501Headquarters, USAISCRPKI Not found143.73.76.0
- 143.73.78.0/24AS1501Headquarters, USAISCRPKI Not found143.73.78.0
- 143.73.79.0/24AS1501Headquarters, USAISCRPKI Not found143.73.79.0
- 143.73.84.0/24AS1501Headquarters, USAISCRPKI Not found143.73.84.0
- 143.73.85.0/24AS1501Headquarters, USAISCRPKI Not found143.73.85.0
- 143.73.86.0/24AS1501Headquarters, USAISCRPKI Not found143.73.86.0
- 143.73.90.0/24AS1501Headquarters, USAISCRPKI Not found143.73.90.0
- 143.73.92.0/24AS1501Headquarters, USAISCRPKI Not found143.73.92.0
- 143.73.93.0/24AS1501Headquarters, USAISCRPKI Not found143.73.93.0
- 143.73.95.0/24AS1501Headquarters, USAISCRPKI Not found143.73.95.0
- 143.73.126.0/24AS1540Headquarters, USAISCRPKI Not found143.73.126.0
- 143.73.173.0/24AS747Headquarters, USAISCRPKI Not found143.73.173.0
On the internet, routes are announced as prefixes: an autonomous system tells its neighbours via BGP that it can deliver traffic for, say, 85.240.0.0/13. 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.