BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
204.222.0.0/15
Announced exactly
- 204.222.0.0/15AS721United States Department of Defense (DoD)RPKI Not found204.222.0.0
- Registry
- ARIN · United States · Jan 5, 1995
- Delegated block
- 204.222.0.0 – 204.222.255.255
Covering routes
No less-specific route covers it.
More-specific routes
- 204.222.0.0/22AS27064United States Department of Defense (DoD)RPKI Not found204.222.0.0
- 204.222.6.0/23AS668United States Department of Defense (DoD)RPKI Not found204.222.6.0
- 204.222.8.0/23AS668United States Department of Defense (DoD)RPKI Not found204.222.8.0
- 204.222.64.0/21AS668United States Department of Defense (DoD)RPKI Not found204.222.64.0
- 204.222.89.0/24AS5180United States Department of Defense (DoD)RPKI Not found204.222.89.0
- 204.222.176.0/24AS5957United States Department of Defense (DoD)RPKI Not found204.222.176.0
- 204.222.177.0/24AS5957United States Department of Defense (DoD)RPKI Not found204.222.177.0
- 204.222.178.0/24AS5957United States Department of Defense (DoD)RPKI Not found204.222.178.0
- 204.222.179.0/24AS5957United States Department of Defense (DoD)RPKI Not found204.222.179.0
- 204.222.192.0/21AS27064United States Department of Defense (DoD)RPKI Not found204.222.192.0
- 204.222.212.0/24AS300United States Department of Defense (DoD)RPKI Not found204.222.212.0
- 204.222.228.0/23AS5978United States Department of Defense (DoD)RPKI Not found204.222.228.0
- 204.222.248.0/24AS56United States Department of Defense (DoD)RPKI Not found204.222.248.0
- 204.222.249.0/24AS56United States Department of Defense (DoD)RPKI Not found204.222.249.0
- 204.223.8.0/21AS637United States Department of Defense (DoD)RPKI Not found204.223.8.0
- 204.223.34.0/23AS637United States Department of Defense (DoD)RPKI Not found204.223.34.0
- 204.223.36.0/22AS637United States Department of Defense (DoD)RPKI Not found204.223.36.0
- 204.223.40.0/24AS637United States Department of Defense (DoD)RPKI Not found204.223.40.0
- 204.223.41.0/24AS637United States Department of Defense (DoD)RPKI Not found204.223.41.0
- 204.223.42.0/23AS637United States Department of Defense (DoD)RPKI Not found204.223.42.0
- 204.223.44.0/22AS637United States Department of Defense (DoD)RPKI Not found204.223.44.0
- 204.223.75.0/24AS637United States Department of Defense (DoD)RPKI Not found204.223.75.0
- 204.223.78.0/23AS637United States Department of Defense (DoD)RPKI Not found204.223.78.0
- 204.223.80.0/24AS637United States Department of Defense (DoD)RPKI Not found204.223.80.0
- 204.223.81.0/24AS637United States Department of Defense (DoD)RPKI Not found204.223.81.0
- 204.223.82.0/23AS637United States Department of Defense (DoD)RPKI Not found204.223.82.0
- 204.223.84.0/22AS637United States Department of Defense (DoD)RPKI Not found204.223.84.0
- 204.223.88.0/22AS637United States Department of Defense (DoD)RPKI Not found204.223.88.0
- 204.223.92.0/23AS637United States Department of Defense (DoD)RPKI Not found204.223.92.0
- 204.223.94.0/24AS637United States Department of Defense (DoD)RPKI Not found204.223.94.0
- 204.223.96.0/20AS637United States Department of Defense (DoD)RPKI Not found204.223.96.0
- 204.223.112.0/21AS637United States Department of Defense (DoD)RPKI Not found204.223.112.0
- 204.223.126.0/23AS637United States Department of Defense (DoD)RPKI Not found204.223.126.0
- 204.223.128.0/21AS637United States Department of Defense (DoD)RPKI Not found204.223.128.0
- 204.223.136.0/21AS637United States Department of Defense (DoD)RPKI Not found204.223.136.0
- 204.223.144.0/21AS637United States Department of Defense (DoD)RPKI Not found204.223.144.0
- 204.223.152.0/22AS637United States Department of Defense (DoD)RPKI Not found204.223.152.0
- 204.223.176.0/24AS637United States Department of Defense (DoD)RPKI Not found204.223.176.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.