BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
179.40.0.0/15
Announced exactly
- 179.40.0.0/15AS22927Telefonica de ArgentinaRPKI Valid179.40.0.0
- Registry
- LACNIC · Argentina · Jun 20, 2013
- Delegated block
- 179.40.0.0 – 179.41.255.255
Covering routes
No less-specific route covers it.
More-specific routes
- 179.40.0.0/17AS22927Telefonica de ArgentinaRPKI Valid179.40.0.0
- 179.40.8.0/22AS20207Gigared S.A.RPKI Valid179.40.8.0
- 179.40.11.0/24AS20207Gigared S.A.RPKI Valid179.40.11.0
- 179.40.24.0/24AS22927Telefonica de ArgentinaRPKI Valid179.40.24.0
- 179.40.42.0/24AS52477ApInterRPKI Valid179.40.42.0
- 179.40.45.0/24AS272945UV MUNDO DIGITAL SRLRPKI Valid179.40.45.0
- 179.40.50.0/24AS27983Red Intercable Digital S.A.RPKI Valid179.40.50.0
- 179.40.69.0/24AS52444Pogliotti & Pogliotti Construcciones S.A.RPKI Valid179.40.69.0
- 179.40.70.0/24AS52444Pogliotti & Pogliotti Construcciones S.A.RPKI Valid179.40.70.0
- 179.40.100.0/22AS27927Coop. Popular de Elec., Obras y Servicios Pub. de Santa Rosa LTDARPKI Valid179.40.100.0
- 179.40.100.0/24AS27927Coop. Popular de Elec., Obras y Servicios Pub. de Santa Rosa LTDARPKI Valid179.40.100.0
- 179.40.101.0/24AS27927Coop. Popular de Elec., Obras y Servicios Pub. de Santa Rosa LTDARPKI Valid179.40.101.0
- 179.40.102.0/24AS27927Coop. Popular de Elec., Obras y Servicios Pub. de Santa Rosa LTDARPKI Valid179.40.102.0
- 179.40.103.0/24AS27927Coop. Popular de Elec., Obras y Servicios Pub. de Santa Rosa LTDARPKI Valid179.40.103.0
- 179.40.104.0/24AS27927Coop. Popular de Elec., Obras y Servicios Pub. de Santa Rosa LTDARPKI Valid179.40.104.0
- 179.40.105.0/24AS27927Coop. Popular de Elec., Obras y Servicios Pub. de Santa Rosa LTDARPKI Valid179.40.105.0
- 179.40.106.0/24AS27927Coop. Popular de Elec., Obras y Servicios Pub. de Santa Rosa LTDARPKI Valid179.40.106.0
- 179.40.109.0/24AS270022FULLNET SRLRPKI Valid179.40.109.0
On the internet, routes are announced as prefixes: an autonomous system tells its neighbours via BGP that it can deliver traffic for, say, 193.166.0.0/15. 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.