BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
72.164.0.0/15
Announced exactly
- 72.164.0.0/15AS209CenturyLink Communications, LLCRPKI Not found72.164.0.0
- Registry
- ARIN · United States · Oct 28, 2005
- Delegated block
- 72.164.0.0 – 72.165.255.255
Covering routes
No less-specific route covers it.
More-specific routes
- 72.164.18.0/24AS3356Level 3 Parent, LLCRPKI Not found72.164.18.0
- 72.164.134.0/24AS14487Wind River InternetRPKI Not found72.164.134.0
- 72.164.216.0/24AS3356Level 3 Parent, LLCRPKI Not found72.164.216.0
- 72.164.217.0/24AS3356Level 3 Parent, LLCRPKI Not found72.164.217.0
- 72.164.219.0/24AS3356Level 3 Parent, LLCRPKI Not found72.164.219.0
- 72.165.8.0/23AS3356Level 3 Parent, LLCRPKI Not found72.165.8.0
- 72.165.12.0/23AS17385Orbitel Communications, LLCRPKI Not found72.165.12.0
- 72.165.28.0/23AS10835Visionary Communications LLCRPKI Not found72.165.28.0
- 72.165.69.0/24AS54538PALO ALTO NETWORKSRPKI Not found72.165.69.0
- 72.165.163.0/24AS395391Talking Platforms, LLCRPKI Not found72.165.163.0
- 72.165.188.0/24AS400160City of YumaRPKI Not found72.165.188.0
- 72.165.202.0/24AS395391Talking Platforms, LLCRPKI Not found72.165.202.0
- 72.165.236.0/24AS10753Level 3 Parent, LLCRPKI Not found72.165.236.0
- 72.165.237.0/24AS10753Level 3 Parent, LLCRPKI Not found72.165.237.0
- 72.165.239.0/24AS20103Valmont IndustriesRPKI Not found72.165.239.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.