BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
74.4.0.0/15
Announced exactly
- 74.4.0.0/15AS209CenturyLink Communications, LLCRPKI Not found74.4.0.0
- Registry
- ARIN · United States · Jan 10, 2006
- Delegated block
- 74.4.0.0 – 74.5.255.255
Covering routes
No less-specific route covers it.
More-specific routes
- 74.4.5.0/24AS22561CenturyLink Communications, LLCRPKI Not found74.4.5.0
- 74.4.7.0/24AS4284CenturyLink Communications, LLCRPKI Not found74.4.7.0
- 74.4.8.0/24AS11398CenturyLink Communications, LLCRPKI Not found74.4.8.0
- 74.4.9.0/24AS4283CenturyLink Communications, LLCRPKI Not found74.4.9.0
- 74.4.10.0/24AS2379CenturyLink Communications, LLCRPKI Not found74.4.10.0
- 74.4.11.0/24AS4282CenturyLink Communications, LLCRPKI Not found74.4.11.0
- 74.4.12.0/24AS13787CenturyLink Communications, LLCRPKI Not found74.4.12.0
- 74.4.13.0/24AS13787CenturyLink Communications, LLCRPKI Not found74.4.13.0
- 74.4.16.0/21AS22561CenturyLink Communications, LLCRPKI Not found74.4.16.0
- 74.4.31.0/24AS54274Henny Penny CorporationRPKI Not found74.4.31.0
- 74.4.48.0/20AS209CenturyLink Communications, LLCRPKI Not found74.4.48.0
- 74.4.96.0/20AS2379CenturyLink Communications, LLCRPKI Not found74.4.96.0
- 74.4.104.0/22AS209CenturyLink Communications, LLCRPKI Not found74.4.104.0
- 74.4.108.0/23AS209CenturyLink Communications, LLCRPKI Not found74.4.108.0
- 74.4.110.0/24AS209CenturyLink Communications, LLCRPKI Not found74.4.110.0
- 74.4.160.0/20AS2379CenturyLink Communications, LLCRPKI Not found74.4.160.0
- 74.4.176.0/21AS14921CenturyLink Communications, LLCRPKI Not found74.4.176.0
- 74.4.192.0/19AS2379CenturyLink Communications, LLCRPKI Not found74.4.192.0
- 74.5.0.0/19AS19901BrightspeedRPKI Not found74.5.0.0
- 74.5.64.0/19AS17402CenturyLink Communications, LLCRPKI Not found74.5.64.0
- 74.5.128.0/19AS19901BrightspeedRPKI Not found74.5.128.0
- 74.5.168.0/21AS2379CenturyLink Communications, LLCRPKI Not found74.5.168.0
- 74.5.192.0/21AS13787CenturyLink Communications, LLCRPKI Not found74.5.192.0
- 74.5.200.0/21AS22561CenturyLink Communications, LLCRPKI Not found74.5.200.0
- 74.5.208.0/21AS17402CenturyLink Communications, LLCRPKI Not found74.5.208.0
- 74.5.224.0/19AS2379CenturyLink Communications, LLCRPKI Not found74.5.224.0
- 74.5.247.0/24AS209CenturyLink Communications, LLCRPKI Not found74.5.247.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.