BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
1.177.0.0/16
Announced exactly
- 1.177.0.0/16AS38091LG HelloVision Corp.RPKI Not found1.177.0.0
- Registry
- APNIC · South Korea · Jun 16, 2010
- Delegated block
- 1.176.0.0 – 1.177.255.255
Covering routes
No less-specific route covers it.
More-specific routes
- 1.177.0.0/21AS17577LG HelloVision Corp.RPKI Not found1.177.0.0
- 1.177.8.0/21AS17577LG HelloVision Corp.RPKI Not found1.177.8.0
- 1.177.16.0/21AS17577LG HelloVision Corp.RPKI Not found1.177.16.0
- 1.177.24.0/21AS17577LG HelloVision Corp.RPKI Not found1.177.24.0
- 1.177.32.0/21AS17577LG HelloVision Corp.RPKI Not found1.177.32.0
- 1.177.40.0/21AS17577LG HelloVision Corp.RPKI Not found1.177.40.0
- 1.177.48.0/21AS17577LG HelloVision Corp.RPKI Not found1.177.48.0
- 1.177.56.0/21AS17577LG HelloVision Corp.RPKI Not found1.177.56.0
- 1.177.64.0/22AS9845LG HelloVision Corp.RPKI Not found1.177.64.0
- 1.177.68.0/22AS9845LG HelloVision Corp.RPKI Not found1.177.68.0
- 1.177.72.0/22AS9845LG HelloVision Corp.RPKI Not found1.177.72.0
- 1.177.76.0/22AS9845LG HelloVision Corp.RPKI Not found1.177.76.0
- 1.177.80.0/22AS9845LG HelloVision Corp.RPKI Not found1.177.80.0
- 1.177.84.0/22AS9845LG HelloVision Corp.RPKI Not found1.177.84.0
- 1.177.88.0/22AS9845LG HelloVision Corp.RPKI Not found1.177.88.0
- 1.177.92.0/22AS9845LG HelloVision Corp.RPKI Not found1.177.92.0
- 1.177.96.0/22AS9845LG HelloVision Corp.RPKI Not found1.177.96.0
- 1.177.100.0/22AS9845LG HelloVision Corp.RPKI Not found1.177.100.0
- 1.177.104.0/22AS9845LG HelloVision Corp.RPKI Not found1.177.104.0
- 1.177.108.0/22AS9845LG HelloVision Corp.RPKI Not found1.177.108.0
- 1.177.112.0/22AS9845LG HelloVision Corp.RPKI Not found1.177.112.0
- 1.177.116.0/22AS9845LG HelloVision Corp.RPKI Not found1.177.116.0
- 1.177.116.0/24AS9845LG HelloVision Corp.RPKI Not found1.177.116.0
- 1.177.117.0/24AS9845LG HelloVision Corp.RPKI Not found1.177.117.0
- 1.177.118.0/24AS9845LG HelloVision Corp.RPKI Not found1.177.118.0
- 1.177.119.0/24AS9845LG HelloVision Corp.RPKI Not found1.177.119.0
- 1.177.120.0/22AS9845LG HelloVision Corp.RPKI Not found1.177.120.0
- 1.177.124.0/22AS9845LG HelloVision Corp.RPKI Not found1.177.124.0
- 1.177.128.0/22AS9697LG HelloVision Corp.RPKI Not found1.177.128.0
- 1.177.132.0/22AS9697LG HelloVision Corp.RPKI Not found1.177.132.0
- 1.177.136.0/22AS9697LG HelloVision Corp.RPKI Not found1.177.136.0
- 1.177.140.0/22AS9697LG HelloVision Corp.RPKI Not found1.177.140.0
- 1.177.144.0/22AS9845LG HelloVision Corp.RPKI Not found1.177.144.0
- 1.177.148.0/22AS9845LG HelloVision Corp.RPKI Not found1.177.148.0
- 1.177.152.0/22AS9697LG HelloVision Corp.RPKI Not found1.177.152.0
- 1.177.156.0/22AS9697LG HelloVision Corp.RPKI Not found1.177.156.0
- 1.177.160.0/22AS9697LG HelloVision Corp.RPKI Not found1.177.160.0
- 1.177.164.0/22AS9697LG HelloVision Corp.RPKI Not found1.177.164.0
- 1.177.164.0/24AS9697LG HelloVision Corp.RPKI Not found1.177.164.0
- 1.177.165.0/24AS9697LG HelloVision Corp.RPKI Not found1.177.165.0
- 1.177.166.0/24AS9697LG HelloVision Corp.RPKI Not found1.177.166.0
- 1.177.167.0/24AS9697LG HelloVision Corp.RPKI Not found1.177.167.0
- 1.177.168.0/22AS9697LG HelloVision Corp.RPKI Not found1.177.168.0
- 1.177.172.0/22AS9697LG HelloVision Corp.RPKI Not found1.177.172.0
- 1.177.176.0/22AS9697LG HelloVision Corp.RPKI Not found1.177.176.0
- 1.177.180.0/22AS9697LG HelloVision Corp.RPKI Not found1.177.180.0
- 1.177.184.0/22AS9697LG HelloVision Corp.RPKI Not found1.177.184.0
- 1.177.188.0/22AS9697LG HelloVision Corp.RPKI Not found1.177.188.0
- 1.177.192.0/22AS9697LG HelloVision Corp.RPKI Not found1.177.192.0
- 1.177.196.0/22AS9697LG HelloVision Corp.RPKI Not found1.177.196.0
- 1.177.200.0/22AS9697LG HelloVision Corp.RPKI Not found1.177.200.0
- 1.177.204.0/22AS9697LG HelloVision Corp.RPKI Not found1.177.204.0
- 1.177.208.0/22AS9697LG HelloVision Corp.RPKI Not found1.177.208.0
- 1.177.212.0/22AS9697LG HelloVision Corp.RPKI Not found1.177.212.0
- 1.177.216.0/22AS9697LG HelloVision Corp.RPKI Not found1.177.216.0
- 1.177.220.0/22AS9845LG HelloVision Corp.RPKI Not found1.177.220.0
- 1.177.224.0/22AS9845LG HelloVision Corp.RPKI Not found1.177.224.0
- 1.177.228.0/22AS9845LG HelloVision Corp.RPKI Not found1.177.228.0
- 1.177.232.0/22AS9845LG HelloVision Corp.RPKI Not found1.177.232.0
- 1.177.236.0/22AS9845LG HelloVision Corp.RPKI Not found1.177.236.0
- 1.177.240.0/22AS9845LG HelloVision Corp.RPKI Not found1.177.240.0
- 1.177.244.0/22AS9845LG HelloVision Corp.RPKI Not found1.177.244.0
- 1.177.248.0/22AS9845LG HelloVision Corp.RPKI Not found1.177.248.0
- 1.177.252.0/22AS9845LG HelloVision Corp.RPKI Not found1.177.252.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.