BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
113.130.128.0/17
Announced exactly
- 113.130.128.0/17AS38091LG HelloVision Corp.RPKI Not found113.130.128.0
- Registry
- APNIC · South Korea · Nov 10, 2008
- Delegated block
- 113.130.128.0 – 113.130.255.255
Covering routes
No less-specific route covers it.
More-specific routes
- 113.130.128.0/21AS9845LG HelloVision Corp.RPKI Not found113.130.128.0
- 113.130.128.0/24AS9845LG HelloVision Corp.RPKI Not found113.130.128.0
- 113.130.129.0/24AS9845LG HelloVision Corp.RPKI Not found113.130.129.0
- 113.130.130.0/24AS9845LG HelloVision Corp.RPKI Not found113.130.130.0
- 113.130.131.0/24AS9845LG HelloVision Corp.RPKI Not found113.130.131.0
- 113.130.132.0/24AS9845LG HelloVision Corp.RPKI Not found113.130.132.0
- 113.130.133.0/24AS9845LG HelloVision Corp.RPKI Not found113.130.133.0
- 113.130.134.0/24AS9845LG HelloVision Corp.RPKI Not found113.130.134.0
- 113.130.135.0/24AS9845LG HelloVision Corp.RPKI Not found113.130.135.0
- 113.130.136.0/21AS9845LG HelloVision Corp.RPKI Not found113.130.136.0
- 113.130.144.0/21AS9845LG HelloVision Corp.RPKI Not found113.130.144.0
- 113.130.152.0/21AS9845LG HelloVision Corp.RPKI Not found113.130.152.0
- 113.130.160.0/21AS9845LG HelloVision Corp.RPKI Not found113.130.160.0
- 113.130.168.0/21AS9845LG HelloVision Corp.RPKI Not found113.130.168.0
- 113.130.176.0/21AS9845LG HelloVision Corp.RPKI Not found113.130.176.0
- 113.130.184.0/21AS9845LG HelloVision Corp.RPKI Not found113.130.184.0
- 113.130.192.0/21AS9845LG HelloVision Corp.RPKI Not found113.130.192.0
- 113.130.200.0/21AS9845LG HelloVision Corp.RPKI Not found113.130.200.0
- 113.130.208.0/21AS9845LG HelloVision Corp.RPKI Not found113.130.208.0
- 113.130.216.0/22AS9845LG HelloVision Corp.RPKI Not found113.130.216.0
- 113.130.216.0/24AS9845LG HelloVision Corp.RPKI Not found113.130.216.0
- 113.130.217.0/24AS9845LG HelloVision Corp.RPKI Not found113.130.217.0
- 113.130.218.0/24AS9845LG HelloVision Corp.RPKI Not found113.130.218.0
- 113.130.219.0/24AS9845LG HelloVision Corp.RPKI Not found113.130.219.0
- 113.130.220.0/23AS9845LG HelloVision Corp.RPKI Not found113.130.220.0
- 113.130.222.0/24AS9845LG HelloVision Corp.RPKI Not found113.130.222.0
- 113.130.223.0/24AS9845LG HelloVision Corp.RPKI Not found113.130.223.0
- 113.130.224.0/24AS9845LG HelloVision Corp.RPKI Not found113.130.224.0
- 113.130.225.0/24AS9845LG HelloVision Corp.RPKI Not found113.130.225.0
- 113.130.226.0/24AS9845LG HelloVision Corp.RPKI Not found113.130.226.0
- 113.130.227.0/24AS9845LG HelloVision Corp.RPKI Not found113.130.227.0
- 113.130.228.0/24AS9845LG HelloVision Corp.RPKI Not found113.130.228.0
- 113.130.229.0/24AS9845LG HelloVision Corp.RPKI Not found113.130.229.0
- 113.130.230.0/24AS9845LG HelloVision Corp.RPKI Not found113.130.230.0
- 113.130.231.0/24AS9845LG HelloVision Corp.RPKI Not found113.130.231.0
- 113.130.232.0/21AS9845LG HelloVision Corp.RPKI Not found113.130.232.0
- 113.130.240.0/21AS9845LG HelloVision Corp.RPKI Not found113.130.240.0
- 113.130.248.0/24AS9845LG HelloVision Corp.RPKI Not found113.130.248.0
- 113.130.249.0/24AS9845LG HelloVision Corp.RPKI Not found113.130.249.0
- 113.130.250.0/24AS9845LG HelloVision Corp.RPKI Not found113.130.250.0
- 113.130.251.0/24AS9845LG HelloVision Corp.RPKI Not found113.130.251.0
- 113.130.252.0/24AS9845LG HelloVision Corp.RPKI Not found113.130.252.0
- 113.130.253.0/24AS9845LG HelloVision Corp.RPKI Not found113.130.253.0
- 113.130.254.0/24AS9845LG HelloVision Corp.RPKI Not found113.130.254.0
- 113.130.255.0/24AS9845LG HelloVision Corp.RPKI Not found113.130.255.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.