BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
6.42.128.0/18
Announced exactly
- 6.42.128.0/18AS749United States Department of Defense (DoD)RPKI Not found6.42.128.0
- Registry
- ARIN · United States · Feb 1, 1994
- Delegated block
- 6.0.0.0 – 6.255.255.255
Covering routes
No less-specific route covers it.
More-specific routes
- 6.42.128.0/23AS1540Headquarters, USAISCRPKI Not found6.42.128.0
- 6.42.130.0/23AS1540Headquarters, USAISCRPKI Not found6.42.130.0
- 6.42.132.0/23AS1540Headquarters, USAISCRPKI Not found6.42.132.0
- 6.42.134.0/23AS1540Headquarters, USAISCRPKI Not found6.42.134.0
- 6.42.136.0/23AS1540Headquarters, USAISCRPKI Not found6.42.136.0
- 6.42.138.0/23AS1540Headquarters, USAISCRPKI Not found6.42.138.0
- 6.42.140.0/23AS1540Headquarters, USAISCRPKI Not found6.42.140.0
- 6.42.142.0/23AS1540Headquarters, USAISCRPKI Not found6.42.142.0
- 6.42.144.0/23AS1540Headquarters, USAISCRPKI Not found6.42.144.0
- 6.42.146.0/23AS1540Headquarters, USAISCRPKI Not found6.42.146.0
- 6.42.148.0/23AS1540Headquarters, USAISCRPKI Not found6.42.148.0
- 6.42.150.0/23AS1540Headquarters, USAISCRPKI Not found6.42.150.0
- 6.42.152.0/23AS1540Headquarters, USAISCRPKI Not found6.42.152.0
- 6.42.154.0/23AS1540Headquarters, USAISCRPKI Not found6.42.154.0
- 6.42.156.0/23AS1540Headquarters, USAISCRPKI Not found6.42.156.0
- 6.42.158.0/23AS1540Headquarters, USAISCRPKI Not found6.42.158.0
- 6.42.160.0/23AS1540Headquarters, USAISCRPKI Not found6.42.160.0
- 6.42.162.0/23AS1540Headquarters, USAISCRPKI Not found6.42.162.0
- 6.42.164.0/23AS1540Headquarters, USAISCRPKI Not found6.42.164.0
- 6.42.166.0/23AS1540Headquarters, USAISCRPKI Not found6.42.166.0
- 6.42.168.0/23AS1540Headquarters, USAISCRPKI Not found6.42.168.0
- 6.42.170.0/23AS1540Headquarters, USAISCRPKI Not found6.42.170.0
- 6.42.172.0/23AS1540Headquarters, USAISCRPKI Not found6.42.172.0
- 6.42.174.0/23AS1540Headquarters, USAISCRPKI Not found6.42.174.0
- 6.42.176.0/23AS1540Headquarters, USAISCRPKI Not found6.42.176.0
- 6.42.178.0/23AS1540Headquarters, USAISCRPKI Not found6.42.178.0
- 6.42.180.0/23AS1540Headquarters, USAISCRPKI Not found6.42.180.0
- 6.42.182.0/23AS1540Headquarters, USAISCRPKI Not found6.42.182.0
- 6.42.184.0/23AS1540Headquarters, USAISCRPKI Not found6.42.184.0
- 6.42.186.0/23AS1540Headquarters, USAISCRPKI Not found6.42.186.0
- 6.42.188.0/23AS1540Headquarters, USAISCRPKI Not found6.42.188.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.