Country
—
ASN LANDING PAGE
KE-NET2000
Last updated · Apr 4, 2026
Country
—
Total prefixes
65
IPv4 prefixes
63
IPv6 prefixes
2
KE-NET2000 currently shows 65 prefixes and 34 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.
KE-NET2000 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.
AS328490
AS328490
—
AS327786
AS327786
—
AS329044
AS329044
—
AS328753
AS328753
—
AS37129
AS37129
—
AS328987
AS328987
—
AS329211
AS329211
—
AS329621
AS329621
—
AS328162
AS328162
—
AS328782
AS328782
—
AS329622
AS329622
—
AS327748
AS327748
—
AS329654
AS329654
—
AS329497
AS329497
—
AS329528
AS329528
—
AS329192
AS329192
—
AS329518
AS329518
—
AS329183
AS329183
—
AS329702
AS329702
—
AS329437
AS329437
—
AS329272
AS329272
—
AS37406
AS37406
—
AS327994
AS327994
—
AS16637
AS16637
—
AS329288
AS329288
—
AS329426
AS329426
—
AS328993
AS328993
—
AS329033
AS329033
—
AS37684
AS37684
—
AS329562
AS329562
—
AS329618
AS329618
—
AS329658
AS329658
—
| Prefix | Name | Country |
|---|---|---|
| 195.202.64.0/21 | AS9129 | — |
| 195.202.64.0/24 | AS9129 | — |
| 195.202.65.0/24 | AS9129 | — |
| 195.202.66.0/24 | AS9129 | — |
| 195.202.67.0/24 | AS9129 | — |
| 195.202.72.0/21 | AS9129 | — |
| 195.202.73.0/24 | AS9129 | — |
| 195.202.75.0/24 | AS9129 | — |
| 195.202.76.0/24 | AS9129 | — |
| 195.202.80.0/21 | AS9129 | — |
| 195.202.80.0/22 | AS9129 | — |
| 195.202.81.0/24 | AS9129 | — |
| 195.202.87.0/24 | AS9129 | — |
| 195.202.88.0/21 | AS9129 | — |
| 195.202.88.0/22 | AS9129 | — |
| 195.202.88.0/24 | AS9129 | — |
| 195.202.89.0/24 | AS9129 | — |
| 195.202.90.0/24 | AS9129 | — |
| 195.202.92.0/22 | AS9129 | — |
| 195.202.93.0/24 | AS9129 | — |
| 2001:4368:2000::/48 | AS9129 | — |
| 2001:4368::/32 | AS9129 | — |
| 217.199.144.0/21 | AS9129 | — |
| 217.199.144.0/24 | AS9129 | — |
| 217.199.145.0/24 | AS9129 | — |
| 217.199.146.0/24 | AS9129 | — |
| 217.199.148.0/24 | AS9129 | — |
| 217.199.149.0/24 | AS9129 | — |
| 217.199.151.0/24 | AS9129 | — |
| 217.199.152.0/21 | AS9129 | — |
| 217.199.153.0/24 | AS9129 | — |
| 41.209.10.0/24 | AS9129 | — |
| 41.209.12.0/24 | AS9129 | — |
| 41.209.14.0/24 | AS9129 | — |
| 41.209.15.0/24 | AS9129 | — |
| 41.209.16.0/20 | AS9129 | — |
| 41.209.16.0/21 | AS9129 | — |
| 41.209.17.0/24 | AS9129 | — |
| 41.209.18.0/24 | AS9129 | — |
| 41.209.19.0/24 | AS9129 | — |
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.
AS9129 is an autonomous system number used to identify an independently operated network. The current page associates it with KE-NET2000 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 AS9129. 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 AS9129, 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.