BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
211.32.0.0/16
Announced exactly
- 211.32.0.0/16AS3786LG DACOM CorporationRPKI Not found211.32.0.0
- Registry
- APNIC · South Korea · Aug 27, 1999
- Delegated block
- 211.32.0.0 – 211.32.255.255
Covering routes
No less-specific route covers it.
More-specific routes
- 211.32.8.0/24AS38661abcleRPKI Not found211.32.8.0
- 211.32.22.0/24AS10185Hana Bank Co.RPKI Not found211.32.22.0
- 211.32.30.0/24AS9319HCN CHUNGBUK CABLE TV SYSTEMSRPKI Not found211.32.30.0
- 211.32.31.0/24AS10185Hana Bank Co.RPKI Not found211.32.31.0
- 211.32.32.0/24AS10185Hana Bank Co.RPKI Not found211.32.32.0
- 211.32.34.0/24AS23601tsisRPKI Not found211.32.34.0
- 211.32.37.0/24AS9319HCN CHUNGBUK CABLE TV SYSTEMSRPKI Not found211.32.37.0
- 211.32.53.0/24AS9530SHINSEGAE I C Co., Ltd.RPKI Not found211.32.53.0
- 211.32.93.0/24AS9967kbcardRPKI Not found211.32.93.0
- 211.32.100.0/24AS23601tsisRPKI Not found211.32.100.0
- 211.32.121.0/24AS9319HCN CHUNGBUK CABLE TV SYSTEMSRPKI Not found211.32.121.0
- 211.32.122.0/23AS9319HCN CHUNGBUK CABLE TV SYSTEMSRPKI Not found211.32.122.0
- 211.32.127.0/24AS9319HCN CHUNGBUK CABLE TV SYSTEMSRPKI Not found211.32.127.0
- 211.32.128.0/24AS9569SEOCHO CABLE SYSTEMS CO., LTD.RPKI Not found211.32.128.0
- 211.32.155.0/24AS45974NHNCLOUDRPKI Not found211.32.155.0
- 211.32.160.0/24AS9699Standard CharteredRPKI Not found211.32.160.0
- 211.32.161.0/24AS18305POSCO DXRPKI Not found211.32.161.0
- 211.32.162.0/24AS18305POSCO DXRPKI Not found211.32.162.0
- 211.32.165.0/24AS18305POSCO DXRPKI Not found211.32.165.0
- 211.32.174.0/24AS131890Tmoney co., ltdRPKI Not found211.32.174.0
- 211.32.186.0/24AS9632SEOUL DAIRY CO-OP.RPKI Not found211.32.186.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.