BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
210.206.0.0/16
Announced exactly
- 210.206.0.0/16AS3786LG DACOM CorporationRPKI Not found210.206.0.0
- Registry
- APNIC · South Korea · May 25, 1999
- Delegated block
- 210.206.0.0 – 210.207.255.255
Covering routes
No less-specific route covers it.
More-specific routes
- 210.206.37.0/24AS17586LG HelloVision Corp.RPKI Not found210.206.37.0
- 210.206.41.0/24AS17586LG HelloVision Corp.RPKI Not found210.206.41.0
- 210.206.46.0/24AS17586LG HelloVision Corp.RPKI Not found210.206.46.0
- 210.206.47.0/24AS17586LG HelloVision Corp.RPKI Not found210.206.47.0
- 210.206.52.0/24AS18318LG HelloVision Corp.RPKI Not found210.206.52.0
- 210.206.81.0/24AS38661abcleRPKI Not found210.206.81.0
- 210.206.82.0/24AS18318LG HelloVision Corp.RPKI Not found210.206.82.0
- 210.206.83.0/24AS18318LG HelloVision Corp.RPKI Not found210.206.83.0
- 210.206.84.0/24AS18318LG HelloVision Corp.RPKI Not found210.206.84.0
- 210.206.88.0/24AS45974NHNCLOUDRPKI Not found210.206.88.0
- 210.206.94.0/24AS18318LG HelloVision Corp.RPKI Not found210.206.94.0
- 210.206.99.0/24AS18318LG HelloVision Corp.RPKI Not found210.206.99.0
- 210.206.100.0/24AS18318LG HelloVision Corp.RPKI Not found210.206.100.0
- 210.206.102.0/24AS18318LG HelloVision Corp.RPKI Not found210.206.102.0
- 210.206.131.0/24AS9959KOREA STOCK EXCHANGERPKI Not found210.206.131.0
- 210.206.132.0/24AS9959KOREA STOCK EXCHANGERPKI Not found210.206.132.0
- 210.206.185.0/24AS18318LG HelloVision Corp.RPKI Not found210.206.185.0
- 210.206.186.0/23AS17598LG HelloVision Corp.RPKI Not found210.206.186.0
- 210.206.189.0/24AS45987Dongwha Enterprise Co. Ltd.RPKI Not found210.206.189.0
- 210.206.199.0/24AS17598LG HelloVision Corp.RPKI Not found210.206.199.0
- 210.206.200.0/24AS17598LG HelloVision Corp.RPKI Not found210.206.200.0
- 210.206.209.0/24AS17598LG HelloVision Corp.RPKI Not found210.206.209.0
- 210.206.221.0/24AS17862Kangwon National UniversityRPKI Not found210.206.221.0
- 210.206.237.0/24AS38661abcleRPKI Not found210.206.237.0
- 210.206.239.0/24AS38661abcleRPKI Not found210.206.239.0
- 210.206.245.0/24AS38661abcleRPKI Not found210.206.245.0
- 210.206.248.0/24AS17853LGTELECOMRPKI Not found210.206.248.0
- 210.206.254.0/24AS17598LG HelloVision Corp.RPKI Not found210.206.254.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.