BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
211.173.0.0/17
Announced exactly
- 211.173.0.0/17AS9316DACOM-PUBNETPLUSRPKI Not found211.173.0.0
- Registry
- APNIC · South Korea · May 26, 2000
- Delegated block
- 211.173.0.0 – 211.173.127.255
Covering routes
No less-specific route covers it.
More-specific routes
- 211.173.8.0/23AS10055Korean National Railroad AdministrationRPKI Not found211.173.8.0
- 211.173.10.0/24AS10055Korean National Railroad AdministrationRPKI Not found211.173.10.0
- 211.173.16.0/24AS38669LG HelloVision Corp.RPKI Not found211.173.16.0
- 211.173.17.0/24AS38669LG HelloVision Corp.RPKI Not found211.173.17.0
- 211.173.18.0/24AS38669LG HelloVision Corp.RPKI Not found211.173.18.0
- 211.173.19.0/24AS38669LG HelloVision Corp.RPKI Not found211.173.19.0
- 211.173.20.0/24AS38669LG HelloVision Corp.RPKI Not found211.173.20.0
- 211.173.21.0/24AS38669LG HelloVision Corp.RPKI Not found211.173.21.0
- 211.173.22.0/24AS38669LG HelloVision Corp.RPKI Not found211.173.22.0
- 211.173.23.0/24AS38669LG HelloVision Corp.RPKI Not found211.173.23.0
- 211.173.24.0/22AS9770LG HelloVision Corp.RPKI Not found211.173.24.0
- 211.173.34.0/24AS17841NATIONAL INFORMATION RESOURCES SERVICERPKI Not found211.173.34.0
- 211.173.35.0/24AS17841NATIONAL INFORMATION RESOURCES SERVICERPKI Not found211.173.35.0
- 211.173.36.0/24AS17841NATIONAL INFORMATION RESOURCES SERVICERPKI Not found211.173.36.0
- 211.173.37.0/24AS17841NATIONAL INFORMATION RESOURCES SERVICERPKI Not found211.173.37.0
- 211.173.38.0/24AS17841NATIONAL INFORMATION RESOURCES SERVICERPKI Not found211.173.38.0
- 211.173.39.0/24AS17841NATIONAL INFORMATION RESOURCES SERVICERPKI Not found211.173.39.0
- 211.173.40.0/24AS10165KOREA CUSTOMS SERVICERPKI Not found211.173.40.0
- 211.173.41.0/24AS10165KOREA CUSTOMS SERVICERPKI Not found211.173.41.0
- 211.173.42.0/24AS10165KOREA CUSTOMS SERVICERPKI Not found211.173.42.0
- 211.173.43.0/24AS10165KOREA CUSTOMS SERVICERPKI Not found211.173.43.0
- 211.173.44.0/24AS10165KOREA CUSTOMS SERVICERPKI Not found211.173.44.0
- 211.173.45.0/24AS10165KOREA CUSTOMS SERVICERPKI Not found211.173.45.0
- 211.173.46.0/24AS17841NATIONAL INFORMATION RESOURCES SERVICERPKI Not found211.173.46.0
- 211.173.48.0/24AS9698LG HelloVision Corp.RPKI Not found211.173.48.0
- 211.173.49.0/24AS9698LG HelloVision Corp.RPKI Not found211.173.49.0
- 211.173.50.0/24AS9698LG HelloVision Corp.RPKI Not found211.173.50.0
- 211.173.51.0/24AS9698LG HelloVision Corp.RPKI Not found211.173.51.0
- 211.173.52.0/24AS9698LG HelloVision Corp.RPKI Not found211.173.52.0
- 211.173.53.0/24AS9698LG HelloVision Corp.RPKI Not found211.173.53.0
- 211.173.54.0/24AS9698LG HelloVision Corp.RPKI Not found211.173.54.0
- 211.173.55.0/24AS9698LG HelloVision Corp.RPKI Not found211.173.55.0
- 211.173.64.0/22AS9770LG HelloVision Corp.RPKI Not found211.173.64.0
- 211.173.84.0/22AS9770LG HelloVision Corp.RPKI Not found211.173.84.0
- 211.173.88.0/24AS9698LG HelloVision Corp.RPKI Not found211.173.88.0
- 211.173.89.0/24AS9698LG HelloVision Corp.RPKI Not found211.173.89.0
- 211.173.90.0/24AS9698LG HelloVision Corp.RPKI Not found211.173.90.0
- 211.173.91.0/24AS9698LG HelloVision Corp.RPKI Not found211.173.91.0
- 211.173.92.0/24AS9698LG HelloVision Corp.RPKI Not found211.173.92.0
- 211.173.93.0/24AS9698LG HelloVision Corp.RPKI Not found211.173.93.0
- 211.173.94.0/24AS9698LG HelloVision Corp.RPKI Not found211.173.94.0
- 211.173.95.0/24AS9698LG HelloVision Corp.RPKI Not found211.173.95.0
- 211.173.106.0/24AS152226PARADISERPKI Not found211.173.106.0
- 211.173.107.0/24AS152226PARADISERPKI Not found211.173.107.0
- 211.173.108.0/22AS9770LG HelloVision Corp.RPKI Not found211.173.108.0
- 211.173.112.0/20AS17858LG POWERCOMMRPKI Not found211.173.112.0
- 211.173.112.0/21AS17858LG POWERCOMMRPKI Not found211.173.112.0
- 211.173.120.0/21AS17858LG POWERCOMMRPKI Not found211.173.120.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.