BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
138.164.0.0/14
Announced exactly
- 138.164.0.0/14AS721United States Department of Defense (DoD)RPKI Not found138.164.0.0
- Registry
- ARIN · United States · May 7, 1990
- Delegated block
- 138.164.0.0 – 138.164.255.255
Covering routes
No less-specific route covers it.
More-specific routes
- 138.167.0.0/20AS637United States Department of Defense (DoD)RPKI Not found138.167.0.0
- 138.167.20.0/23AS637United States Department of Defense (DoD)RPKI Not found138.167.20.0
- 138.167.32.0/21AS637United States Department of Defense (DoD)RPKI Not found138.167.32.0
- 138.167.40.0/22AS637United States Department of Defense (DoD)RPKI Not found138.167.40.0
- 138.167.44.0/22AS637United States Department of Defense (DoD)RPKI Not found138.167.44.0
- 138.167.48.0/20AS637United States Department of Defense (DoD)RPKI Not found138.167.48.0
- 138.167.64.0/24AS637United States Department of Defense (DoD)RPKI Not found138.167.64.0
- 138.167.65.0/24AS637United States Department of Defense (DoD)RPKI Not found138.167.65.0
- 138.167.66.0/24AS637United States Department of Defense (DoD)RPKI Not found138.167.66.0
- 138.167.67.0/24AS637United States Department of Defense (DoD)RPKI Not found138.167.67.0
- 138.167.68.0/24AS637United States Department of Defense (DoD)RPKI Not found138.167.68.0
- 138.167.69.0/24AS637United States Department of Defense (DoD)RPKI Not found138.167.69.0
- 138.167.70.0/24AS637United States Department of Defense (DoD)RPKI Not found138.167.70.0
- 138.167.71.0/24AS637United States Department of Defense (DoD)RPKI Not found138.167.71.0
- 138.167.72.0/24AS637United States Department of Defense (DoD)RPKI Not found138.167.72.0
- 138.167.73.0/24AS637United States Department of Defense (DoD)RPKI Not found138.167.73.0
- 138.167.74.0/24AS637United States Department of Defense (DoD)RPKI Not found138.167.74.0
- 138.167.75.0/24AS637United States Department of Defense (DoD)RPKI Not found138.167.75.0
- 138.167.76.0/24AS637United States Department of Defense (DoD)RPKI Not found138.167.76.0
- 138.167.77.0/24AS637United States Department of Defense (DoD)RPKI Not found138.167.77.0
- 138.167.78.0/24AS637United States Department of Defense (DoD)RPKI Not found138.167.78.0
- 138.167.79.0/24AS637United States Department of Defense (DoD)RPKI Not found138.167.79.0
- 138.167.80.0/24AS637United States Department of Defense (DoD)RPKI Not found138.167.80.0
- 138.167.81.0/24AS637United States Department of Defense (DoD)RPKI Not found138.167.81.0
- 138.167.82.0/24AS637United States Department of Defense (DoD)RPKI Not found138.167.82.0
- 138.167.83.0/24AS637United States Department of Defense (DoD)RPKI Not found138.167.83.0
- 138.167.84.0/24AS637United States Department of Defense (DoD)RPKI Not found138.167.84.0
- 138.167.85.0/24AS637United States Department of Defense (DoD)RPKI Not found138.167.85.0
- 138.167.104.0/22AS637United States Department of Defense (DoD)RPKI Not found138.167.104.0
- 138.167.108.0/22AS637United States Department of Defense (DoD)RPKI Not found138.167.108.0
- 138.167.112.0/23AS637United States Department of Defense (DoD)RPKI Not found138.167.112.0
- 138.167.119.0/24AS637United States Department of Defense (DoD)RPKI Not found138.167.119.0
- 138.167.120.0/21AS637United States Department of Defense (DoD)RPKI Not found138.167.120.0
- 138.167.128.0/23AS637United States Department of Defense (DoD)RPKI Not found138.167.128.0
- 138.167.130.0/23AS637United States Department of Defense (DoD)RPKI Not found138.167.130.0
- 138.167.132.0/23AS637United States Department of Defense (DoD)RPKI Not found138.167.132.0
- 138.167.134.0/23AS637United States Department of Defense (DoD)RPKI Not found138.167.134.0
- 138.167.136.0/23AS637United States Department of Defense (DoD)RPKI Not found138.167.136.0
- 138.167.138.0/23AS637United States Department of Defense (DoD)RPKI Not found138.167.138.0
- 138.167.140.0/22AS637United States Department of Defense (DoD)RPKI Not found138.167.140.0
- 138.167.144.0/20AS637United States Department of Defense (DoD)RPKI Not found138.167.144.0
- 138.167.160.0/21AS637United States Department of Defense (DoD)RPKI Not found138.167.160.0
- 138.167.176.0/20AS637United States Department of Defense (DoD)RPKI Not found138.167.176.0
- 138.167.200.0/22AS637United States Department of Defense (DoD)RPKI Not found138.167.200.0
- 138.167.206.0/24AS637United States Department of Defense (DoD)RPKI Not found138.167.206.0
- 138.167.208.0/20AS637United States Department of Defense (DoD)RPKI Not found138.167.208.0
- 138.167.224.0/21AS637United States Department of Defense (DoD)RPKI Not found138.167.224.0
- 138.167.232.0/24AS637United States Department of Defense (DoD)RPKI Not found138.167.232.0
- 138.167.235.0/24AS637United States Department of Defense (DoD)RPKI Not found138.167.235.0
- 138.167.236.0/22AS637United States Department of Defense (DoD)RPKI Not found138.167.236.0
- 138.167.248.0/22AS637United States Department of Defense (DoD)RPKI Not found138.167.248.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.