BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
211.112.128.0/17
Announced exactly
- 211.112.128.0/17AS9316DACOM-PUBNETPLUSRPKI Not found211.112.128.0
- Registry
- APNIC · South Korea · Apr 14, 2000
- Delegated block
- 211.112.128.0 – 211.112.255.255
Covering routes
No less-specific route covers it.
More-specific routes
- 211.112.137.0/25AS131797National Medical CenterRPKI Not found211.112.137.0
- 211.112.148.0/24AS9770LG HelloVision Corp.RPKI Not found211.112.148.0
- 211.112.154.0/24AS17841NATIONAL INFORMATION RESOURCES SERVICERPKI Not found211.112.154.0
- 211.112.156.0/22AS9770LG HelloVision Corp.RPKI Not found211.112.156.0
- 211.112.160.0/20AS17858LG POWERCOMMRPKI Not found211.112.160.0
- 211.112.160.0/21AS17858LG POWERCOMMRPKI Not found211.112.160.0
- 211.112.168.0/21AS17858LG POWERCOMMRPKI Not found211.112.168.0
- 211.112.180.0/22AS9770LG HelloVision Corp.RPKI Not found211.112.180.0
- 211.112.192.0/20AS17858LG POWERCOMMRPKI Not found211.112.192.0
- 211.112.192.0/21AS17858LG POWERCOMMRPKI Not found211.112.192.0
- 211.112.200.0/21AS17858LG POWERCOMMRPKI Not found211.112.200.0
- 211.112.208.0/22AS9770LG HelloVision Corp.RPKI Not found211.112.208.0
- 211.112.216.0/24AS38669LG HelloVision Corp.RPKI Not found211.112.216.0
- 211.112.217.0/24AS38669LG HelloVision Corp.RPKI Not found211.112.217.0
- 211.112.218.0/24AS38669LG HelloVision Corp.RPKI Not found211.112.218.0
- 211.112.219.0/24AS38669LG HelloVision Corp.RPKI Not found211.112.219.0
- 211.112.220.0/24AS38669LG HelloVision Corp.RPKI Not found211.112.220.0
- 211.112.221.0/24AS38669LG HelloVision Corp.RPKI Not found211.112.221.0
- 211.112.222.0/24AS38669LG HelloVision Corp.RPKI Not found211.112.222.0
- 211.112.223.0/24AS38669LG HelloVision Corp.RPKI Not found211.112.223.0
- 211.112.236.0/22AS9770LG HelloVision Corp.RPKI Not found211.112.236.0
- 211.112.240.0/24AS38669LG HelloVision Corp.RPKI Not found211.112.240.0
- 211.112.241.0/24AS38669LG HelloVision Corp.RPKI Not found211.112.241.0
- 211.112.242.0/24AS38669LG HelloVision Corp.RPKI Not found211.112.242.0
- 211.112.243.0/24AS38669LG HelloVision Corp.RPKI Not found211.112.243.0
- 211.112.244.0/24AS38669LG HelloVision Corp.RPKI Not found211.112.244.0
- 211.112.245.0/24AS38669LG HelloVision Corp.RPKI Not found211.112.245.0
- 211.112.246.0/24AS38669LG HelloVision Corp.RPKI Not found211.112.246.0
- 211.112.247.0/24AS38669LG HelloVision Corp.RPKI Not found211.112.247.0
- 211.112.248.0/22AS9770LG HelloVision Corp.RPKI Not found211.112.248.0
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.