Country
—
ASN LANDING PAGE
WISCNET1-AS - WiscNet
Last updated · Apr 4, 2026
Country
—
Total prefixes
39
IPv4 prefixes
37
IPv6 prefixes
2
WISCNET1-AS - WiscNet currently shows 39 prefixes and 55 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.
WISCNET1-AS - WiscNet 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.
AS19782
AS19782
—
AS3128
AS3128
—
AS47015
AS47015
—
AS3676
AS3676
—
AS11500
AS11500
—
AS25979
AS25979
—
AS53355
AS53355
—
AS33503
AS33503
—
AS22971
AS22971
—
AS395963
AS395963
—
AS394316
AS394316
—
AS36723
AS36723
—
AS401492
AS401492
—
AS22137
AS22137
—
AS40347
AS40347
—
AS64243
AS64243
—
AS393257
AS393257
—
AS394673
AS394673
—
AS14192
AS14192
—
AS22066
AS22066
—
AS400632
AS400632
—
AS2041
AS2041
—
AS53599
AS53599
—
AS57
AS57
—
AS103
AS103
—
AS23301
AS23301
—
AS3136
AS3136
—
AS1736
AS1736
—
AS396939
AS396939
—
AS55133
AS55133
—
AS26415
AS26415
—
AS40387
AS40387
—
AS7386
AS7386
—
AS46103
AS46103
—
| Prefix | Name | Country |
|---|---|---|
| 140.104.0.0/16 | AS2381 | — |
| 140.189.0.0/16 | AS2381 | — |
| 143.109.192.0/19 | AS2381 | — |
| 143.109.64.0/19 | AS2381 | — |
| 144.89.0.0/18 | AS2381 | — |
| 148.59.44.0/24 | AS2381 | — |
| 160.32.0.0/22 | AS2381 | — |
| 165.128.0.0/16 | AS2381 | — |
| 170.125.0.0/16 | AS2381 | — |
| 170.125.238.0/23 | AS2381 | — |
| 192.156.230.0/24 | AS2381 | — |
| 192.206.48.0/24 | AS2381 | — |
| 198.150.0.0/16 | AS2381 | — |
| 199.197.64.0/18 | AS2381 | — |
| 199.233.142.0/24 | AS2381 | — |
| 199.233.44.0/23 | AS2381 | — |
| 199.233.44.0/24 | AS2381 | — |
| 199.233.45.0/24 | AS2381 | — |
| 199.233.84.0/24 | AS2381 | — |
| 199.233.86.0/24 | AS2381 | — |
| 199.242.176.0/24 | AS2381 | — |
| 199.248.186.0/24 | AS2381 | — |
| 2001:4e0::/32 | AS2381 | — |
| 204.128.233.0/24 | AS2381 | — |
| 204.128.234.0/24 | AS2381 | — |
| 204.128.235.0/24 | AS2381 | — |
| 204.128.236.0/24 | AS2381 | — |
| 204.128.237.0/24 | AS2381 | — |
| 204.128.238.0/24 | AS2381 | — |
| 204.128.240.0/24 | AS2381 | — |
| 204.128.241.0/24 | AS2381 | — |
| 204.128.242.0/24 | AS2381 | — |
| 204.145.232.0/24 | AS2381 | — |
| 205.213.0.0/16 | AS2381 | — |
| 208.85.28.0/22 | AS2381 | — |
| 216.56.0.0/16 | AS2381 | — |
| 216.56.252.0/23 | AS2381 | — |
| 2620:11f:f000::/40 | AS2381 | — |
| 64.189.15.0/24 | AS2381 | — |
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.
AS2381 is an autonomous system number used to identify an independently operated network. The current page associates it with WISCNET1-AS - WiscNet 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 AS2381. 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 AS2381, 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.