BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
136.220.0.0/15
Announced exactly
- 136.220.0.0/15AS721United States Department of Defense (DoD)RPKI Not found136.220.0.0
- Registry
- ARIN · United States · Sep 29, 1989
- Delegated block
- 136.220.0.0 – 136.220.255.255
Covering routes
No less-specific route covers it.
More-specific routes
- 136.220.17.0/24AS1540Headquarters, USAISCRPKI Not found136.220.17.0
- 136.220.18.0/24AS1540Headquarters, USAISCRPKI Not found136.220.18.0
- 136.220.19.0/24AS1540Headquarters, USAISCRPKI Not found136.220.19.0
- 136.220.20.0/24AS1540Headquarters, USAISCRPKI Not found136.220.20.0
- 136.220.21.0/24AS1540Headquarters, USAISCRPKI Not found136.220.21.0
- 136.220.22.0/24AS1540Headquarters, USAISCRPKI Not found136.220.22.0
- 136.220.23.0/24AS1540Headquarters, USAISCRPKI Not found136.220.23.0
- 136.220.24.0/24AS1540Headquarters, USAISCRPKI Not found136.220.24.0
- 136.220.25.0/24AS1540Headquarters, USAISCRPKI Not found136.220.25.0
- 136.220.26.0/24AS1540Headquarters, USAISCRPKI Not found136.220.26.0
- 136.220.27.0/24AS1540Headquarters, USAISCRPKI Not found136.220.27.0
- 136.220.28.0/24AS1540Headquarters, USAISCRPKI Not found136.220.28.0
- 136.220.29.0/24AS1540Headquarters, USAISCRPKI Not found136.220.29.0
- 136.220.30.0/23AS1540Headquarters, USAISCRPKI Not found136.220.30.0
- 136.220.32.0/22AS1540Headquarters, USAISCRPKI Not found136.220.32.0
- 136.220.36.0/24AS1540Headquarters, USAISCRPKI Not found136.220.36.0
- 136.220.38.0/24AS1540Headquarters, USAISCRPKI Not found136.220.38.0
- 136.220.58.0/24AS1540Headquarters, USAISCRPKI Not found136.220.58.0
- 136.220.59.0/24AS1540Headquarters, USAISCRPKI Not found136.220.59.0
- 136.220.60.0/24AS1540Headquarters, USAISCRPKI Not found136.220.60.0
- 136.220.83.0/24AS1540Headquarters, USAISCRPKI Not found136.220.83.0
- 136.220.84.0/24AS1540Headquarters, USAISCRPKI Not found136.220.84.0
- 136.220.85.0/24AS1540Headquarters, USAISCRPKI Not found136.220.85.0
- 136.220.86.0/24AS1540Headquarters, USAISCRPKI Not found136.220.86.0
- 136.220.87.0/24AS1540Headquarters, USAISCRPKI Not found136.220.87.0
- 136.220.88.0/24AS1540Headquarters, USAISCRPKI Not found136.220.88.0
- 136.220.89.0/24AS1540Headquarters, USAISCRPKI Not found136.220.89.0
- 136.220.90.0/24AS1540Headquarters, USAISCRPKI Not found136.220.90.0
- 136.220.91.0/24AS1540Headquarters, USAISCRPKI Not found136.220.91.0
- 136.220.92.0/24AS1540Headquarters, USAISCRPKI Not found136.220.92.0
- 136.220.93.0/24AS1540Headquarters, USAISCRPKI Not found136.220.93.0
- 136.220.94.0/24AS1540Headquarters, USAISCRPKI Not found136.220.94.0
- 136.220.124.0/24AS1540Headquarters, USAISCRPKI Not found136.220.124.0
- 136.220.125.0/24AS1540Headquarters, USAISCRPKI Not found136.220.125.0
- 136.220.126.0/24AS1540Headquarters, USAISCRPKI Not found136.220.126.0
- 136.220.128.0/23AS1540Headquarters, USAISCRPKI Not found136.220.128.0
- 136.220.130.0/24AS1540Headquarters, USAISCRPKI Not found136.220.130.0
- 136.220.142.0/24AS1540Headquarters, USAISCRPKI Not found136.220.142.0
- 136.220.143.0/24AS1540Headquarters, USAISCRPKI Not found136.220.143.0
- 136.220.170.0/23AS1540Headquarters, USAISCRPKI Not found136.220.170.0
- 136.220.172.0/23AS1540Headquarters, USAISCRPKI Not found136.220.172.0
- 136.220.230.0/23AS1540Headquarters, USAISCRPKI Not found136.220.230.0
- 136.220.232.0/23AS1540Headquarters, USAISCRPKI Not found136.220.232.0
- 136.220.234.0/24AS1540Headquarters, USAISCRPKI Not found136.220.234.0
- 136.220.235.0/24AS1540Headquarters, USAISCRPKI Not found136.220.235.0
- 136.220.240.0/23AS1540Headquarters, USAISCRPKI Not found136.220.240.0
- 136.220.242.0/23AS1540Headquarters, USAISCRPKI Not found136.220.242.0
- 136.220.244.0/24AS1540Headquarters, USAISCRPKI Not found136.220.244.0
- 136.220.245.0/24AS1540Headquarters, USAISCRPKI Not found136.220.245.0
- 136.220.252.0/22AS1540Headquarters, USAISCRPKI Not found136.220.252.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.