BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
Examples:
59.152.128.0/18
One collector's view (APNIC). A route filtered before it reaches that collector is not listed.
Announced exactly
- 59.152.128.0/18AS38091LG HelloVision Corp.RPKI Not found59.152.128.0
- Registry
- APNIC · South Korea · Oct 18, 2006
- Delegated block
- 59.152.128.0 – 59.152.191.255
Covering routes
0
No less-specific route covers it.
More-specific routes
64 more-specifics from 1 origin AS(es)
- 59.152.128.0/21AS38120LG HelloVision Corp.RPKI Not found59.152.128.0
- 59.152.128.0/24AS38120LG HelloVision Corp.RPKI Not found59.152.128.0
- 59.152.129.0/24AS38120LG HelloVision Corp.RPKI Not found59.152.129.0
- 59.152.130.0/24AS38120LG HelloVision Corp.RPKI Not found59.152.130.0
- 59.152.131.0/24AS38120LG HelloVision Corp.RPKI Not found59.152.131.0
- 59.152.132.0/24AS38120LG HelloVision Corp.RPKI Not found59.152.132.0
- 59.152.133.0/24AS38120LG HelloVision Corp.RPKI Not found59.152.133.0
- 59.152.134.0/24AS38120LG HelloVision Corp.RPKI Not found59.152.134.0
- 59.152.135.0/24AS38120LG HelloVision Corp.RPKI Not found59.152.135.0
- 59.152.136.0/24AS38120LG HelloVision Corp.RPKI Not found59.152.136.0
- 59.152.137.0/24AS38120LG HelloVision Corp.RPKI Not found59.152.137.0
- 59.152.138.0/24AS38120LG HelloVision Corp.RPKI Not found59.152.138.0
- 59.152.139.0/24AS38120LG HelloVision Corp.RPKI Not found59.152.139.0
- 59.152.140.0/24AS38120LG HelloVision Corp.RPKI Not found59.152.140.0
- 59.152.141.0/24AS38120LG HelloVision Corp.RPKI Not found59.152.141.0
- 59.152.142.0/24AS38120LG HelloVision Corp.RPKI Not found59.152.142.0
- 59.152.143.0/24AS38120LG HelloVision Corp.RPKI Not found59.152.143.0
- 59.152.144.0/24AS38120LG HelloVision Corp.RPKI Not found59.152.144.0
- 59.152.145.0/24AS38120LG HelloVision Corp.RPKI Not found59.152.145.0
- 59.152.146.0/24AS38120LG HelloVision Corp.RPKI Not found59.152.146.0
- 59.152.147.0/24AS38120LG HelloVision Corp.RPKI Not found59.152.147.0
- 59.152.148.0/24AS38120LG HelloVision Corp.RPKI Not found59.152.148.0
- 59.152.149.0/24AS38120LG HelloVision Corp.RPKI Not found59.152.149.0
- 59.152.150.0/24AS38120LG HelloVision Corp.RPKI Not found59.152.150.0
- 59.152.151.0/24AS38120LG HelloVision Corp.RPKI Not found59.152.151.0
- 59.152.152.0/24AS38120LG HelloVision Corp.RPKI Not found59.152.152.0
- 59.152.153.0/24AS38120LG HelloVision Corp.RPKI Not found59.152.153.0
- 59.152.154.0/24AS38120LG HelloVision Corp.RPKI Not found59.152.154.0
- 59.152.155.0/24AS38120LG HelloVision Corp.RPKI Not found59.152.155.0
- 59.152.156.0/24AS38120LG HelloVision Corp.RPKI Not found59.152.156.0
- 59.152.157.0/24AS38120LG HelloVision Corp.RPKI Not found59.152.157.0
- 59.152.158.0/24AS38120LG HelloVision Corp.RPKI Not found59.152.158.0
- 59.152.159.0/24AS38120LG HelloVision Corp.RPKI Not found59.152.159.0
- 59.152.160.0/21AS38120LG HelloVision Corp.RPKI Not found59.152.160.0
- 59.152.160.0/24AS38120LG HelloVision Corp.RPKI Not found59.152.160.0
- 59.152.161.0/24AS38120LG HelloVision Corp.RPKI Not found59.152.161.0
- 59.152.162.0/24AS38120LG HelloVision Corp.RPKI Not found59.152.162.0
- 59.152.163.0/24AS38120LG HelloVision Corp.RPKI Not found59.152.163.0
- 59.152.164.0/24AS38120LG HelloVision Corp.RPKI Not found59.152.164.0
- 59.152.165.0/24AS38120LG HelloVision Corp.RPKI Not found59.152.165.0
- 59.152.166.0/24AS38120LG HelloVision Corp.RPKI Not found59.152.166.0
- 59.152.167.0/24AS38120LG HelloVision Corp.RPKI Not found59.152.167.0
- 59.152.168.0/21AS38120LG HelloVision Corp.RPKI Not found59.152.168.0
- 59.152.168.0/24AS38120LG HelloVision Corp.RPKI Not found59.152.168.0
- 59.152.169.0/24AS38120LG HelloVision Corp.RPKI Not found59.152.169.0
- 59.152.170.0/24AS38120LG HelloVision Corp.RPKI Not found59.152.170.0
- 59.152.171.0/24AS38120LG HelloVision Corp.RPKI Not found59.152.171.0
- 59.152.172.0/24AS38120LG HelloVision Corp.RPKI Not found59.152.172.0
- 59.152.173.0/24AS38120LG HelloVision Corp.RPKI Not found59.152.173.0
- 59.152.174.0/24AS38120LG HelloVision Corp.RPKI Not found59.152.174.0
- 59.152.175.0/24AS38120LG HelloVision Corp.RPKI Not found59.152.175.0
- 59.152.176.0/24AS38120LG HelloVision Corp.RPKI Not found59.152.176.0
- 59.152.177.0/24AS38120LG HelloVision Corp.RPKI Not found59.152.177.0
- 59.152.178.0/24AS38120LG HelloVision Corp.RPKI Not found59.152.178.0
- 59.152.179.0/24AS38120LG HelloVision Corp.RPKI Not found59.152.179.0
- 59.152.180.0/24AS38120LG HelloVision Corp.RPKI Not found59.152.180.0
- 59.152.181.0/24AS38120LG HelloVision Corp.RPKI Not found59.152.181.0
- 59.152.182.0/24AS38120LG HelloVision Corp.RPKI Not found59.152.182.0
- 59.152.183.0/24AS38120LG HelloVision Corp.RPKI Not found59.152.183.0
- 59.152.184.0/21AS38120LG HelloVision Corp.RPKI Not found59.152.184.0
- 59.152.184.0/24AS38120LG HelloVision Corp.RPKI Not found59.152.184.0
- 59.152.189.0/24AS38120LG HelloVision Corp.RPKI Not found59.152.189.0
- 59.152.190.0/24AS38120LG HelloVision Corp.RPKI Not found59.152.190.0
- 59.152.191.0/24AS38120LG HelloVision Corp.RPKI Not found59.152.191.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.