BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
81.2.128.0/18
Announced exactly
- 81.2.128.0/18AS174Cogent Communications, LLCRPKI Not found81.2.128.0
- Registry
- RIPE NCC · United States · Mar 15, 2002
- Delegated block
- 81.2.128.0 – 81.2.191.255
Covering routes
No less-specific route covers it.
More-specific routes
- 81.2.128.0/24AS19970R&R Managed Telecom ServicesRPKI Not found81.2.128.0
- 81.2.132.0/22AS203591TECNO GENERAL S.R.LRPKI Valid81.2.132.0
- 81.2.136.0/24AS213671Vision Fibre Media Ltd.RPKI Valid81.2.136.0
- 81.2.137.0/24AS213671Vision Fibre Media Ltd.RPKI Valid81.2.137.0
- 81.2.138.0/24AS213671Vision Fibre Media Ltd.RPKI Valid81.2.138.0
- 81.2.139.0/24AS213671Vision Fibre Media Ltd.RPKI Valid81.2.139.0
- 81.2.140.0/24AS213671Vision Fibre Media Ltd.RPKI Valid81.2.140.0
- 81.2.141.0/24AS213671Vision Fibre Media Ltd.RPKI Valid81.2.141.0
- 81.2.142.0/23AS198545FLEX NETWORK SARLRPKI Not found81.2.142.0
- 81.2.144.0/22AS208905Exelera Telecom LtdRPKI Valid81.2.144.0
- 81.2.148.0/24AS201042SD1-Telecom SRLRPKI Not found81.2.148.0
- 81.2.150.0/23AS198545FLEX NETWORK SARLRPKI Not found81.2.150.0
- 81.2.152.0/21AS48945OPEN FIBRE NETWORKS (WHOLESALE) LIMITEDRPKI Not found81.2.152.0
- 81.2.160.0/21AS48945OPEN FIBRE NETWORKS (WHOLESALE) LIMITEDRPKI Not found81.2.160.0
- 81.2.168.0/21AS48945OPEN FIBRE NETWORKS (WHOLESALE) LIMITEDRPKI Not found81.2.168.0
- 81.2.176.0/21AS48945OPEN FIBRE NETWORKS (WHOLESALE) LIMITEDRPKI Not found81.2.176.0
- 81.2.184.0/24AS208855MYWIFI TELEKOMUNIKASYON SANAYI TICARET LIMITED SIRKETIRPKI Valid81.2.184.0
- 81.2.187.0/24AS209784WIFISAX GmbHRPKI Valid81.2.187.0
- 81.2.188.0/23AS208905Exelera Telecom LtdRPKI Valid81.2.188.0
- 81.2.190.0/24AS205520XTB S.A.RPKI Not found81.2.190.0
- 81.2.191.0/24AS200736MEDIANET INVEST AERPKI Not found81.2.191.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.