BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
181.80.0.0/12
Announced exactly
- 181.80.0.0/12AS7303Telecom Argentina S.A.RPKI Not found181.80.0.0
- Registry
- LACNIC · Argentina · Sep 19, 2011
- Delegated block
- 181.80.0.0 – 181.83.255.255
Covering routes
No less-specific route covers it.
More-specific routes
- 181.80.0.0/15AS7303Telecom Argentina S.A.RPKI Valid181.80.0.0
- 181.80.9.0/24AS264791COOPERATIVA DE PROVISION DE ELECTRICIDAD Y OTROS SS PUBLICOS CONSUMO Y VIVIENDA DE LEZAMA LTDARPKI Valid181.80.9.0
- 181.80.10.0/24AS264791COOPERATIVA DE PROVISION DE ELECTRICIDAD Y OTROS SS PUBLICOS CONSUMO Y VIVIENDA DE LEZAMA LTDARPKI Valid181.80.10.0
- 181.80.38.0/24AS265842NARDANONE PEDRO FEDERICO SALVADORRPKI Valid181.80.38.0
- 181.81.246.0/24AS265630COMISSO DANTE ANIBALRPKI Valid181.81.246.0
- 181.81.247.0/24AS265630COMISSO DANTE ANIBALRPKI Valid181.81.247.0
- 181.81.248.0/22AS264715COOPERATIVA ELECTRICA LIMITADA DE RUFINORPKI Valid181.81.248.0
- 181.82.0.0/15AS7303Telecom Argentina S.A.RPKI Valid181.82.0.0
- 181.84.0.0/15AS7303Telecom Argentina S.A.RPKI Not found181.84.0.0
- 181.85.155.0/24AS52440Universidad de La PuntaRPKI Valid181.85.155.0
- 181.85.208.0/24AS27895Nucleo S.A.RPKI Valid181.85.208.0
- 181.85.209.0/24AS27895Nucleo S.A.RPKI Valid181.85.209.0
- 181.85.210.0/24AS27895Nucleo S.A.RPKI Valid181.85.210.0
- 181.85.211.0/24AS27895Nucleo S.A.RPKI Valid181.85.211.0
- 181.85.212.0/23AS27895Nucleo S.A.RPKI Valid181.85.212.0
- 181.86.0.0/15AS7303Telecom Argentina S.A.RPKI Valid181.86.0.0
- 181.88.0.0/15AS7303Telecom Argentina S.A.RPKI Valid181.88.0.0
- 181.90.0.0/15AS7303Telecom Argentina S.A.RPKI Not found181.90.0.0
- 181.91.84.0/23AS27895Nucleo S.A.RPKI Valid181.91.84.0
- 181.91.86.0/23AS27895Nucleo S.A.RPKI Valid181.91.86.0
- 181.92.0.0/15AS7303Telecom Argentina S.A.RPKI Valid181.92.0.0
- 181.93.244.0/24AS265630COMISSO DANTE ANIBALRPKI Valid181.93.244.0
- 181.93.248.0/24AS265630COMISSO DANTE ANIBALRPKI Valid181.93.248.0
- 181.94.0.0/15AS7303Telecom Argentina S.A.RPKI Not found181.94.0.0
- 181.94.100.0/24AS7303Telecom Argentina S.A.RPKI Valid181.94.100.0
- 181.94.192.0/22AS265630COMISSO DANTE ANIBALRPKI Valid181.94.192.0
- 181.94.197.0/24AS27895Nucleo S.A.RPKI Valid181.94.197.0
- 181.94.208.0/23AS27895Nucleo S.A.RPKI Valid181.94.208.0
- 181.94.210.0/24AS27895Nucleo S.A.RPKI Valid181.94.210.0
- 181.94.212.0/22AS27895Nucleo S.A.RPKI Valid181.94.212.0
- 181.94.220.0/22AS27895Nucleo S.A.RPKI Valid181.94.220.0
- 181.94.224.0/23AS27895Nucleo S.A.RPKI Valid181.94.224.0
- 181.94.226.0/23AS27895Nucleo S.A.RPKI Valid181.94.226.0
- 181.94.228.0/24AS27895Nucleo S.A.RPKI Valid181.94.228.0
- 181.94.229.0/24AS27895Nucleo S.A.RPKI Valid181.94.229.0
- 181.94.230.0/24AS27895Nucleo S.A.RPKI Valid181.94.230.0
- 181.94.231.0/24AS27895Nucleo S.A.RPKI Valid181.94.231.0
- 181.94.232.0/23AS27895Nucleo S.A.RPKI Valid181.94.232.0
- 181.94.234.0/23AS27895Nucleo S.A.RPKI Valid181.94.234.0
- 181.94.236.0/23AS27895Nucleo S.A.RPKI Valid181.94.236.0
- 181.94.238.0/24AS27895Nucleo S.A.RPKI Valid181.94.238.0
- 181.94.241.0/24AS27895Nucleo S.A.RPKI Valid181.94.241.0
- 181.94.242.0/23AS27895Nucleo S.A.RPKI Valid181.94.242.0
- 181.94.244.0/22AS27895Nucleo S.A.RPKI Valid181.94.244.0
- 181.94.248.0/23AS27895Nucleo S.A.RPKI Valid181.94.248.0
- 181.94.250.0/24AS27895Nucleo S.A.RPKI Valid181.94.250.0
- 181.94.252.0/24AS265686PROVIDERS S.A.RPKI Valid181.94.252.0
- 181.94.253.0/24AS265686PROVIDERS S.A.RPKI Valid181.94.253.0
- 181.94.254.0/24AS265686PROVIDERS S.A.RPKI Valid181.94.254.0
- 181.94.255.0/24AS265686PROVIDERS S.A.RPKI Valid181.94.255.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.