BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
71.48.0.0/13
Announced exactly
- 71.48.0.0/13AS209CenturyLink Communications, LLCRPKI Not found71.48.0.0
- Registry
- ARIN · United States · Apr 26, 2005
- Delegated block
- 71.48.0.0 – 71.55.255.255
Covering routes
No less-specific route covers it.
More-specific routes
- 71.48.32.0/20AS209CenturyLink Communications, LLCRPKI Not found71.48.32.0
- 71.48.56.0/21AS209CenturyLink Communications, LLCRPKI Not found71.48.56.0
- 71.48.112.0/20AS17402CenturyLink Communications, LLCRPKI Not found71.48.112.0
- 71.48.176.0/21AS14921CenturyLink Communications, LLCRPKI Not found71.48.176.0
- 71.48.184.0/21AS6222CenturyLink Communications, LLCRPKI Not found71.48.184.0
- 71.48.192.0/21AS19901BrightspeedRPKI Not found71.48.192.0
- 71.49.0.0/19AS2379CenturyLink Communications, LLCRPKI Not found71.49.0.0
- 71.49.32.0/19AS19901BrightspeedRPKI Not found71.49.32.0
- 71.49.80.0/20AS17402CenturyLink Communications, LLCRPKI Not found71.49.80.0
- 71.49.96.0/19AS2379CenturyLink Communications, LLCRPKI Not found71.49.96.0
- 71.49.128.0/20AS209CenturyLink Communications, LLCRPKI Not found71.49.128.0
- 71.49.168.0/21AS209CenturyLink Communications, LLCRPKI Not found71.49.168.0
- 71.49.192.0/21AS19901BrightspeedRPKI Not found71.49.192.0
- 71.49.204.0/23AS209CenturyLink Communications, LLCRPKI Not found71.49.204.0
- 71.49.206.0/23AS209CenturyLink Communications, LLCRPKI Not found71.49.206.0
- 71.49.224.0/20AS209CenturyLink Communications, LLCRPKI Not found71.49.224.0
- 71.50.0.0/20AS14921CenturyLink Communications, LLCRPKI Not found71.50.0.0
- 71.50.32.0/19AS19901BrightspeedRPKI Not found71.50.32.0
- 71.50.64.0/19AS11398CenturyLink Communications, LLCRPKI Not found71.50.64.0
- 71.50.64.0/20AS209CenturyLink Communications, LLCRPKI Not found71.50.64.0
- 71.50.128.0/18AS19901BrightspeedRPKI Not found71.50.128.0
- 71.50.192.0/19AS19901BrightspeedRPKI Not found71.50.192.0
- 71.51.64.0/19AS2379CenturyLink Communications, LLCRPKI Not found71.51.64.0
- 71.51.64.0/20AS209CenturyLink Communications, LLCRPKI Not found71.51.64.0
- 71.51.96.0/20AS19901BrightspeedRPKI Not found71.51.96.0
- 71.51.128.0/19AS17402CenturyLink Communications, LLCRPKI Not found71.51.128.0
- 71.51.160.0/19AS19901BrightspeedRPKI Not found71.51.160.0
- 71.51.216.0/21AS19901BrightspeedRPKI Not found71.51.216.0
- 71.52.0.0/19AS209CenturyLink Communications, LLCRPKI Not found71.52.0.0
- 71.52.48.0/20AS209CenturyLink Communications, LLCRPKI Not found71.52.48.0
- 71.52.96.0/19AS2379CenturyLink Communications, LLCRPKI Not found71.52.96.0
- 71.52.96.0/20AS209CenturyLink Communications, LLCRPKI Not found71.52.96.0
- 71.53.64.0/21AS14921CenturyLink Communications, LLCRPKI Not found71.53.64.0
- 71.53.72.0/21AS14921CenturyLink Communications, LLCRPKI Not found71.53.72.0
- 71.53.128.0/19AS19901BrightspeedRPKI Not found71.53.128.0
- 71.53.224.0/19AS2379CenturyLink Communications, LLCRPKI Not found71.53.224.0
- 71.54.0.0/19AS209CenturyLink Communications, LLCRPKI Not found71.54.0.0
- 71.54.32.0/19AS19901BrightspeedRPKI Not found71.54.32.0
- 71.54.160.0/19AS209CenturyLink Communications, LLCRPKI Not found71.54.160.0
- 71.54.192.0/20AS209CenturyLink Communications, LLCRPKI Not found71.54.192.0
- 71.55.64.0/19AS19901BrightspeedRPKI Not found71.55.64.0
- 71.55.104.0/21AS209CenturyLink Communications, LLCRPKI Not found71.55.104.0
- 71.55.128.0/19AS17402CenturyLink Communications, LLCRPKI Not found71.55.128.0
- 71.55.192.0/19AS2379CenturyLink Communications, LLCRPKI Not found71.55.192.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.