BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
143.140.0.0/14
Announced exactly
- 143.140.0.0/14AS721United States Department of Defense (DoD)RPKI Not found143.140.0.0
- Registry
- ARIN · United States · Sep 21, 1990
- Delegated block
- 143.140.0.0 – 143.143.255.255
Covering routes
No less-specific route covers it.
More-specific routes
- 143.140.0.0/21AS56United States Department of Defense (DoD)RPKI Not found143.140.0.0
- 143.140.8.0/23AS56United States Department of Defense (DoD)RPKI Not found143.140.8.0
- 143.140.10.0/24AS56United States Department of Defense (DoD)RPKI Not found143.140.10.0
- 143.140.11.0/24AS129United States Department of Defense (DoD)RPKI Not found143.140.11.0
- 143.140.32.0/19AS56United States Department of Defense (DoD)RPKI Not found143.140.32.0
- 143.140.64.0/21AS409Air Force Systems NetworkingRPKI Not found143.140.64.0
- 143.140.70.0/24AS409Air Force Systems NetworkingRPKI Not found143.140.70.0
- 143.140.128.0/19AS56United States Department of Defense (DoD)RPKI Not found143.140.128.0
- 143.140.160.0/20AS56United States Department of Defense (DoD)RPKI Not found143.140.160.0
- 143.141.96.0/22AS391Air Force Systems NetworkingRPKI Not found143.141.96.0
- 143.141.100.0/22AS56United States Department of Defense (DoD)RPKI Not found143.141.100.0
- 143.141.104.0/22AS56United States Department of Defense (DoD)RPKI Not found143.141.104.0
- 143.141.112.0/24AS56United States Department of Defense (DoD)RPKI Not found143.141.112.0
- 143.141.113.0/24AS56United States Department of Defense (DoD)RPKI Not found143.141.113.0
- 143.141.114.0/24AS56United States Department of Defense (DoD)RPKI Not found143.141.114.0
- 143.141.115.0/24AS56United States Department of Defense (DoD)RPKI Not found143.141.115.0
- 143.141.116.0/24AS56United States Department of Defense (DoD)RPKI Not found143.141.116.0
- 143.141.117.0/24AS56United States Department of Defense (DoD)RPKI Not found143.141.117.0
- 143.141.118.0/24AS56United States Department of Defense (DoD)RPKI Not found143.141.118.0
- 143.141.119.0/24AS56United States Department of Defense (DoD)RPKI Not found143.141.119.0
- 143.141.128.0/22AS56United States Department of Defense (DoD)RPKI Not found143.141.128.0
- 143.141.136.0/21AS56United States Department of Defense (DoD)RPKI Not found143.141.136.0
- 143.141.160.0/20AS56United States Department of Defense (DoD)RPKI Not found143.141.160.0
- 143.141.176.0/20AS56United States Department of Defense (DoD)RPKI Not found143.141.176.0
- 143.141.192.0/18AS56United States Department of Defense (DoD)RPKI Not found143.141.192.0
- 143.142.0.0/18AS56United States Department of Defense (DoD)RPKI Not found143.142.0.0
- 143.142.96.0/21AS56United States Department of Defense (DoD)RPKI Not found143.142.96.0
- 143.142.106.0/24AS56United States Department of Defense (DoD)RPKI Not found143.142.106.0
- 143.142.160.0/20AS56United States Department of Defense (DoD)RPKI Not found143.142.160.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.