BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
114.29.0.0/17
Announced exactly
- 114.29.0.0/17AS38091LG HelloVision Corp.RPKI Not found114.29.0.0
- Registry
- APNIC · South Korea · Apr 21, 2008
- Delegated block
- 114.29.0.0 – 114.29.127.255
Covering routes
No less-specific route covers it.
More-specific routes
- 114.29.0.0/21AS38669LG HelloVision Corp.RPKI Not found114.29.0.0
- 114.29.8.0/21AS38669LG HelloVision Corp.RPKI Not found114.29.8.0
- 114.29.16.0/21AS38669LG HelloVision Corp.RPKI Not found114.29.16.0
- 114.29.24.0/21AS38669LG HelloVision Corp.RPKI Not found114.29.24.0
- 114.29.32.0/21AS38669LG HelloVision Corp.RPKI Not found114.29.32.0
- 114.29.40.0/22AS38669LG HelloVision Corp.RPKI Not found114.29.40.0
- 114.29.44.0/24AS38669LG HelloVision Corp.RPKI Not found114.29.44.0
- 114.29.45.0/24AS38669LG HelloVision Corp.RPKI Not found114.29.45.0
- 114.29.46.0/23AS38669LG HelloVision Corp.RPKI Not found114.29.46.0
- 114.29.48.0/21AS38669LG HelloVision Corp.RPKI Not found114.29.48.0
- 114.29.56.0/21AS38669LG HelloVision Corp.RPKI Not found114.29.56.0
- 114.29.64.0/21AS38669LG HelloVision Corp.RPKI Not found114.29.64.0
- 114.29.72.0/21AS38669LG HelloVision Corp.RPKI Not found114.29.72.0
- 114.29.77.0/24AS38669LG HelloVision Corp.RPKI Not found114.29.77.0
- 114.29.80.0/21AS38669LG HelloVision Corp.RPKI Not found114.29.80.0
- 114.29.88.0/21AS38669LG HelloVision Corp.RPKI Not found114.29.88.0
- 114.29.96.0/21AS38669LG HelloVision Corp.RPKI Not found114.29.96.0
- 114.29.104.0/21AS38669LG HelloVision Corp.RPKI Not found114.29.104.0
- 114.29.112.0/24AS38669LG HelloVision Corp.RPKI Not found114.29.112.0
- 114.29.113.0/24AS38669LG HelloVision Corp.RPKI Not found114.29.113.0
- 114.29.114.0/24AS38669LG HelloVision Corp.RPKI Not found114.29.114.0
- 114.29.115.0/24AS38669LG HelloVision Corp.RPKI Not found114.29.115.0
- 114.29.116.0/22AS38669LG HelloVision Corp.RPKI Not found114.29.116.0
- 114.29.120.0/23AS38669LG HelloVision Corp.RPKI Not found114.29.120.0
- 114.29.122.0/24AS38669LG HelloVision Corp.RPKI Not found114.29.122.0
- 114.29.123.0/24AS38669LG HelloVision Corp.RPKI Not found114.29.123.0
- 114.29.124.0/22AS38669LG HelloVision Corp.RPKI Not found114.29.124.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.