Country
—
ASN LANDING PAGE
KINXIDC-AS-KR KINX
Last updated · Apr 4, 2026
Country
—
Total prefixes
188
IPv4 prefixes
186
IPv6 prefixes
2
KINXIDC-AS-KR KINX currently shows 188 prefixes and 30 upstream, downstream, or peer relationships. Larger prefix inventories often indicate broader network footprint, but they should still be read together with country and peering context.
ASN landing pages are more useful than a single IP page when you want cloud provider attribution, routing research, infrastructure comparison, or network topology analysis at the organization level.
KINXIDC-AS-KR KINX is currently associated with an unknown region. Country data is only a starting point; the more important signals are the organization name, website, prefix volume, and peering relationships that reveal whether the network behaves like a cloud platform, ISP, CDN, or enterprise backbone.
This page is currently showing live ASN data that can be used for peer, prefix, and network scale analysis. The most useful next step is usually to return to a related IP landing page, then compare that concrete address with this ASN profile and with broader topic pages for routing, cloud attribution, or WHOIS ownership analysis.
Detailed data for this ASN is not available right now.
AS17589
AS17589
—
AS398704
AS398704
—
AS46003
AS46003
—
AS9639
AS9639
—
AS23599
AS23599
—
AS152205
AS152205
—
AS24429
AS24429
—
AS45382
AS45382
—
AS4792
AS4792
—
AS17877
AS17877
—
AS45102
AS45102
—
AS152229
AS152229
—
AS138995
AS138995
—
AS135530
AS135530
—
AS137983
AS137983
—
AS63199
AS63199
—
AS19551
AS19551
—
AS24319
AS24319
—
AS9318
AS9318
—
AS23344
AS23344
—
AS21859
AS21859
—
AS23588
AS23588
—
AS16839
AS16839
—
AS131094
AS131094
—
AS26464
AS26464
—
AS31529
AS31529
—
AS136897
AS136897
—
| Prefix | Name | Country |
|---|---|---|
| 1.201.0.0/18 | AS9286 | — |
| 1.201.125.0/24 | AS9286 | — |
| 1.201.126.0/24 | AS9286 | — |
| 1.201.127.0/24 | AS9286 | — |
| 1.201.128.0/18 | AS9286 | — |
| 1.201.128.0/24 | AS9286 | — |
| 1.201.136.0/22 | AS9286 | — |
| 1.201.152.0/21 | AS9286 | — |
| 1.201.16.0/24 | AS9286 | — |
| 1.201.17.0/24 | AS9286 | — |
| 1.201.18.0/24 | AS9286 | — |
| 1.201.19.0/24 | AS9286 | — |
| 1.201.192.0/18 | AS9286 | — |
| 1.201.64.0/18 | AS9286 | — |
| 1.201.65.0/24 | AS9286 | — |
| 1.201.66.0/24 | AS9286 | — |
| 103.230.59.0/24 | AS9286 | — |
| 103.6.100.0/22 | AS9286 | — |
| 103.6.101.0/24 | AS9286 | — |
| 103.6.102.0/24 | AS9286 | — |
| 103.60.124.0/24 | AS9286 | — |
| 103.60.125.0/24 | AS9286 | — |
| 103.60.126.0/24 | AS9286 | — |
| 103.60.127.0/24 | AS9286 | — |
| 121.50.64.0/19 | AS9286 | — |
| 121.50.96.0/19 | AS9286 | — |
| 121.78.0.0/18 | AS9286 | — |
| 121.78.104.0/21 | AS9286 | — |
| 121.78.112.0/21 | AS9286 | — |
| 121.78.123.0/24 | AS9286 | — |
| 121.78.125.0/24 | AS9286 | — |
| 121.78.128.0/18 | AS9286 | — |
| 121.78.128.0/21 | AS9286 | — |
| 121.78.128.0/24 | AS9286 | — |
| 121.78.130.0/24 | AS9286 | — |
| 121.78.135.0/24 | AS9286 | — |
| 121.78.136.0/21 | AS9286 | — |
| 121.78.144.0/21 | AS9286 | — |
| 121.78.151.0/24 | AS9286 | — |
| 121.78.153.0/24 | AS9286 | — |
A strong reference ASN for Google DNS, Google Cloud, and global network footprint analysis.
Useful for analyzing CDN, Anycast, WAF, and large-scale edge network behavior.
Helpful when comparing Azure, enterprise backbone, and large-cloud routing patterns.
A useful ASN landing page for understanding AWS and large cloud-network ownership.
Continue from this ASN into the differences between WHOIS ownership and ASN ownership.
Continue from this ASN into route troubleshooting and network analysis.
Useful when you want to compare this ASN against larger cloud and edge networks.
Continue from the ASN page into WHOIS and ownership verification.
AS9286 is an autonomous system number used to identify an independently operated network. The current page associates it with KINXIDC-AS-KR KINX in an unknown region, which helps determine whether it behaves like a cloud provider, ISP, CDN, or enterprise backbone.
They help explain the scale, interconnection depth, and route structure of AS9286. Richer peering and upstream data often indicate broader network reach, but they should still be interpreted together with prefixes and related IP landing pages.
The best next step is usually to return to a concrete IP landing page to see how a specific address maps into AS9286, then continue into cloud, WHOIS, or routing topic pages to understand the network in a broader context.
Understand why WHOIS ownership and ASN ownership can differ, and how to combine both when deciding who really owns or operates an IP.
Use WHOIS, ASN, prefixes, and organization data to determine who ultimately owns an IP, range, or resolved domain target.
Learn what ASN, BGP routes, prefixes, upstreams, downstreams, and peers mean, then explore real ASN pages.
Compare large cloud and edge networks such as Google, Cloudflare, Microsoft, and Amazon through their ASN landing pages.