BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
152.231.64.0/18
Announced exactly
- 152.231.64.0/18AS27651ENTEL CHILE S.A.RPKI Valid152.231.64.0
- Registry
- LACNIC · Chile · Jun 13, 2014
- Delegated block
- 152.231.64.0 – 152.231.127.255
Covering routes
No less-specific route covers it.
More-specific routes
- 152.231.64.0/24AS27651ENTEL CHILE S.A.RPKI Valid152.231.64.0
- 152.231.65.0/24AS27651ENTEL CHILE S.A.RPKI Valid152.231.65.0
- 152.231.66.0/24AS27651ENTEL CHILE S.A.RPKI Valid152.231.66.0
- 152.231.67.0/24AS27651ENTEL CHILE S.A.RPKI Valid152.231.67.0
- 152.231.68.0/24AS27651ENTEL CHILE S.A.RPKI Valid152.231.68.0
- 152.231.69.0/24AS27651ENTEL CHILE S.A.RPKI Valid152.231.69.0
- 152.231.70.0/24AS27651ENTEL CHILE S.A.RPKI Valid152.231.70.0
- 152.231.71.0/24AS27651ENTEL CHILE S.A.RPKI Valid152.231.71.0
- 152.231.72.0/24AS27651ENTEL CHILE S.A.RPKI Valid152.231.72.0
- 152.231.73.0/24AS27651ENTEL CHILE S.A.RPKI Valid152.231.73.0
- 152.231.74.0/24AS27651ENTEL CHILE S.A.RPKI Valid152.231.74.0
- 152.231.75.0/24AS27651ENTEL CHILE S.A.RPKI Valid152.231.75.0
- 152.231.76.0/24AS27651ENTEL CHILE S.A.RPKI Valid152.231.76.0
- 152.231.77.0/24AS27651ENTEL CHILE S.A.RPKI Valid152.231.77.0
- 152.231.78.0/24AS27651ENTEL CHILE S.A.RPKI Valid152.231.78.0
- 152.231.79.0/24AS27651ENTEL CHILE S.A.RPKI Valid152.231.79.0
- 152.231.80.0/24AS27651ENTEL CHILE S.A.RPKI Valid152.231.80.0
- 152.231.81.0/24AS27651ENTEL CHILE S.A.RPKI Valid152.231.81.0
- 152.231.82.0/24AS27651ENTEL CHILE S.A.RPKI Valid152.231.82.0
- 152.231.83.0/24AS27651ENTEL CHILE S.A.RPKI Valid152.231.83.0
- 152.231.84.0/24AS27651ENTEL CHILE S.A.RPKI Valid152.231.84.0
- 152.231.85.0/24AS27651ENTEL CHILE S.A.RPKI Valid152.231.85.0
- 152.231.86.0/24AS27651ENTEL CHILE S.A.RPKI Valid152.231.86.0
- 152.231.87.0/24AS27651ENTEL CHILE S.A.RPKI Valid152.231.87.0
- 152.231.88.0/24AS27651ENTEL CHILE S.A.RPKI Valid152.231.88.0
- 152.231.89.0/24AS27651ENTEL CHILE S.A.RPKI Valid152.231.89.0
- 152.231.90.0/24AS27651ENTEL CHILE S.A.RPKI Valid152.231.90.0
- 152.231.91.0/24AS27651ENTEL CHILE S.A.RPKI Valid152.231.91.0
- 152.231.92.0/24AS27651ENTEL CHILE S.A.RPKI Valid152.231.92.0
- 152.231.93.0/24AS27651ENTEL CHILE S.A.RPKI Valid152.231.93.0
- 152.231.94.0/24AS27651ENTEL CHILE S.A.RPKI Valid152.231.94.0
- 152.231.95.0/24AS27651ENTEL CHILE S.A.RPKI Valid152.231.95.0
- 152.231.102.0/23AS27651ENTEL CHILE S.A.RPKI Valid152.231.102.0
- 152.231.104.0/24AS27651ENTEL CHILE S.A.RPKI Valid152.231.104.0
- 152.231.105.0/24AS27651ENTEL CHILE S.A.RPKI Valid152.231.105.0
- 152.231.106.0/24AS27651ENTEL CHILE S.A.RPKI Valid152.231.106.0
- 152.231.107.0/24AS27651ENTEL CHILE S.A.RPKI Valid152.231.107.0
- 152.231.108.0/24AS27651ENTEL CHILE S.A.RPKI Valid152.231.108.0
- 152.231.109.0/24AS27651ENTEL CHILE S.A.RPKI Valid152.231.109.0
- 152.231.110.0/24AS27986ENTEL CHILE S.A.RPKI Valid152.231.110.0
- 152.231.111.0/24AS27986ENTEL CHILE S.A.RPKI Valid152.231.111.0
- 152.231.112.0/24AS27651ENTEL CHILE S.A.RPKI Valid152.231.112.0
- 152.231.113.0/24AS27651ENTEL CHILE S.A.RPKI Valid152.231.113.0
- 152.231.114.0/24AS27651ENTEL CHILE S.A.RPKI Valid152.231.114.0
- 152.231.115.0/24AS27651ENTEL CHILE S.A.RPKI Valid152.231.115.0
- 152.231.116.0/24AS27651ENTEL CHILE S.A.RPKI Valid152.231.116.0
- 152.231.117.0/24AS27651ENTEL CHILE S.A.RPKI Valid152.231.117.0
- 152.231.118.0/24AS27651ENTEL CHILE S.A.RPKI Valid152.231.118.0
- 152.231.120.0/24AS27651ENTEL CHILE S.A.RPKI Valid152.231.120.0
- 152.231.121.0/24AS27651ENTEL CHILE S.A.RPKI Valid152.231.121.0
- 152.231.122.0/24AS27651ENTEL CHILE S.A.RPKI Valid152.231.122.0
- 152.231.123.0/24AS27651ENTEL CHILE S.A.RPKI Valid152.231.123.0
- 152.231.125.0/24AS27651ENTEL CHILE S.A.RPKI Valid152.231.125.0
- 152.231.126.0/24AS27651ENTEL CHILE S.A.RPKI Valid152.231.126.0
- 152.231.127.0/24AS27651ENTEL CHILE S.A.RPKI Valid152.231.127.0
On the internet, routes are announced as prefixes: an autonomous system tells its neighbours via BGP that it can deliver traffic for, say, 2.48.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.