BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
80.174.128.0/17
Announced exactly
- 80.174.128.0/17AS29119AIRE NETWORKS DEL MEDITERRANEO SL UNIPERSONALRPKI Valid80.174.128.0
- Registry
- RIPE NCC · Spain · Jul 5, 2004
- Delegated block
- 80.174.0.0 – 80.174.255.255
Covering routes
No less-specific route covers it.
More-specific routes
- 80.174.135.0/24AS49453Global Layer B.V.RPKI Valid80.174.135.0
- 80.174.136.0/22AS6830Liberty Global Europe Holding B.V.RPKI Valid80.174.136.0
- 80.174.140.0/22AS6830Liberty Global Europe Holding B.V.RPKI Valid80.174.140.0
- 80.174.144.0/23AS2914NTT America, Inc.RPKI Valid80.174.144.0
- 80.174.148.0/22AS399138Microlink NetworkRPKI Valid80.174.148.0
- 80.174.172.0/22AS6282Fiber Optical Network LLCRPKI Valid80.174.172.0
- 80.174.176.0/22AS3561CenturyLink Communications, LLCRPKI Valid80.174.176.0
- 80.174.180.0/22AS399138Microlink NetworkRPKI Valid80.174.180.0
- 80.174.188.0/22AS6282Fiber Optical Network LLCRPKI Valid80.174.188.0
- 80.174.202.0/24AS13335Cloudflare, Inc.RPKI Valid80.174.202.0
- 80.174.203.0/24AS49453Global Layer B.V.RPKI Valid80.174.203.0
- 80.174.204.0/24AS49453Global Layer B.V.RPKI Valid80.174.204.0
- 80.174.205.0/24AS13335Cloudflare, Inc.RPKI Valid80.174.205.0
- 80.174.206.0/24AS212477RoyaleHosting BVRPKI Valid80.174.206.0
- 80.174.207.0/24AS212477RoyaleHosting BVRPKI Valid80.174.207.0
- 80.174.216.0/24AS3949NTT America, Inc.RPKI Valid80.174.216.0
- 80.174.217.0/24AS3949NTT America, Inc.RPKI Valid80.174.217.0
- 80.174.218.0/24AS3949NTT America, Inc.RPKI Valid80.174.218.0
- 80.174.219.0/24AS3949NTT America, Inc.RPKI Valid80.174.219.0
- 80.174.220.0/24AS3949NTT America, Inc.RPKI Valid80.174.220.0
- 80.174.221.0/24AS3949NTT America, Inc.RPKI Valid80.174.221.0
- 80.174.222.0/24AS3949NTT America, Inc.RPKI Valid80.174.222.0
- 80.174.223.0/24AS3949NTT America, Inc.RPKI Valid80.174.223.0
- 80.174.248.0/24AS2914NTT America, Inc.RPKI Valid80.174.248.0
- 80.174.251.0/24AS63018Dedicated.comRPKI Valid80.174.251.0
- 80.174.252.0/23AS395793Arisk Communications inc.RPKI Valid80.174.252.0
- 80.174.254.0/24AS395793Arisk Communications inc.RPKI Valid80.174.254.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.