Country
—
ASN LANDING PAGE
KREONET-AS-KR KISTI
Last updated · Apr 4, 2026
Country
—
Total prefixes
200
IPv4 prefixes
199
IPv6 prefixes
1
KREONET-AS-KR KISTI currently shows 200 prefixes and 43 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.
KREONET-AS-KR KISTI 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.
AS23596
AS23596
—
AS152671
AS152671
—
AS9489
AS9489
—
AS10052
AS10052
—
AS17595
AS17595
—
AS38426
AS38426
—
AS45379
AS45379
—
AS9488
AS9488
—
AS9949
AS9949
—
AS152212
AS152212
—
AS10070
AS10070
—
AS18297
AS18297
—
AS2385
AS2385
—
AS10162
AS10162
—
AS131795
AS131795
—
AS9568
AS9568
—
AS9637
AS9637
—
AS18336
AS18336
—
AS9695
AS9695
—
AS24026
AS24026
—
AS131869
AS131869
—
AS1704
AS1704
—
AS17856
AS17856
—
AS17866
AS17866
—
AS10063
AS10063
—
AS55616
AS55616
—
AS131830
AS131830
—
AS10187
AS10187
—
AS7564
AS7564
—
AS1781
AS1781
—
AS9275
AS9275
—
AS17579
AS17579
—
AS9317
AS9317
—
AS18026
AS18026
—
AS38696
AS38696
—
AS45963
AS45963
—
AS3784
AS3784
—
AS18034
AS18034
—
AS9686
AS9686
—
AS18298
AS18298
—
| Prefix | Name | Country |
|---|---|---|
| 134.75.0.0/16 | AS1237 | — |
| 134.75.20.0/24 | AS1237 | — |
| 134.75.250.0/24 | AS1237 | — |
| 134.75.52.0/23 | AS1237 | — |
| 147.47.120.0/21 | AS1237 | — |
| 147.47.124.0/24 | AS1237 | — |
| 147.47.125.0/24 | AS1237 | — |
| 150.183.0.0/16 | AS1237 | — |
| 150.183.11.0/24 | AS1237 | — |
| 2001:320::/32 | AS1237 | — |
| 202.30.40.0/22 | AS1237 | — |
| 202.30.60.0/22 | AS1237 | — |
| 202.31.182.0/24 | AS1237 | — |
| 203.230.108.0/22 | AS1237 | — |
| 203.230.116.0/23 | AS1237 | — |
| 203.230.116.0/24 | AS1237 | — |
| 203.230.120.0/24 | AS1237 | — |
| 203.230.126.0/24 | AS1237 | — |
| 203.230.16.0/23 | AS1237 | — |
| 203.230.2.0/24 | AS1237 | — |
| 203.230.22.0/23 | AS1237 | — |
| 203.230.24.0/21 | AS1237 | — |
| 203.230.3.0/24 | AS1237 | — |
| 203.230.6.0/24 | AS1237 | — |
| 203.230.60.0/22 | AS1237 | — |
| 203.230.64.0/21 | AS1237 | — |
| 203.230.72.0/24 | AS1237 | — |
| 203.230.73.0/24 | AS1237 | — |
| 203.230.74.0/23 | AS1237 | — |
| 203.230.76.0/22 | AS1237 | — |
| 203.230.8.0/22 | AS1237 | — |
| 203.233.155.0/24 | AS1237 | — |
| 203.233.156.0/24 | AS1237 | — |
| 203.241.116.0/23 | AS1237 | — |
| 203.241.118.0/24 | AS1237 | — |
| 203.241.120.0/22 | AS1237 | — |
| 203.241.164.0/24 | AS1237 | — |
| 203.241.165.0/24 | AS1237 | — |
| 203.241.170.0/23 | AS1237 | — |
| 203.241.172.0/23 | AS1237 | — |
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.
AS1237 is an autonomous system number used to identify an independently operated network. The current page associates it with KREONET-AS-KR KISTI 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 AS1237. 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 AS1237, 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.