BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
138.50.0.0/16
Announced exactly
- 138.50.0.0/16AS721United States Department of Defense (DoD)RPKI Not found138.50.0.0
- Registry
- ARIN · United States · Feb 6, 1990
- Delegated block
- 138.50.0.0 – 138.50.255.255
Covering routes
No less-specific route covers it.
More-specific routes
- 138.50.0.0/23AS1540Headquarters, USAISCRPKI Not found138.50.0.0
- 138.50.2.0/23AS1540Headquarters, USAISCRPKI Not found138.50.2.0
- 138.50.4.0/23AS1540Headquarters, USAISCRPKI Not found138.50.4.0
- 138.50.6.0/23AS1540Headquarters, USAISCRPKI Not found138.50.6.0
- 138.50.8.0/23AS1540Headquarters, USAISCRPKI Not found138.50.8.0
- 138.50.10.0/23AS1540Headquarters, USAISCRPKI Not found138.50.10.0
- 138.50.14.0/24AS1540Headquarters, USAISCRPKI Not found138.50.14.0
- 138.50.15.0/24AS1540Headquarters, USAISCRPKI Not found138.50.15.0
- 138.50.17.0/24AS1540Headquarters, USAISCRPKI Not found138.50.17.0
- 138.50.18.0/24AS1540Headquarters, USAISCRPKI Not found138.50.18.0
- 138.50.19.0/24AS1540Headquarters, USAISCRPKI Not found138.50.19.0
- 138.50.40.0/23AS1540Headquarters, USAISCRPKI Not found138.50.40.0
- 138.50.42.0/23AS1540Headquarters, USAISCRPKI Not found138.50.42.0
- 138.50.44.0/23AS1540Headquarters, USAISCRPKI Not found138.50.44.0
- 138.50.46.0/23AS1540Headquarters, USAISCRPKI Not found138.50.46.0
- 138.50.48.0/23AS1540Headquarters, USAISCRPKI Not found138.50.48.0
- 138.50.50.0/23AS1540Headquarters, USAISCRPKI Not found138.50.50.0
- 138.50.52.0/24AS1540Headquarters, USAISCRPKI Not found138.50.52.0
- 138.50.53.0/24AS1540Headquarters, USAISCRPKI Not found138.50.53.0
- 138.50.64.0/24AS1540Headquarters, USAISCRPKI Not found138.50.64.0
- 138.50.65.0/24AS1540Headquarters, USAISCRPKI Not found138.50.65.0
- 138.50.66.0/24AS1540Headquarters, USAISCRPKI Not found138.50.66.0
- 138.50.67.0/24AS1540Headquarters, USAISCRPKI Not found138.50.67.0
- 138.50.68.0/23AS1540Headquarters, USAISCRPKI Not found138.50.68.0
- 138.50.70.0/23AS1540Headquarters, USAISCRPKI Not found138.50.70.0
- 138.50.72.0/24AS1540Headquarters, USAISCRPKI Not found138.50.72.0
- 138.50.73.0/24AS1540Headquarters, USAISCRPKI Not found138.50.73.0
- 138.50.74.0/24AS1540Headquarters, USAISCRPKI Not found138.50.74.0
- 138.50.75.0/24AS1540Headquarters, USAISCRPKI Not found138.50.75.0
- 138.50.96.0/24AS1540Headquarters, USAISCRPKI Not found138.50.96.0
- 138.50.97.0/24AS1540Headquarters, USAISCRPKI Not found138.50.97.0
- 138.50.98.0/24AS1540Headquarters, USAISCRPKI Not found138.50.98.0
- 138.50.104.0/23AS1540Headquarters, USAISCRPKI Not found138.50.104.0
- 138.50.106.0/23AS1540Headquarters, USAISCRPKI Not found138.50.106.0
- 138.50.108.0/23AS1540Headquarters, USAISCRPKI Not found138.50.108.0
- 138.50.110.0/24AS1540Headquarters, USAISCRPKI Not found138.50.110.0
- 138.50.111.0/24AS1540Headquarters, USAISCRPKI Not found138.50.111.0
- 138.50.112.0/24AS1540Headquarters, USAISCRPKI Not found138.50.112.0
- 138.50.128.0/17AS1565United States Department of Defense (DoD)RPKI Not found138.50.128.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.