BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
190.216.0.0/18
Announced exactly
- 190.216.0.0/18AS3549Level 3 Parent, LLCRPKI Not found190.216.0.0
- Registry
- LACNIC · Argentina · Oct 4, 2007
- Delegated block
- 190.216.0.0 – 190.216.255.255
Covering routes
No less-specific route covers it.
More-specific routes
- 190.216.3.0/24AS3549Level 3 Parent, LLCRPKI Not found190.216.3.0
- 190.216.10.0/24AS3549Level 3 Parent, LLCRPKI Not found190.216.10.0
- 190.216.17.0/24AS3549Level 3 Parent, LLCRPKI Not found190.216.17.0
- 190.216.18.0/24AS20207Gigared S.A.RPKI Valid190.216.18.0
- 190.216.24.0/24AS20207Gigared S.A.RPKI Valid190.216.24.0
- 190.216.31.0/24AS3549Level 3 Parent, LLCRPKI Not found190.216.31.0
- 190.216.32.0/24AS262187Patagonia Green S.A.RPKI Valid190.216.32.0
- 190.216.33.0/24AS3549Level 3 Parent, LLCRPKI Not found190.216.33.0
- 190.216.36.0/24AS3549Level 3 Parent, LLCRPKI Not found190.216.36.0
- 190.216.39.0/24AS3549Level 3 Parent, LLCRPKI Not found190.216.39.0
- 190.216.42.0/24AS3549Level 3 Parent, LLCRPKI Not found190.216.42.0
- 190.216.43.0/24AS3549Level 3 Parent, LLCRPKI Not found190.216.43.0
- 190.216.52.0/24AS3549Level 3 Parent, LLCRPKI Not found190.216.52.0
- 190.216.56.0/24AS265758COOPERATIVA DE OBRAS Y SERVICIOS PUBLICOS DE DESPENADEROS LIMITADARPKI Valid190.216.56.0
- 190.216.57.0/24AS3549Level 3 Parent, LLCRPKI Not found190.216.57.0
- 190.216.58.0/24AS3549Level 3 Parent, LLCRPKI Not found190.216.58.0
- 190.216.60.0/24AS20207Gigared S.A.RPKI Valid190.216.60.0
- 190.216.61.0/24AS52444Pogliotti & Pogliotti Construcciones S.A.RPKI Valid190.216.61.0
- 190.216.62.0/24AS20207Gigared S.A.RPKI Valid190.216.62.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.