BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
186.118.0.0/16
Announced exactly
- 186.118.0.0/16AS3816COLOMBIA TELECOMUNICACIONES S.A. ESP BICRPKI Valid186.118.0.0
- Registry
- LACNIC · Colombia · Mar 25, 2011
- Delegated block
- 186.116.0.0 – 186.119.255.255
Covering routes
No less-specific route covers it.
More-specific routes
- 186.118.0.0/19AS3816COLOMBIA TELECOMUNICACIONES S.A. ESP BICRPKI Valid186.118.0.0
- 186.118.32.0/19AS3816COLOMBIA TELECOMUNICACIONES S.A. ESP BICRPKI Valid186.118.32.0
- 186.118.64.0/19AS3816COLOMBIA TELECOMUNICACIONES S.A. ESP BICRPKI Valid186.118.64.0
- 186.118.100.0/22AS3816COLOMBIA TELECOMUNICACIONES S.A. ESP BICRPKI Valid186.118.100.0
- 186.118.120.0/22AS3816COLOMBIA TELECOMUNICACIONES S.A. ESP BICRPKI Valid186.118.120.0
- 186.118.124.0/22AS3816COLOMBIA TELECOMUNICACIONES S.A. ESP BICRPKI Valid186.118.124.0
- 186.118.128.0/22AS3816COLOMBIA TELECOMUNICACIONES S.A. ESP BICRPKI Valid186.118.128.0
- 186.118.132.0/22AS3816COLOMBIA TELECOMUNICACIONES S.A. ESP BICRPKI Valid186.118.132.0
- 186.118.136.0/22AS3816COLOMBIA TELECOMUNICACIONES S.A. ESP BICRPKI Valid186.118.136.0
- 186.118.140.0/22AS3816COLOMBIA TELECOMUNICACIONES S.A. ESP BICRPKI Valid186.118.140.0
- 186.118.144.0/22AS3816COLOMBIA TELECOMUNICACIONES S.A. ESP BICRPKI Valid186.118.144.0
- 186.118.148.0/22AS3816COLOMBIA TELECOMUNICACIONES S.A. ESP BICRPKI Valid186.118.148.0
- 186.118.152.0/22AS3816COLOMBIA TELECOMUNICACIONES S.A. ESP BICRPKI Valid186.118.152.0
- 186.118.156.0/22AS3816COLOMBIA TELECOMUNICACIONES S.A. ESP BICRPKI Valid186.118.156.0
- 186.118.160.0/22AS3816COLOMBIA TELECOMUNICACIONES S.A. ESP BICRPKI Valid186.118.160.0
- 186.118.164.0/22AS3816COLOMBIA TELECOMUNICACIONES S.A. ESP BICRPKI Valid186.118.164.0
- 186.118.168.0/22AS3816COLOMBIA TELECOMUNICACIONES S.A. ESP BICRPKI Valid186.118.168.0
- 186.118.172.0/22AS3816COLOMBIA TELECOMUNICACIONES S.A. ESP BICRPKI Valid186.118.172.0
- 186.118.176.0/22AS3816COLOMBIA TELECOMUNICACIONES S.A. ESP BICRPKI Valid186.118.176.0
- 186.118.180.0/22AS3816COLOMBIA TELECOMUNICACIONES S.A. ESP BICRPKI Valid186.118.180.0
- 186.118.184.0/24AS3816COLOMBIA TELECOMUNICACIONES S.A. ESP BICRPKI Valid186.118.184.0
- 186.118.185.0/24AS3816COLOMBIA TELECOMUNICACIONES S.A. ESP BICRPKI Valid186.118.185.0
- 186.118.186.0/24AS262182TELEFONICA GLOBAL SOLUTIONS PERU S.A.C.RPKI Valid186.118.186.0
- 186.118.187.0/24AS262182TELEFONICA GLOBAL SOLUTIONS PERU S.A.C.RPKI Valid186.118.187.0
- 186.118.188.0/22AS3816COLOMBIA TELECOMUNICACIONES S.A. ESP BICRPKI Valid186.118.188.0
- 186.118.192.0/20AS3816COLOMBIA TELECOMUNICACIONES S.A. ESP BICRPKI Valid186.118.192.0
- 186.118.216.0/21AS3816COLOMBIA TELECOMUNICACIONES S.A. ESP BICRPKI Valid186.118.216.0
- 186.118.224.0/19AS3816COLOMBIA TELECOMUNICACIONES S.A. ESP BICRPKI Valid186.118.224.0
On the internet, routes are announced as prefixes: an autonomous system tells its neighbours via BGP that it can deliver traffic for, say, 2.48.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.