BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
207.132.0.0/15
Announced exactly
- 207.132.0.0/15AS721United States Department of Defense (DoD)RPKI Not found207.132.0.0
- Registry
- ARIN · United States · May 8, 1996
- Delegated block
- 207.132.0.0 – 207.133.255.255
Covering routes
No less-specific route covers it.
More-specific routes
- 207.132.33.0/24AS2749Navy Network Information Center (NNIC)RPKI Not found207.132.33.0
- 207.132.76.0/24AS27064United States Department of Defense (DoD)RPKI Not found207.132.76.0
- 207.132.83.0/24AS1904United States Department of Defense (DoD)RPKI Not found207.132.83.0
- 207.132.97.0/24AS367United States Department of Defense (DoD)RPKI Not found207.132.97.0
- 207.132.100.0/24AS27066United States Department of Defense (DoD)RPKI Not found207.132.100.0
- 207.132.116.0/24AS5927United States Department of Defense (DoD)RPKI Not found207.132.116.0
- 207.132.117.0/24AS5927United States Department of Defense (DoD)RPKI Not found207.132.117.0
- 207.132.127.0/24AS5180United States Department of Defense (DoD)RPKI Not found207.132.127.0
- 207.132.147.0/24AS668United States Department of Defense (DoD)RPKI Not found207.132.147.0
- 207.132.199.0/24AS27065United States Department of Defense (DoD)RPKI Not found207.132.199.0
- 207.132.201.0/24AS5180United States Department of Defense (DoD)RPKI Not found207.132.201.0
- 207.132.202.0/24AS5180United States Department of Defense (DoD)RPKI Not found207.132.202.0
- 207.132.241.0/24AS27064United States Department of Defense (DoD)RPKI Not found207.132.241.0
- 207.132.242.0/24AS27064United States Department of Defense (DoD)RPKI Not found207.132.242.0
- 207.132.243.0/24AS27064United States Department of Defense (DoD)RPKI Not found207.132.243.0
- 207.133.0.0/24AS6026United States Department of Defense (DoD)RPKI Not found207.133.0.0
- 207.133.1.0/24AS6026United States Department of Defense (DoD)RPKI Not found207.133.1.0
- 207.133.4.0/23AS6026United States Department of Defense (DoD)RPKI Not found207.133.4.0
- 207.133.6.0/24AS6026United States Department of Defense (DoD)RPKI Not found207.133.6.0
- 207.133.8.0/21AS1540Headquarters, USAISCRPKI Not found207.133.8.0
- 207.133.16.0/21AS1540Headquarters, USAISCRPKI Not found207.133.16.0
- 207.133.66.0/24AS5180United States Department of Defense (DoD)RPKI Not found207.133.66.0
- 207.133.75.0/24AS5180United States Department of Defense (DoD)RPKI Not found207.133.75.0
- 207.133.76.0/24AS5180United States Department of Defense (DoD)RPKI Not found207.133.76.0
- 207.133.77.0/24AS5180United States Department of Defense (DoD)RPKI Not found207.133.77.0
- 207.133.78.0/24AS27065United States Department of Defense (DoD)RPKI Not found207.133.78.0
- 207.133.79.0/24AS27065United States Department of Defense (DoD)RPKI Not found207.133.79.0
- 207.133.80.0/24AS27065United States Department of Defense (DoD)RPKI Not found207.133.80.0
- 207.133.82.0/24AS5180United States Department of Defense (DoD)RPKI Not found207.133.82.0
- 207.133.116.0/24AS27142United States Department of Defense (DoD)RPKI Not found207.133.116.0
- 207.133.128.0/24AS5180United States Department of Defense (DoD)RPKI Not found207.133.128.0
- 207.133.129.0/24AS5180United States Department of Defense (DoD)RPKI Not found207.133.129.0
- 207.133.131.0/24AS5180United States Department of Defense (DoD)RPKI Not found207.133.131.0
- 207.133.134.0/24AS27064United States Department of Defense (DoD)RPKI Not found207.133.134.0
- 207.133.135.0/24AS27064United States Department of Defense (DoD)RPKI Not found207.133.135.0
- 207.133.136.0/23AS3954United States Department of Defense (DoD)RPKI Not found207.133.136.0
- 207.133.138.0/24AS5180United States Department of Defense (DoD)RPKI Not found207.133.138.0
- 207.133.140.0/24AS5182United States Department of Defense (DoD)RPKI Not found207.133.140.0
- 207.133.141.0/24AS3954United States Department of Defense (DoD)RPKI Not found207.133.141.0
- 207.133.148.0/24AS5180United States Department of Defense (DoD)RPKI Not found207.133.148.0
- 207.133.150.0/24AS5180United States Department of Defense (DoD)RPKI Not found207.133.150.0
- 207.133.151.0/24AS5180United States Department of Defense (DoD)RPKI Not found207.133.151.0
- 207.133.162.0/24AS56United States Department of Defense (DoD)RPKI Not found207.133.162.0
- 207.133.167.0/24AS56United States Department of Defense (DoD)RPKI Not found207.133.167.0
- 207.133.168.0/24AS56United States Department of Defense (DoD)RPKI Not found207.133.168.0
- 207.133.169.0/24AS56United States Department of Defense (DoD)RPKI Not found207.133.169.0
- 207.133.170.0/24AS56United States Department of Defense (DoD)RPKI Not found207.133.170.0
- 207.133.172.0/24AS56United States Department of Defense (DoD)RPKI Not found207.133.172.0
- 207.133.173.0/24AS56United States Department of Defense (DoD)RPKI Not found207.133.173.0
- 207.133.174.0/24AS56United States Department of Defense (DoD)RPKI Not found207.133.174.0
- 207.133.175.0/24AS56United States Department of Defense (DoD)RPKI Not found207.133.175.0
- 207.133.177.0/24AS56United States Department of Defense (DoD)RPKI Not found207.133.177.0
- 207.133.179.0/24AS391Air Force Systems NetworkingRPKI Not found207.133.179.0
- 207.133.189.0/24AS391Air Force Systems NetworkingRPKI Not found207.133.189.0
- 207.133.190.0/24AS56United States Department of Defense (DoD)RPKI Not found207.133.190.0
- 207.133.194.0/24AS153Headquarters, USAISCRPKI Not found207.133.194.0
- 207.133.198.0/24AS1540Headquarters, USAISCRPKI Not found207.133.198.0
- 207.133.205.0/24AS1540Headquarters, USAISCRPKI Not found207.133.205.0
- 207.133.206.0/23AS1540Headquarters, USAISCRPKI Not found207.133.206.0
- 207.133.211.0/24AS668United States Department of Defense (DoD)RPKI Not found207.133.211.0
- 207.133.219.0/24AS1540Headquarters, USAISCRPKI Not found207.133.219.0
- 207.133.220.0/24AS1540Headquarters, USAISCRPKI Not found207.133.220.0
- 207.133.241.0/24AS5180United States Department of Defense (DoD)RPKI Not found207.133.241.0
- 207.133.242.0/24AS3954United States Department of Defense (DoD)RPKI Not found207.133.242.0
- 207.133.243.0/24AS3954United States Department of Defense (DoD)RPKI Not found207.133.243.0
- 207.133.245.0/24AS5182United States Department of Defense (DoD)RPKI Not found207.133.245.0
- 207.133.246.0/24AS5182United States Department of Defense (DoD)RPKI Not found207.133.246.0
- 207.133.247.0/24AS5180United States Department of Defense (DoD)RPKI Not found207.133.247.0
- 207.133.249.0/24AS5182United States Department of Defense (DoD)RPKI Not found207.133.249.0
- 207.133.250.0/24AS5182United States Department of Defense (DoD)RPKI Not found207.133.250.0
- 207.133.251.0/24AS5182United States Department of Defense (DoD)RPKI Not found207.133.251.0
- 207.133.252.0/24AS5182United States Department of Defense (DoD)RPKI Not found207.133.252.0
- 207.133.254.0/24AS5182United States Department of Defense (DoD)RPKI Not found207.133.254.0
- 207.133.255.0/24AS5182United States Department of Defense (DoD)RPKI Not found207.133.255.0
On the internet, routes are announced as prefixes: an autonomous system tells its neighbours via BGP that it can deliver traffic for, say, 193.166.0.0/15. 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.