BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
216.32.0.0/14
Announced exactly
- 216.32.0.0/14AS3561CenturyLink Communications, LLCRPKI Not found216.32.0.0
- Registry
- ARIN · United States · Jul 30, 1998
- Delegated block
- 216.32.0.0 – 216.35.255.255
Covering routes
No less-specific route covers it.
More-specific routes
- 216.32.0.0/19AS3561CenturyLink Communications, LLCRPKI Not found216.32.0.0
- 216.32.32.0/19AS3561CenturyLink Communications, LLCRPKI Not found216.32.32.0
- 216.32.60.0/24AS14415Host Collective, Inc.RPKI Not found216.32.60.0
- 216.32.62.0/24AS394463Veros SoftwareRPKI Not found216.32.62.0
- 216.32.80.0/23AS10899Caris Life SciencesRPKI Not found216.32.80.0
- 216.32.80.0/24AS10899Caris Life SciencesRPKI Not found216.32.80.0
- 216.32.81.0/24AS10899Caris Life SciencesRPKI Not found216.32.81.0
- 216.32.120.0/21AS3561CenturyLink Communications, LLCRPKI Not found216.32.120.0
- 216.32.128.0/19AS3561CenturyLink Communications, LLCRPKI Not found216.32.128.0
- 216.32.151.0/24AS203Level 3 Parent, LLCRPKI Not found216.32.151.0
- 216.32.160.0/19AS3561CenturyLink Communications, LLCRPKI Not found216.32.160.0
- 216.32.180.0/22AS8075Microsoft CorporationRPKI Not found216.32.180.0
- 216.32.224.0/19AS3561CenturyLink Communications, LLCRPKI Not found216.32.224.0
- 216.33.0.0/19AS3561CenturyLink Communications, LLCRPKI Not found216.33.0.0
- 216.33.60.0/22AS3561CenturyLink Communications, LLCRPKI Not found216.33.60.0
- 216.33.64.0/19AS3561CenturyLink Communications, LLCRPKI Not found216.33.64.0
- 216.33.90.0/23AS397076ECi Software Solutions, Inc.RPKI Not found216.33.90.0
- 216.33.96.0/19AS3561CenturyLink Communications, LLCRPKI Not found216.33.96.0
- 216.33.132.0/22AS3561CenturyLink Communications, LLCRPKI Not found216.33.132.0
- 216.33.160.0/19AS3561CenturyLink Communications, LLCRPKI Not found216.33.160.0
- 216.33.160.0/24AS203Level 3 Parent, LLCRPKI Not found216.33.160.0
- 216.33.192.0/20AS3561CenturyLink Communications, LLCRPKI Not found216.33.192.0
- 216.33.198.0/24AS3561CenturyLink Communications, LLCRPKI Not found216.33.198.0
- 216.33.224.0/19AS3561CenturyLink Communications, LLCRPKI Not found216.33.224.0
- 216.34.0.0/19AS3561CenturyLink Communications, LLCRPKI Not found216.34.0.0
- 216.34.32.0/20AS3561CenturyLink Communications, LLCRPKI Not found216.34.32.0
- 216.34.48.0/20AS3561CenturyLink Communications, LLCRPKI Not found216.34.48.0
- 216.34.60.0/24AS19701Yodlee Inc.RPKI Not found216.34.60.0
- 216.34.61.0/24AS19701Yodlee Inc.RPKI Not found216.34.61.0
- 216.34.64.0/19AS3561CenturyLink Communications, LLCRPKI Not found216.34.64.0
- 216.34.96.0/19AS3561CenturyLink Communications, LLCRPKI Not found216.34.96.0
- 216.34.102.0/23AS8739ICDSoft Ltd.RPKI Not found216.34.102.0
- 216.34.104.0/23AS8739ICDSoft Ltd.RPKI Not found216.34.104.0
- 216.34.108.0/23AS8739ICDSoft Ltd.RPKI Not found216.34.108.0
- 216.34.114.0/23AS8739ICDSoft Ltd.RPKI Not found216.34.114.0
- 216.34.116.0/22AS8739ICDSoft Ltd.RPKI Not found216.34.116.0
- 216.34.124.0/23AS8739ICDSoft Ltd.RPKI Not found216.34.124.0
- 216.34.128.0/20AS3561CenturyLink Communications, LLCRPKI Not found216.34.128.0
- 216.34.144.0/20AS3561CenturyLink Communications, LLCRPKI Not found216.34.144.0
- 216.34.160.0/20AS3561CenturyLink Communications, LLCRPKI Not found216.34.160.0
- 216.34.176.0/20AS3561CenturyLink Communications, LLCRPKI Not found216.34.176.0
- 216.34.192.0/19AS3561CenturyLink Communications, LLCRPKI Not found216.34.192.0
- 216.34.207.0/24AS26762Conversant, LLCRPKI Not found216.34.207.0
- 216.34.224.0/19AS3561CenturyLink Communications, LLCRPKI Not found216.34.224.0
- 216.35.0.0/19AS3561CenturyLink Communications, LLCRPKI Not found216.35.0.0
- 216.35.6.0/24AS19701Yodlee Inc.RPKI Not found216.35.6.0
- 216.35.59.0/24AS6195The Goldman Sachs Group, Inc.RPKI Valid216.35.59.0
- 216.35.64.0/20AS3561CenturyLink Communications, LLCRPKI Not found216.35.64.0
- 216.35.104.0/21AS3561CenturyLink Communications, LLCRPKI Not found216.35.104.0
- 216.35.112.0/20AS3561CenturyLink Communications, LLCRPKI Not found216.35.112.0
- 216.35.128.0/19AS3561CenturyLink Communications, LLCRPKI Not found216.35.128.0
- 216.35.176.0/20AS3561CenturyLink Communications, LLCRPKI Not found216.35.176.0
- 216.35.192.0/20AS3561CenturyLink Communications, LLCRPKI Not found216.35.192.0
- 216.35.194.0/23AS8739ICDSoft Ltd.RPKI Not found216.35.194.0
- 216.35.196.0/23AS8739ICDSoft Ltd.RPKI Not found216.35.196.0
- 216.35.205.0/24AS8739ICDSoft Ltd.RPKI Not found216.35.205.0
- 216.35.207.0/24AS8739ICDSoft Ltd.RPKI Not found216.35.207.0
- 216.35.208.0/20AS3561CenturyLink Communications, LLCRPKI Not found216.35.208.0
- 216.35.224.0/19AS3561CenturyLink Communications, LLCRPKI Not found216.35.224.0
- 216.35.243.0/24AS42427Mimecast Services LimitedRPKI Not found216.35.243.0
- 216.35.244.0/24AS42427Mimecast Services LimitedRPKI Not found216.35.244.0
- 216.35.245.0/24AS3561CenturyLink Communications, LLCRPKI Not found216.35.245.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.