BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
134.235.0.0/16
Announced exactly
- 134.235.0.0/16AS721United States Department of Defense (DoD)RPKI Not found134.235.0.0
- Registry
- ARIN · United States · Aug 7, 1989
- Delegated block
- 134.235.0.0 – 134.235.255.255
Covering routes
No less-specific route covers it.
More-specific routes
- 134.235.17.0/24AS1540Headquarters, USAISCRPKI Not found134.235.17.0
- 134.235.18.0/24AS1540Headquarters, USAISCRPKI Not found134.235.18.0
- 134.235.19.0/24AS1540Headquarters, USAISCRPKI Not found134.235.19.0
- 134.235.20.0/23AS1540Headquarters, USAISCRPKI Not found134.235.20.0
- 134.235.22.0/24AS1540Headquarters, USAISCRPKI Not found134.235.22.0
- 134.235.23.0/24AS1540Headquarters, USAISCRPKI Not found134.235.23.0
- 134.235.24.0/24AS1540Headquarters, USAISCRPKI Not found134.235.24.0
- 134.235.25.0/24AS1540Headquarters, USAISCRPKI Not found134.235.25.0
- 134.235.28.0/23AS1540Headquarters, USAISCRPKI Not found134.235.28.0
- 134.235.54.0/24AS1540Headquarters, USAISCRPKI Not found134.235.54.0
- 134.235.55.0/24AS1540Headquarters, USAISCRPKI Not found134.235.55.0
- 134.235.56.0/24AS1540Headquarters, USAISCRPKI Not found134.235.56.0
- 134.235.57.0/24AS1540Headquarters, USAISCRPKI Not found134.235.57.0
- 134.235.58.0/24AS1540Headquarters, USAISCRPKI Not found134.235.58.0
- 134.235.60.0/23AS1540Headquarters, USAISCRPKI Not found134.235.60.0
- 134.235.64.0/24AS1540Headquarters, USAISCRPKI Not found134.235.64.0
- 134.235.65.0/24AS1540Headquarters, USAISCRPKI Not found134.235.65.0
- 134.235.66.0/24AS1540Headquarters, USAISCRPKI Not found134.235.66.0
- 134.235.67.0/24AS1540Headquarters, USAISCRPKI Not found134.235.67.0
- 134.235.81.0/24AS1540Headquarters, USAISCRPKI Not found134.235.81.0
- 134.235.82.0/24AS1540Headquarters, USAISCRPKI Not found134.235.82.0
- 134.235.92.0/24AS1540Headquarters, USAISCRPKI Not found134.235.92.0
- 134.235.98.0/24AS1540Headquarters, USAISCRPKI Not found134.235.98.0
- 134.235.100.0/23AS1540Headquarters, USAISCRPKI Not found134.235.100.0
- 134.235.102.0/23AS1540Headquarters, USAISCRPKI Not found134.235.102.0
- 134.235.105.0/24AS1540Headquarters, USAISCRPKI Not found134.235.105.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.