BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
36.38.0.0/16
Announced exactly
- 36.38.0.0/16AS38091LG HelloVision Corp.RPKI Not found36.38.0.0
- Registry
- APNIC · South Korea · Feb 3, 2011
- Delegated block
- 36.38.0.0 – 36.39.255.255
Covering routes
No less-specific route covers it.
More-specific routes
- 36.38.0.0/24AS38120LG HelloVision Corp.RPKI Not found36.38.0.0
- 36.38.1.0/24AS38120LG HelloVision Corp.RPKI Not found36.38.1.0
- 36.38.2.0/24AS38120LG HelloVision Corp.RPKI Not found36.38.2.0
- 36.38.3.0/24AS38120LG HelloVision Corp.RPKI Not found36.38.3.0
- 36.38.4.0/24AS38120LG HelloVision Corp.RPKI Not found36.38.4.0
- 36.38.5.0/24AS38120LG HelloVision Corp.RPKI Not found36.38.5.0
- 36.38.6.0/24AS38120LG HelloVision Corp.RPKI Not found36.38.6.0
- 36.38.7.0/24AS38120LG HelloVision Corp.RPKI Not found36.38.7.0
- 36.38.8.0/21AS38091LG HelloVision Corp.RPKI Not found36.38.8.0
- 36.38.12.0/24AS38091LG HelloVision Corp.RPKI Not found36.38.12.0
- 36.38.13.0/24AS45996DAOU TECHNOLOGYRPKI Not found36.38.13.0
- 36.38.16.0/22AS45365LG HelloVision Corp.RPKI Not found36.38.16.0
- 36.38.20.0/22AS45365LG HelloVision Corp.RPKI Not found36.38.20.0
- 36.38.24.0/21AS38091LG HelloVision Corp.RPKI Not found36.38.24.0
- 36.38.24.0/24AS38091LG HelloVision Corp.RPKI Not found36.38.24.0
- 36.38.27.0/24AS38091LG HelloVision Corp.RPKI Not found36.38.27.0
- 36.38.29.0/24AS17586LG HelloVision Corp.RPKI Not found36.38.29.0
- 36.38.30.0/24AS9698LG HelloVision Corp.RPKI Not found36.38.30.0
- 36.38.31.0/24AS9698LG HelloVision Corp.RPKI Not found36.38.31.0
- 36.38.32.0/20AS38091LG HelloVision Corp.RPKI Not found36.38.32.0
- 36.38.32.0/22AS38091LG HelloVision Corp.RPKI Not found36.38.32.0
- 36.38.36.0/24AS38669LG HelloVision Corp.RPKI Not found36.38.36.0
- 36.38.37.0/24AS38669LG HelloVision Corp.RPKI Not found36.38.37.0
- 36.38.38.0/24AS17586LG HelloVision Corp.RPKI Not found36.38.38.0
- 36.38.40.0/24AS9770LG HelloVision Corp.RPKI Not found36.38.40.0
- 36.38.41.0/24AS9770LG HelloVision Corp.RPKI Not found36.38.41.0
- 36.38.42.0/24AS9770LG HelloVision Corp.RPKI Not found36.38.42.0
- 36.38.43.0/24AS9770LG HelloVision Corp.RPKI Not found36.38.43.0
- 36.38.44.0/24AS9770LG HelloVision Corp.RPKI Not found36.38.44.0
- 36.38.45.0/24AS9770LG HelloVision Corp.RPKI Not found36.38.45.0
- 36.38.46.0/24AS9770LG HelloVision Corp.RPKI Not found36.38.46.0
- 36.38.47.0/24AS9770LG HelloVision Corp.RPKI Not found36.38.47.0
- 36.38.48.0/24AS9770LG HelloVision Corp.RPKI Not found36.38.48.0
- 36.38.49.0/24AS9770LG HelloVision Corp.RPKI Not found36.38.49.0
- 36.38.50.0/24AS9770LG HelloVision Corp.RPKI Not found36.38.50.0
- 36.38.51.0/24AS9770LG HelloVision Corp.RPKI Not found36.38.51.0
- 36.38.52.0/24AS9770LG HelloVision Corp.RPKI Not found36.38.52.0
- 36.38.53.0/24AS9770LG HelloVision Corp.RPKI Not found36.38.53.0
- 36.38.54.0/24AS9770LG HelloVision Corp.RPKI Not found36.38.54.0
- 36.38.55.0/24AS9770LG HelloVision Corp.RPKI Not found36.38.55.0
- 36.38.56.0/24AS9770LG HelloVision Corp.RPKI Not found36.38.56.0
- 36.38.57.0/24AS9770LG HelloVision Corp.RPKI Not found36.38.57.0
- 36.38.58.0/24AS9770LG HelloVision Corp.RPKI Not found36.38.58.0
- 36.38.59.0/24AS9770LG HelloVision Corp.RPKI Not found36.38.59.0
- 36.38.60.0/24AS9770LG HelloVision Corp.RPKI Not found36.38.60.0
- 36.38.61.0/24AS9770LG HelloVision Corp.RPKI Not found36.38.61.0
- 36.38.62.0/24AS9770LG HelloVision Corp.RPKI Not found36.38.62.0
- 36.38.63.0/24AS9770LG HelloVision Corp.RPKI Not found36.38.63.0
- 36.38.64.0/21AS18313LG HelloVision Corp.RPKI Not found36.38.64.0
- 36.38.72.0/21AS18313LG HelloVision Corp.RPKI Not found36.38.72.0
- 36.38.80.0/24AS9770LG HelloVision Corp.RPKI Not found36.38.80.0
- 36.38.81.0/24AS9770LG HelloVision Corp.RPKI Not found36.38.81.0
- 36.38.82.0/24AS9770LG HelloVision Corp.RPKI Not found36.38.82.0
- 36.38.83.0/24AS9770LG HelloVision Corp.RPKI Not found36.38.83.0
- 36.38.87.0/24AS38121LG HelloVision Corp.RPKI Not found36.38.87.0
- 36.38.88.0/21AS18313LG HelloVision Corp.RPKI Not found36.38.88.0
- 36.38.96.0/24AS38121LG HelloVision Corp.RPKI Not found36.38.96.0
- 36.38.97.0/24AS38121LG HelloVision Corp.RPKI Not found36.38.97.0
- 36.38.98.0/24AS38121LG HelloVision Corp.RPKI Not found36.38.98.0
- 36.38.99.0/24AS38121LG HelloVision Corp.RPKI Not found36.38.99.0
- 36.38.100.0/24AS38121LG HelloVision Corp.RPKI Not found36.38.100.0
- 36.38.101.0/24AS38121LG HelloVision Corp.RPKI Not found36.38.101.0
- 36.38.102.0/24AS38121LG HelloVision Corp.RPKI Not found36.38.102.0
- 36.38.103.0/24AS38121LG HelloVision Corp.RPKI Not found36.38.103.0
- 36.38.104.0/21AS18313LG HelloVision Corp.RPKI Not found36.38.104.0
- 36.38.112.0/21AS18313LG HelloVision Corp.RPKI Not found36.38.112.0
- 36.38.120.0/21AS18313LG HelloVision Corp.RPKI Not found36.38.120.0
- 36.38.128.0/21AS9697LG HelloVision Corp.RPKI Not found36.38.128.0
- 36.38.136.0/21AS9697LG HelloVision Corp.RPKI Not found36.38.136.0
- 36.38.144.0/21AS9697LG HelloVision Corp.RPKI Not found36.38.144.0
- 36.38.152.0/21AS9697LG HelloVision Corp.RPKI Not found36.38.152.0
- 36.38.160.0/21AS9697LG HelloVision Corp.RPKI Not found36.38.160.0
- 36.38.168.0/22AS38669LG HelloVision Corp.RPKI Not found36.38.168.0
- 36.38.168.0/24AS38669LG HelloVision Corp.RPKI Not found36.38.168.0
- 36.38.169.0/24AS38669LG HelloVision Corp.RPKI Not found36.38.169.0
- 36.38.172.0/22AS38669LG HelloVision Corp.RPKI Not found36.38.172.0
- 36.38.176.0/22AS45365LG HelloVision Corp.RPKI Not found36.38.176.0
- 36.38.176.0/24AS45365LG HelloVision Corp.RPKI Not found36.38.176.0
- 36.38.178.0/24AS45365LG HelloVision Corp.RPKI Not found36.38.178.0
- 36.38.180.0/22AS45365LG HelloVision Corp.RPKI Not found36.38.180.0
- 36.38.180.0/24AS45365LG HelloVision Corp.RPKI Not found36.38.180.0
- 36.38.184.0/22AS45365LG HelloVision Corp.RPKI Not found36.38.184.0
- 36.38.188.0/22AS45365LG HelloVision Corp.RPKI Not found36.38.188.0
- 36.38.192.0/22AS9697LG HelloVision Corp.RPKI Not found36.38.192.0
- 36.38.196.0/22AS9697LG HelloVision Corp.RPKI Not found36.38.196.0
- 36.38.200.0/22AS9697LG HelloVision Corp.RPKI Not found36.38.200.0
- 36.38.204.0/22AS9697LG HelloVision Corp.RPKI Not found36.38.204.0
- 36.38.208.0/22AS9697LG HelloVision Corp.RPKI Not found36.38.208.0
- 36.38.212.0/22AS9697LG HelloVision Corp.RPKI Not found36.38.212.0
- 36.38.216.0/22AS9697LG HelloVision Corp.RPKI Not found36.38.216.0
- 36.38.220.0/22AS9845LG HelloVision Corp.RPKI Not found36.38.220.0
- 36.38.224.0/22AS9845LG HelloVision Corp.RPKI Not found36.38.224.0
- 36.38.228.0/22AS9845LG HelloVision Corp.RPKI Not found36.38.228.0
- 36.38.232.0/22AS9845LG HelloVision Corp.RPKI Not found36.38.232.0
- 36.38.236.0/22AS9697LG HelloVision Corp.RPKI Not found36.38.236.0
- 36.38.240.0/22AS9697LG HelloVision Corp.RPKI Not found36.38.240.0
- 36.38.240.0/24AS9697LG HelloVision Corp.RPKI Not found36.38.240.0
- 36.38.241.0/24AS9697LG HelloVision Corp.RPKI Not found36.38.241.0
- 36.38.242.0/24AS9697LG HelloVision Corp.RPKI Not found36.38.242.0
- 36.38.243.0/24AS9697LG HelloVision Corp.RPKI Not found36.38.243.0
Showing the first 100.
On the internet, routes are announced as prefixes: an autonomous system tells its neighbours via BGP that it can deliver traffic for, say, 158.36.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.