BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
155.152.0.0/14
Announced exactly
- 155.152.0.0/14AS721United States Department of Defense (DoD)RPKI Not found155.152.0.0
- Registry
- ARIN · United States · Dec 23, 1991
- Delegated block
- 155.152.0.0 – 155.152.255.255
Covering routes
No less-specific route covers it.
More-specific routes
- 155.152.0.0/17AS1540Headquarters, USAISCRPKI Not found155.152.0.0
- 155.152.128.0/20AS1493Headquarters, USAISCRPKI Not found155.152.128.0
- 155.152.144.0/22AS1493Headquarters, USAISCRPKI Not found155.152.144.0
- 155.152.150.0/24AS1493Headquarters, USAISCRPKI Not found155.152.150.0
- 155.152.164.0/22AS1590United States Department of Defense (DoD)RPKI Not found155.152.164.0
- 155.152.176.0/20AS1493Headquarters, USAISCRPKI Not found155.152.176.0
- 155.152.212.0/22AS1540Headquarters, USAISCRPKI Not found155.152.212.0
- 155.152.216.0/24AS1540Headquarters, USAISCRPKI Not found155.152.216.0
- 155.152.217.0/24AS1540Headquarters, USAISCRPKI Not found155.152.217.0
- 155.152.218.0/24AS1540Headquarters, USAISCRPKI Not found155.152.218.0
- 155.152.221.0/24AS1590United States Department of Defense (DoD)RPKI Not found155.152.221.0
- 155.152.223.0/24AS1590United States Department of Defense (DoD)RPKI Not found155.152.223.0
- 155.152.253.0/24AS1540Headquarters, USAISCRPKI Not found155.152.253.0
- 155.152.254.0/24AS1540Headquarters, USAISCRPKI Not found155.152.254.0
- 155.153.0.0/16AS1540Headquarters, USAISCRPKI Not found155.153.0.0
- 155.154.0.0/16AS668United States Department of Defense (DoD)RPKI Not found155.154.0.0
- 155.155.0.0/16AS721United States Department of Defense (DoD)RPKI Not found155.155.0.0
- 155.155.16.0/20AS1554United States Department of Defense (DoD)RPKI Not found155.155.16.0
- 155.155.32.0/24AS1585United States Department of Defense (DoD)RPKI Not found155.155.32.0
- 155.155.33.0/24AS1585United States Department of Defense (DoD)RPKI Not found155.155.33.0
- 155.155.48.0/20AS1554United States Department of Defense (DoD)RPKI Not found155.155.48.0
- 155.155.64.0/19AS1554United States Department of Defense (DoD)RPKI Not found155.155.64.0
- 155.155.80.0/20AS1554United States Department of Defense (DoD)RPKI Not found155.155.80.0
- 155.155.91.0/24AS1554United States Department of Defense (DoD)RPKI Not found155.155.91.0
- 155.155.96.0/19AS1554United States Department of Defense (DoD)RPKI Not found155.155.96.0
- 155.155.112.0/20AS1554United States Department of Defense (DoD)RPKI Not found155.155.112.0
- 155.155.128.0/19AS1554United States Department of Defense (DoD)RPKI Not found155.155.128.0
- 155.155.192.0/23AS1556United States Department of Defense (DoD)RPKI Not found155.155.192.0
- 155.155.224.0/20AS1554United States Department of Defense (DoD)RPKI Not found155.155.224.0
- 155.155.240.0/20AS1554United States Department of Defense (DoD)RPKI Not found155.155.240.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.