BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
181.96.0.0/12
Announced exactly
- 181.96.0.0/12AS7303Telecom Argentina S.A.RPKI Not found181.96.0.0
- Registry
- LACNIC · Argentina · Jun 21, 2012
- Delegated block
- 181.96.0.0 – 181.99.255.255
Covering routes
No less-specific route covers it.
More-specific routes
- 181.96.0.0/14AS7303Telecom Argentina S.A.RPKI Valid181.96.0.0
- 181.96.0.0/15AS7303Telecom Argentina S.A.RPKI Valid181.96.0.0
- 181.98.0.0/15AS7303Telecom Argentina S.A.RPKI Valid181.98.0.0
- 181.100.0.0/15AS7303Telecom Argentina S.A.RPKI Valid181.100.0.0
- 181.101.0.0/16AS7303Telecom Argentina S.A.RPKI Valid181.101.0.0
- 181.102.0.0/17AS7303Telecom Argentina S.A.RPKI Valid181.102.0.0
- 181.102.128.0/17AS7303Telecom Argentina S.A.RPKI Valid181.102.128.0
- 181.103.0.0/23AS27895Nucleo S.A.RPKI Valid181.103.0.0
- 181.103.2.0/23AS27895Nucleo S.A.RPKI Valid181.103.2.0
- 181.103.4.0/23AS27895Nucleo S.A.RPKI Valid181.103.4.0
- 181.103.6.0/24AS27895Nucleo S.A.RPKI Valid181.103.6.0
- 181.103.12.0/24AS27895Nucleo S.A.RPKI Valid181.103.12.0
- 181.103.13.0/24AS27895Nucleo S.A.RPKI Valid181.103.13.0
- 181.103.14.0/23AS27895Nucleo S.A.RPKI Valid181.103.14.0
- 181.103.64.0/22AS273854TELEMAS SOCIEDAD ANONIMARPKI Valid181.103.64.0
- 181.103.68.0/22AS273854TELEMAS SOCIEDAD ANONIMARPKI Valid181.103.68.0
- 181.103.72.0/22AS273854TELEMAS SOCIEDAD ANONIMARPKI Valid181.103.72.0
- 181.103.76.0/22AS273854TELEMAS SOCIEDAD ANONIMARPKI Valid181.103.76.0
- 181.103.80.0/24AS273854TELEMAS SOCIEDAD ANONIMARPKI Valid181.103.80.0
- 181.103.81.0/24AS273854TELEMAS SOCIEDAD ANONIMARPKI Valid181.103.81.0
- 181.103.82.0/23AS273854TELEMAS SOCIEDAD ANONIMARPKI Valid181.103.82.0
- 181.103.84.0/22AS273854TELEMAS SOCIEDAD ANONIMARPKI Valid181.103.84.0
- 181.103.85.0/24AS273854TELEMAS SOCIEDAD ANONIMARPKI Valid181.103.85.0
- 181.103.86.0/23AS273854TELEMAS SOCIEDAD ANONIMARPKI Valid181.103.86.0
- 181.103.88.0/24AS273854TELEMAS SOCIEDAD ANONIMARPKI Valid181.103.88.0
- 181.104.0.0/13AS7303Telecom Argentina S.A.RPKI Valid181.104.0.0
- 181.104.0.0/14AS7303Telecom Argentina S.A.RPKI Valid181.104.0.0
- 181.104.92.0/24AS52312TV MUSIC HOUSE JUJUYRPKI Valid181.104.92.0
- 181.105.221.0/24AS265686PROVIDERS S.A.RPKI Valid181.105.221.0
- 181.105.228.0/22AS264642TELESISTEMA S.R.L.RPKI Valid181.105.228.0
- 181.105.232.0/24AS274317LOPEZ TOBIAS FERNANDO DANIELRPKI Valid181.105.232.0
- 181.105.234.0/24AS265686PROVIDERS S.A.RPKI Valid181.105.234.0
- 181.108.0.0/14AS7303Telecom Argentina S.A.RPKI Valid181.108.0.0
- 181.111.167.0/24AS7303Telecom Argentina S.A.RPKI Valid181.111.167.0
- 181.111.168.0/24AS262229COOP DE LUZ Y FUERZA DE LIB.GRAL.SAN MARTIN LTDARPKI Valid181.111.168.0
- 181.111.171.0/24AS262229COOP DE LUZ Y FUERZA DE LIB.GRAL.SAN MARTIN LTDARPKI Valid181.111.171.0
- 181.111.206.0/24AS7303Telecom Argentina S.A.RPKI Valid181.111.206.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.