BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
181.188.192.0/18
Announced exactly
- 181.188.192.0/18AS19114Otecel S.A.RPKI Valid181.188.192.0
- Registry
- LACNIC · Ecuador · Nov 5, 2013
- Delegated block
- 181.188.192.0 – 181.188.255.255
Covering routes
No less-specific route covers it.
More-specific routes
- 181.188.192.0/20AS19114Otecel S.A.RPKI Valid181.188.192.0
- 181.188.192.0/24AS19114Otecel S.A.RPKI Valid181.188.192.0
- 181.188.194.0/24AS19114Otecel S.A.RPKI Valid181.188.194.0
- 181.188.200.0/24AS7315Otecel S.A.RPKI Valid181.188.200.0
- 181.188.201.0/24AS7315Otecel S.A.RPKI Valid181.188.201.0
- 181.188.202.0/24AS52468UFINET PANAMA S.A.RPKI Valid181.188.202.0
- 181.188.203.0/24AS52468UFINET PANAMA S.A.RPKI Valid181.188.203.0
- 181.188.212.0/24AS52331CORPORACION FINANCIERA NACIONALRPKI Valid181.188.212.0
- 181.188.215.0/24AS52468UFINET PANAMA S.A.RPKI Valid181.188.215.0
- 181.188.216.0/24AS52468UFINET PANAMA S.A.RPKI Valid181.188.216.0
- 181.188.224.0/24AS19114Otecel S.A.RPKI Valid181.188.224.0
- 181.188.225.0/24AS273140TELECOMUNICACIONES DEL ORIENTE TELECORPVP S.A.S.RPKI Valid181.188.225.0
- 181.188.226.0/24AS19114Otecel S.A.RPKI Valid181.188.226.0
- 181.188.228.0/24AS272094OPTILINK CIA LTDARPKI Valid181.188.228.0
- 181.188.232.0/24AS19114Otecel S.A.RPKI Valid181.188.232.0
- 181.188.235.0/24AS28097FarcomedRPKI Valid181.188.235.0
- 181.188.237.0/24AS271936SERVICIOS DE TELECOMUNICACIONES ATVCABLE CIA. LTDA.RPKI Valid181.188.237.0
- 181.188.240.0/24AS19114Otecel S.A.RPKI Valid181.188.240.0
- 181.188.242.0/24AS19114Otecel S.A.RPKI Valid181.188.242.0
- 181.188.243.0/24AS19114Otecel S.A.RPKI Valid181.188.243.0
- 181.188.244.0/24AS19114Otecel S.A.RPKI Valid181.188.244.0
- 181.188.245.0/24AS19114Otecel S.A.RPKI Valid181.188.245.0
- 181.188.248.0/24AS19114Otecel S.A.RPKI Valid181.188.248.0
- 181.188.252.0/24AS272097TELEVISION POR CABLE COCATEVE S.A. (GRUPO COCAVISION)RPKI Valid181.188.252.0
On the internet, routes are announced as prefixes: an autonomous system tells its neighbours via BGP that it can deliver traffic for, say, 62.103.0.0/16. 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.