BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
214.58.0.0/16
Announced exactly
- 214.58.0.0/16AS367United States Department of Defense (DoD)RPKI Not found214.58.0.0
- Registry
- ARIN · United States · Mar 27, 1998
- Delegated block
- 214.0.0.0 – 214.255.255.255
Covering routes
- 214.0.0.0/8AS721United States Department of Defense (DoD)RPKI Not found214.0.0.0
More-specific routes
- 214.58.8.0/23AS636United States Department of Defense (DoD)RPKI Not found214.58.8.0
- 214.58.22.0/24AS636United States Department of Defense (DoD)RPKI Not found214.58.22.0
- 214.58.23.0/24AS636United States Department of Defense (DoD)RPKI Not found214.58.23.0
- 214.58.24.0/23AS636United States Department of Defense (DoD)RPKI Not found214.58.24.0
- 214.58.28.0/22AS636United States Department of Defense (DoD)RPKI Not found214.58.28.0
- 214.58.32.0/21AS634United States Department of Defense (DoD)RPKI Not found214.58.32.0
- 214.58.40.0/23AS634United States Department of Defense (DoD)RPKI Not found214.58.40.0
- 214.58.45.0/24AS634United States Department of Defense (DoD)RPKI Not found214.58.45.0
- 214.58.46.0/23AS634United States Department of Defense (DoD)RPKI Not found214.58.46.0
- 214.58.48.0/23AS634United States Department of Defense (DoD)RPKI Not found214.58.48.0
- 214.58.51.0/24AS634United States Department of Defense (DoD)RPKI Not found214.58.51.0
- 214.58.64.0/20AS636United States Department of Defense (DoD)RPKI Not found214.58.64.0
- 214.58.80.0/22AS636United States Department of Defense (DoD)RPKI Not found214.58.80.0
- 214.58.85.0/24AS636United States Department of Defense (DoD)RPKI Not found214.58.85.0
- 214.58.86.0/23AS636United States Department of Defense (DoD)RPKI Not found214.58.86.0
- 214.58.88.0/24AS636United States Department of Defense (DoD)RPKI Not found214.58.88.0
- 214.58.92.0/22AS636United States Department of Defense (DoD)RPKI Not found214.58.92.0
- 214.58.107.0/24AS636United States Department of Defense (DoD)RPKI Not found214.58.107.0
- 214.58.108.0/24AS636United States Department of Defense (DoD)RPKI Not found214.58.108.0
- 214.58.125.0/24AS636United States Department of Defense (DoD)RPKI Not found214.58.125.0
- 214.58.160.0/23AS634United States Department of Defense (DoD)RPKI Not found214.58.160.0
- 214.58.162.0/23AS634United States Department of Defense (DoD)RPKI Not found214.58.162.0
- 214.58.164.0/24AS634United States Department of Defense (DoD)RPKI Not found214.58.164.0
- 214.58.165.0/24AS634United States Department of Defense (DoD)RPKI Not found214.58.165.0
- 214.58.168.0/23AS634United States Department of Defense (DoD)RPKI Not found214.58.168.0
- 214.58.244.0/24AS634United States Department of Defense (DoD)RPKI Not found214.58.244.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.