BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
Examples:
42.82.0.0/16
One collector's view (APNIC). A route filtered before it reaches that collector is not listed.
Announced exactly
- 42.82.0.0/16AS38091LG HelloVision Corp.RPKI Not found42.82.0.0
- Registry
- APNIC · South Korea · Feb 3, 2011
- Delegated block
- 42.82.0.0 – 42.82.255.255
Covering routes
0
No less-specific route covers it.
More-specific routes
76 more-specifics from 5 origin AS(es)
- 42.82.0.0/21AS9697LG HelloVision Corp.RPKI Not found42.82.0.0
- 42.82.8.0/21AS9697LG HelloVision Corp.RPKI Not found42.82.8.0
- 42.82.16.0/21AS9697LG HelloVision Corp.RPKI Not found42.82.16.0
- 42.82.24.0/21AS9697LG HelloVision Corp.RPKI Not found42.82.24.0
- 42.82.32.0/24AS9770LG HelloVision Corp.RPKI Not found42.82.32.0
- 42.82.33.0/24AS9770LG HelloVision Corp.RPKI Not found42.82.33.0
- 42.82.34.0/24AS9770LG HelloVision Corp.RPKI Not found42.82.34.0
- 42.82.35.0/24AS9770LG HelloVision Corp.RPKI Not found42.82.35.0
- 42.82.36.0/24AS9770LG HelloVision Corp.RPKI Not found42.82.36.0
- 42.82.37.0/24AS9770LG HelloVision Corp.RPKI Not found42.82.37.0
- 42.82.38.0/24AS9770LG HelloVision Corp.RPKI Not found42.82.38.0
- 42.82.39.0/24AS9770LG HelloVision Corp.RPKI Not found42.82.39.0
- 42.82.40.0/24AS9770LG HelloVision Corp.RPKI Not found42.82.40.0
- 42.82.41.0/24AS9770LG HelloVision Corp.RPKI Not found42.82.41.0
- 42.82.42.0/24AS9770LG HelloVision Corp.RPKI Not found42.82.42.0
- 42.82.43.0/24AS9770LG HelloVision Corp.RPKI Not found42.82.43.0
- 42.82.44.0/24AS9770LG HelloVision Corp.RPKI Not found42.82.44.0
- 42.82.45.0/24AS9770LG HelloVision Corp.RPKI Not found42.82.45.0
- 42.82.46.0/24AS9770LG HelloVision Corp.RPKI Not found42.82.46.0
- 42.82.47.0/24AS9770LG HelloVision Corp.RPKI Not found42.82.47.0
- 42.82.48.0/20AS9697LG HelloVision Corp.RPKI Not found42.82.48.0
- 42.82.64.0/22AS9845LG HelloVision Corp.RPKI Not found42.82.64.0
- 42.82.68.0/22AS9845LG HelloVision Corp.RPKI Not found42.82.68.0
- 42.82.72.0/22AS9845LG HelloVision Corp.RPKI Not found42.82.72.0
- 42.82.76.0/22AS9845LG HelloVision Corp.RPKI Not found42.82.76.0
- 42.82.80.0/22AS9845LG HelloVision Corp.RPKI Not found42.82.80.0
- 42.82.84.0/22AS9845LG HelloVision Corp.RPKI Not found42.82.84.0
- 42.82.88.0/22AS9845LG HelloVision Corp.RPKI Not found42.82.88.0
- 42.82.92.0/22AS9845LG HelloVision Corp.RPKI Not found42.82.92.0
- 42.82.96.0/22AS9845LG HelloVision Corp.RPKI Not found42.82.96.0
- 42.82.100.0/22AS9845LG HelloVision Corp.RPKI Not found42.82.100.0
- 42.82.104.0/22AS9845LG HelloVision Corp.RPKI Not found42.82.104.0
- 42.82.108.0/22AS9845LG HelloVision Corp.RPKI Not found42.82.108.0
- 42.82.112.0/22AS9697LG HelloVision Corp.RPKI Not found42.82.112.0
- 42.82.116.0/22AS9845LG HelloVision Corp.RPKI Not found42.82.116.0
- 42.82.120.0/22AS9845LG HelloVision Corp.RPKI Not found42.82.120.0
- 42.82.124.0/22AS9845LG HelloVision Corp.RPKI Not found42.82.124.0
- 42.82.128.0/22AS38669LG HelloVision Corp.RPKI Not found42.82.128.0
- 42.82.132.0/22AS38669LG HelloVision Corp.RPKI Not found42.82.132.0
- 42.82.133.0/24AS38669LG HelloVision Corp.RPKI Not found42.82.133.0
- 42.82.136.0/22AS38669LG HelloVision Corp.RPKI Not found42.82.136.0
- 42.82.140.0/22AS38669LG HelloVision Corp.RPKI Not found42.82.140.0
- 42.82.144.0/22AS38669LG HelloVision Corp.RPKI Not found42.82.144.0
- 42.82.148.0/22AS38669LG HelloVision Corp.RPKI Not found42.82.148.0
- 42.82.152.0/22AS38669LG HelloVision Corp.RPKI Not found42.82.152.0
- 42.82.156.0/22AS38669LG HelloVision Corp.RPKI Not found42.82.156.0
- 42.82.160.0/20AS9698LG HelloVision Corp.RPKI Not found42.82.160.0
- 42.82.167.0/24AS9698LG HelloVision Corp.RPKI Not found42.82.167.0
- 42.82.176.0/24AS9770LG HelloVision Corp.RPKI Not found42.82.176.0
- 42.82.177.0/24AS9770LG HelloVision Corp.RPKI Not found42.82.177.0
- 42.82.178.0/24AS9770LG HelloVision Corp.RPKI Not found42.82.178.0
- 42.82.179.0/24AS9770LG HelloVision Corp.RPKI Not found42.82.179.0
- 42.82.180.0/24AS9770LG HelloVision Corp.RPKI Not found42.82.180.0
- 42.82.181.0/24AS9770LG HelloVision Corp.RPKI Not found42.82.181.0
- 42.82.182.0/24AS9770LG HelloVision Corp.RPKI Not found42.82.182.0
- 42.82.183.0/24AS9770LG HelloVision Corp.RPKI Not found42.82.183.0
- 42.82.184.0/24AS9770LG HelloVision Corp.RPKI Not found42.82.184.0
- 42.82.185.0/24AS9770LG HelloVision Corp.RPKI Not found42.82.185.0
- 42.82.186.0/24AS9770LG HelloVision Corp.RPKI Not found42.82.186.0
- 42.82.187.0/24AS9770LG HelloVision Corp.RPKI Not found42.82.187.0
- 42.82.188.0/24AS9770LG HelloVision Corp.RPKI Not found42.82.188.0
- 42.82.189.0/24AS9770LG HelloVision Corp.RPKI Not found42.82.189.0
- 42.82.190.0/24AS9770LG HelloVision Corp.RPKI Not found42.82.190.0
- 42.82.191.0/24AS9770LG HelloVision Corp.RPKI Not found42.82.191.0
- 42.82.192.0/22AS9770LG HelloVision Corp.RPKI Not found42.82.192.0
- 42.82.196.0/22AS9770LG HelloVision Corp.RPKI Not found42.82.196.0
- 42.82.200.0/22AS9770LG HelloVision Corp.RPKI Not found42.82.200.0
- 42.82.204.0/22AS9770LG HelloVision Corp.RPKI Not found42.82.204.0
- 42.82.208.0/20AS9770LG HelloVision Corp.RPKI Not found42.82.208.0
- 42.82.224.0/22AS9845LG HelloVision Corp.RPKI Not found42.82.224.0
- 42.82.228.0/22AS9845LG HelloVision Corp.RPKI Not found42.82.228.0
- 42.82.232.0/22AS9697LG HelloVision Corp.RPKI Not found42.82.232.0
- 42.82.236.0/22AS9697LG HelloVision Corp.RPKI Not found42.82.236.0
- 42.82.240.0/22AS9845LG HelloVision Corp.RPKI Not found42.82.240.0
- 42.82.248.0/22AS9845LG HelloVision Corp.RPKI Not found42.82.248.0
- 42.82.252.0/22AS9845LG HelloVision Corp.RPKI Not found42.82.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, 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.