BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
158.8.0.0/14
Announced exactly
- 158.8.0.0/14AS721United States Department of Defense (DoD)RPKI Not found158.8.0.0
- Registry
- ARIN · United States · Jan 13, 1993
- Delegated block
- 158.8.0.0 – 158.8.255.255
Covering routes
No less-specific route covers it.
More-specific routes
- 158.8.0.0/16AS5180United States Department of Defense (DoD)RPKI Not found158.8.0.0
- 158.9.16.0/24AS153Headquarters, USAISCRPKI Not found158.9.16.0
- 158.9.49.0/24AS1540Headquarters, USAISCRPKI Not found158.9.49.0
- 158.9.52.0/22AS129United States Department of Defense (DoD)RPKI Not found158.9.52.0
- 158.9.64.0/23AS27064United States Department of Defense (DoD)RPKI Not found158.9.64.0
- 158.9.66.0/23AS27064United States Department of Defense (DoD)RPKI Not found158.9.66.0
- 158.9.72.0/23AS27064United States Department of Defense (DoD)RPKI Not found158.9.72.0
- 158.9.74.0/23AS27064United States Department of Defense (DoD)RPKI Not found158.9.74.0
- 158.9.80.0/23AS27064United States Department of Defense (DoD)RPKI Not found158.9.80.0
- 158.9.82.0/23AS27064United States Department of Defense (DoD)RPKI Not found158.9.82.0
- 158.9.84.0/23AS27064United States Department of Defense (DoD)RPKI Not found158.9.84.0
- 158.9.86.0/23AS27064United States Department of Defense (DoD)RPKI Not found158.9.86.0
- 158.9.94.0/24AS1540Headquarters, USAISCRPKI Not found158.9.94.0
- 158.9.99.0/24AS27064United States Department of Defense (DoD)RPKI Not found158.9.99.0
- 158.9.100.0/23AS367United States Department of Defense (DoD)RPKI Not found158.9.100.0
- 158.9.102.0/24AS1540Headquarters, USAISCRPKI Not found158.9.102.0
- 158.9.104.0/24AS1540Headquarters, USAISCRPKI Not found158.9.104.0
- 158.9.106.0/23AS1540Headquarters, USAISCRPKI Not found158.9.106.0
- 158.9.127.0/24AS1540Headquarters, USAISCRPKI Not found158.9.127.0
- 158.9.128.0/24AS1540Headquarters, USAISCRPKI Not found158.9.128.0
- 158.9.129.0/24AS1540Headquarters, USAISCRPKI Not found158.9.129.0
- 158.9.132.0/24AS1540Headquarters, USAISCRPKI Not found158.9.132.0
- 158.9.133.0/24AS1540Headquarters, USAISCRPKI Not found158.9.133.0
- 158.9.136.0/23AS1540Headquarters, USAISCRPKI Not found158.9.136.0
- 158.9.138.0/24AS1540Headquarters, USAISCRPKI Not found158.9.138.0
- 158.9.139.0/24AS1540Headquarters, USAISCRPKI Not found158.9.139.0
- 158.9.142.0/24AS27064United States Department of Defense (DoD)RPKI Not found158.9.142.0
- 158.9.148.0/24AS1540Headquarters, USAISCRPKI Not found158.9.148.0
- 158.9.149.0/24AS27064United States Department of Defense (DoD)RPKI Not found158.9.149.0
- 158.9.152.0/24AS1540Headquarters, USAISCRPKI Not found158.9.152.0
- 158.9.153.0/24AS27064United States Department of Defense (DoD)RPKI Not found158.9.153.0
- 158.9.160.0/24AS1540Headquarters, USAISCRPKI Not found158.9.160.0
- 158.9.161.0/24AS1540Headquarters, USAISCRPKI Not found158.9.161.0
- 158.9.168.0/24AS1540Headquarters, USAISCRPKI Not found158.9.168.0
- 158.9.178.0/24AS1540Headquarters, USAISCRPKI Not found158.9.178.0
- 158.9.199.0/24AS1540Headquarters, USAISCRPKI Not found158.9.199.0
- 158.9.200.0/24AS1540Headquarters, USAISCRPKI Not found158.9.200.0
- 158.9.201.0/24AS1540Headquarters, USAISCRPKI Not found158.9.201.0
- 158.9.208.0/24AS1540Headquarters, USAISCRPKI Not found158.9.208.0
- 158.9.209.0/24AS1540Headquarters, USAISCRPKI Not found158.9.209.0
- 158.9.216.0/23AS1540Headquarters, USAISCRPKI Not found158.9.216.0
- 158.9.225.0/24AS1540Headquarters, USAISCRPKI Not found158.9.225.0
- 158.9.246.0/24AS1540Headquarters, USAISCRPKI Not found158.9.246.0
- 158.9.247.0/24AS367United States Department of Defense (DoD)RPKI Not found158.9.247.0
- 158.9.253.0/24AS1540Headquarters, USAISCRPKI Not found158.9.253.0
- 158.9.254.0/23AS1540Headquarters, USAISCRPKI Not found158.9.254.0
- 158.11.0.0/22AS1540Headquarters, USAISCRPKI Not found158.11.0.0
- 158.11.8.0/22AS1540Headquarters, USAISCRPKI Not found158.11.8.0
- 158.11.16.0/24AS1501Headquarters, USAISCRPKI Not found158.11.16.0
- 158.11.17.0/24AS1501Headquarters, USAISCRPKI Not found158.11.17.0
- 158.11.18.0/24AS1501Headquarters, USAISCRPKI Not found158.11.18.0
- 158.11.19.0/24AS1501Headquarters, USAISCRPKI Not found158.11.19.0
- 158.11.25.0/24AS1501Headquarters, USAISCRPKI Not found158.11.25.0
- 158.11.26.0/24AS1501Headquarters, USAISCRPKI Not found158.11.26.0
- 158.11.27.0/24AS1501Headquarters, USAISCRPKI Not found158.11.27.0
- 158.11.32.0/23AS1540Headquarters, USAISCRPKI Not found158.11.32.0
- 158.11.34.0/24AS1540Headquarters, USAISCRPKI Not found158.11.34.0
- 158.11.40.0/22AS1540Headquarters, USAISCRPKI Not found158.11.40.0
- 158.11.40.0/23AS1540Headquarters, USAISCRPKI Not found158.11.40.0
- 158.11.42.0/23AS1540Headquarters, USAISCRPKI Not found158.11.42.0
- 158.11.44.0/24AS1540Headquarters, USAISCRPKI Not found158.11.44.0
- 158.11.50.0/23AS1540Headquarters, USAISCRPKI Not found158.11.50.0
- 158.11.62.0/23AS1540Headquarters, USAISCRPKI Not found158.11.62.0
- 158.11.63.0/24AS1540Headquarters, USAISCRPKI Not found158.11.63.0
- 158.11.64.0/23AS1540Headquarters, USAISCRPKI Not found158.11.64.0
- 158.11.76.0/23AS1540Headquarters, USAISCRPKI Not found158.11.76.0
- 158.11.160.0/24AS1501Headquarters, USAISCRPKI Not found158.11.160.0
- 158.11.168.0/24AS1501Headquarters, USAISCRPKI Not found158.11.168.0
- 158.11.195.0/24AS1540Headquarters, USAISCRPKI Not found158.11.195.0
- 158.11.197.0/24AS1501Headquarters, USAISCRPKI Not found158.11.197.0
- 158.11.208.0/23AS1501Headquarters, USAISCRPKI Not found158.11.208.0
- 158.11.227.0/24AS1540Headquarters, USAISCRPKI Not found158.11.227.0
- 158.11.228.0/23AS1540Headquarters, USAISCRPKI Not found158.11.228.0
- 158.11.228.0/24AS1540Headquarters, USAISCRPKI Not found158.11.228.0
- 158.11.231.0/24AS1540Headquarters, USAISCRPKI Not found158.11.231.0
- 158.11.233.0/24AS1540Headquarters, USAISCRPKI Not found158.11.233.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.