BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
158.14.0.0/15
Announced exactly
- 158.14.0.0/15AS721United States Department of Defense (DoD)RPKI Not found158.14.0.0
- Registry
- ARIN · United States · Jan 12, 1993
- Delegated block
- 158.14.0.0 – 158.14.255.255
Covering routes
No less-specific route covers it.
More-specific routes
- 158.14.62.0/24AS367United States Department of Defense (DoD)RPKI Not found158.14.62.0
- 158.14.75.0/24AS1540Headquarters, USAISCRPKI Not found158.14.75.0
- 158.14.76.0/24AS1540Headquarters, USAISCRPKI Not found158.14.76.0
- 158.14.77.0/24AS1540Headquarters, USAISCRPKI Not found158.14.77.0
- 158.14.78.0/24AS1540Headquarters, USAISCRPKI Not found158.14.78.0
- 158.14.79.0/24AS1540Headquarters, USAISCRPKI Not found158.14.79.0
- 158.14.80.0/24AS1540Headquarters, USAISCRPKI Not found158.14.80.0
- 158.14.81.0/24AS1540Headquarters, USAISCRPKI Not found158.14.81.0
- 158.14.82.0/24AS1540Headquarters, USAISCRPKI Not found158.14.82.0
- 158.14.83.0/24AS1540Headquarters, USAISCRPKI Not found158.14.83.0
- 158.14.84.0/24AS1540Headquarters, USAISCRPKI Not found158.14.84.0
- 158.14.85.0/24AS1540Headquarters, USAISCRPKI Not found158.14.85.0
- 158.14.86.0/24AS1540Headquarters, USAISCRPKI Not found158.14.86.0
- 158.14.87.0/24AS1540Headquarters, USAISCRPKI Not found158.14.87.0
- 158.14.88.0/24AS1540Headquarters, USAISCRPKI Not found158.14.88.0
- 158.14.89.0/24AS1540Headquarters, USAISCRPKI Not found158.14.89.0
- 158.14.108.0/23AS1540Headquarters, USAISCRPKI Not found158.14.108.0
- 158.14.110.0/23AS1540Headquarters, USAISCRPKI Not found158.14.110.0
- 158.14.112.0/23AS1540Headquarters, USAISCRPKI Not found158.14.112.0
- 158.14.114.0/23AS1540Headquarters, USAISCRPKI Not found158.14.114.0
- 158.14.116.0/23AS1540Headquarters, USAISCRPKI Not found158.14.116.0
- 158.14.118.0/23AS1540Headquarters, USAISCRPKI Not found158.14.118.0
- 158.14.120.0/23AS1540Headquarters, USAISCRPKI Not found158.14.120.0
- 158.14.122.0/23AS1540Headquarters, USAISCRPKI Not found158.14.122.0
- 158.14.124.0/23AS1540Headquarters, USAISCRPKI Not found158.14.124.0
- 158.14.126.0/23AS1540Headquarters, USAISCRPKI Not found158.14.126.0
- 158.14.128.0/23AS1540Headquarters, USAISCRPKI Not found158.14.128.0
- 158.14.130.0/23AS1540Headquarters, USAISCRPKI Not found158.14.130.0
- 158.14.132.0/23AS1540Headquarters, USAISCRPKI Not found158.14.132.0
- 158.14.134.0/23AS1540Headquarters, USAISCRPKI Not found158.14.134.0
- 158.14.136.0/23AS1540Headquarters, USAISCRPKI Not found158.14.136.0
- 158.14.138.0/23AS1540Headquarters, USAISCRPKI Not found158.14.138.0
- 158.14.140.0/23AS1540Headquarters, USAISCRPKI Not found158.14.140.0
- 158.14.142.0/23AS1540Headquarters, USAISCRPKI Not found158.14.142.0
- 158.14.144.0/23AS1540Headquarters, USAISCRPKI Not found158.14.144.0
- 158.14.146.0/23AS1540Headquarters, USAISCRPKI Not found158.14.146.0
- 158.14.148.0/23AS1540Headquarters, USAISCRPKI Not found158.14.148.0
- 158.14.150.0/23AS1540Headquarters, USAISCRPKI Not found158.14.150.0
- 158.14.152.0/23AS1540Headquarters, USAISCRPKI Not found158.14.152.0
- 158.14.154.0/23AS1540Headquarters, USAISCRPKI Not found158.14.154.0
- 158.14.156.0/23AS1540Headquarters, USAISCRPKI Not found158.14.156.0
- 158.14.158.0/23AS1540Headquarters, USAISCRPKI Not found158.14.158.0
- 158.14.160.0/23AS1540Headquarters, USAISCRPKI Not found158.14.160.0
- 158.14.162.0/23AS1540Headquarters, USAISCRPKI Not found158.14.162.0
- 158.14.164.0/23AS1540Headquarters, USAISCRPKI Not found158.14.164.0
- 158.14.166.0/23AS1540Headquarters, USAISCRPKI Not found158.14.166.0
- 158.14.168.0/23AS1540Headquarters, USAISCRPKI Not found158.14.168.0
- 158.14.170.0/23AS1540Headquarters, USAISCRPKI Not found158.14.170.0
- 158.14.172.0/23AS1540Headquarters, USAISCRPKI Not found158.14.172.0
- 158.14.174.0/23AS1540Headquarters, USAISCRPKI Not found158.14.174.0
- 158.14.176.0/23AS1540Headquarters, USAISCRPKI Not found158.14.176.0
- 158.14.178.0/23AS1540Headquarters, USAISCRPKI Not found158.14.178.0
- 158.14.180.0/23AS1540Headquarters, USAISCRPKI Not found158.14.180.0
- 158.14.182.0/23AS1540Headquarters, USAISCRPKI Not found158.14.182.0
- 158.14.184.0/23AS1540Headquarters, USAISCRPKI Not found158.14.184.0
- 158.14.186.0/23AS1540Headquarters, USAISCRPKI Not found158.14.186.0
- 158.14.206.0/23AS1540Headquarters, USAISCRPKI Not found158.14.206.0
- 158.14.208.0/23AS1540Headquarters, USAISCRPKI Not found158.14.208.0
- 158.14.210.0/23AS1540Headquarters, USAISCRPKI Not found158.14.210.0
- 158.14.212.0/23AS1540Headquarters, USAISCRPKI Not found158.14.212.0
- 158.14.214.0/23AS1540Headquarters, USAISCRPKI Not found158.14.214.0
- 158.14.216.0/23AS1540Headquarters, USAISCRPKI Not found158.14.216.0
- 158.14.218.0/23AS1540Headquarters, USAISCRPKI Not found158.14.218.0
- 158.14.220.0/23AS1540Headquarters, USAISCRPKI Not found158.14.220.0
- 158.14.222.0/23AS1540Headquarters, USAISCRPKI Not found158.14.222.0
- 158.14.224.0/23AS1540Headquarters, USAISCRPKI Not found158.14.224.0
- 158.14.226.0/23AS1540Headquarters, USAISCRPKI Not found158.14.226.0
- 158.14.228.0/23AS1540Headquarters, USAISCRPKI Not found158.14.228.0
- 158.14.230.0/23AS1540Headquarters, USAISCRPKI Not found158.14.230.0
- 158.14.232.0/23AS1540Headquarters, USAISCRPKI Not found158.14.232.0
- 158.14.234.0/23AS1540Headquarters, USAISCRPKI Not found158.14.234.0
- 158.14.236.0/23AS1540Headquarters, USAISCRPKI Not found158.14.236.0
- 158.14.238.0/23AS1540Headquarters, USAISCRPKI Not found158.14.238.0
- 158.14.240.0/23AS1540Headquarters, USAISCRPKI Not found158.14.240.0
- 158.14.242.0/23AS1540Headquarters, USAISCRPKI Not found158.14.242.0
- 158.14.244.0/23AS1540Headquarters, USAISCRPKI Not found158.14.244.0
- 158.15.0.0/16AS300United States Department of Defense (DoD)RPKI Not found158.15.0.0
- 158.15.226.0/24AS300United States Department of Defense (DoD)RPKI Not found158.15.226.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.