BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
180.182.0.0/16
Announced exactly
- 180.182.0.0/16AS38091LG HelloVision Corp.RPKI Not found180.182.0.0
- Registry
- APNIC · South Korea · Sep 15, 2009
- Delegated block
- 180.182.0.0 – 180.182.255.255
Covering routes
No less-specific route covers it.
More-specific routes
- 180.182.0.0/21AS38091LG HelloVision Corp.RPKI Not found180.182.0.0
- 180.182.8.0/21AS38091LG HelloVision Corp.RPKI Not found180.182.8.0
- 180.182.16.0/21AS38091LG HelloVision Corp.RPKI Not found180.182.16.0
- 180.182.24.0/21AS38091LG HelloVision Corp.RPKI Not found180.182.24.0
- 180.182.32.0/21AS38091LG HelloVision Corp.RPKI Not found180.182.32.0
- 180.182.40.0/21AS38091LG HelloVision Corp.RPKI Not found180.182.40.0
- 180.182.48.0/21AS38091LG HelloVision Corp.RPKI Not found180.182.48.0
- 180.182.48.0/22AS45996DAOU TECHNOLOGYRPKI Not found180.182.48.0
- 180.182.50.0/24AS45996DAOU TECHNOLOGYRPKI Not found180.182.50.0
- 180.182.52.0/23AS45996DAOU TECHNOLOGYRPKI Not found180.182.52.0
- 180.182.54.0/24AS38091LG HelloVision Corp.RPKI Not found180.182.54.0
- 180.182.56.0/21AS38091LG HelloVision Corp.RPKI Not found180.182.56.0
- 180.182.64.0/24AS38669LG HelloVision Corp.RPKI Not found180.182.64.0
- 180.182.66.0/24AS38091LG HelloVision Corp.RPKI Not found180.182.66.0
- 180.182.67.0/24AS38091LG HelloVision Corp.RPKI Not found180.182.67.0
- 180.182.68.0/24AS38091LG HelloVision Corp.RPKI Not found180.182.68.0
- 180.182.72.0/21AS17577LG HelloVision Corp.RPKI Not found180.182.72.0
- 180.182.80.0/21AS17577LG HelloVision Corp.RPKI Not found180.182.80.0
- 180.182.88.0/21AS17577LG HelloVision Corp.RPKI Not found180.182.88.0
- 180.182.96.0/21AS38669LG HelloVision Corp.RPKI Not found180.182.96.0
- 180.182.96.0/22AS38669LG HelloVision Corp.RPKI Not found180.182.96.0
- 180.182.100.0/22AS38669LG HelloVision Corp.RPKI Not found180.182.100.0
- 180.182.104.0/21AS38669LG HelloVision Corp.RPKI Not found180.182.104.0
- 180.182.107.0/24AS38669LG HelloVision Corp.RPKI Not found180.182.107.0
- 180.182.112.0/21AS38669LG HelloVision Corp.RPKI Not found180.182.112.0
- 180.182.120.0/21AS38669LG HelloVision Corp.RPKI Not found180.182.120.0
- 180.182.128.0/19AS17839LG HelloVision Corp.RPKI Not found180.182.128.0
- 180.182.128.0/21AS17839LG HelloVision Corp.RPKI Not found180.182.128.0
- 180.182.131.0/24AS17839LG HelloVision Corp.RPKI Not found180.182.131.0
- 180.182.136.0/21AS17839LG HelloVision Corp.RPKI Not found180.182.136.0
- 180.182.144.0/21AS17839LG HelloVision Corp.RPKI Not found180.182.144.0
- 180.182.152.0/21AS17839LG HelloVision Corp.RPKI Not found180.182.152.0
- 180.182.160.0/21AS18313LG HelloVision Corp.RPKI Not found180.182.160.0
- 180.182.168.0/21AS18313LG HelloVision Corp.RPKI Not found180.182.168.0
- 180.182.176.0/21AS18313LG HelloVision Corp.RPKI Not found180.182.176.0
- 180.182.200.0/21AS18313LG HelloVision Corp.RPKI Not found180.182.200.0
- 180.182.206.0/23AS45996DAOU TECHNOLOGYRPKI Not found180.182.206.0
- 180.182.207.0/24AS45996DAOU TECHNOLOGYRPKI Not found180.182.207.0
- 180.182.208.0/20AS9697LG HelloVision Corp.RPKI Not found180.182.208.0
- 180.182.224.0/24AS9845LG HelloVision Corp.RPKI Not found180.182.224.0
- 180.182.225.0/24AS9845LG HelloVision Corp.RPKI Not found180.182.225.0
- 180.182.226.0/24AS9845LG HelloVision Corp.RPKI Not found180.182.226.0
- 180.182.227.0/24AS9845LG HelloVision Corp.RPKI Not found180.182.227.0
- 180.182.228.0/24AS9845LG HelloVision Corp.RPKI Not found180.182.228.0
- 180.182.229.0/24AS9845LG HelloVision Corp.RPKI Not found180.182.229.0
- 180.182.230.0/24AS9845LG HelloVision Corp.RPKI Not found180.182.230.0
- 180.182.231.0/24AS9845LG HelloVision Corp.RPKI Not found180.182.231.0
- 180.182.232.0/24AS9845LG HelloVision Corp.RPKI Not found180.182.232.0
- 180.182.233.0/24AS9845LG HelloVision Corp.RPKI Not found180.182.233.0
- 180.182.234.0/24AS9845LG HelloVision Corp.RPKI Not found180.182.234.0
- 180.182.235.0/24AS9845LG HelloVision Corp.RPKI Not found180.182.235.0
- 180.182.236.0/24AS9845LG HelloVision Corp.RPKI Not found180.182.236.0
- 180.182.237.0/24AS9845LG HelloVision Corp.RPKI Not found180.182.237.0
- 180.182.238.0/24AS9845LG HelloVision Corp.RPKI Not found180.182.238.0
- 180.182.239.0/24AS9845LG HelloVision Corp.RPKI Not found180.182.239.0
- 180.182.240.0/21AS9845LG HelloVision Corp.RPKI Not found180.182.240.0
On the internet, routes are announced as prefixes: an autonomous system tells its neighbours via BGP that it can deliver traffic for, say, 193.166.0.0/15. 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.