Country
—
ASN LANDING PAGE
GREAT-LAKES-COMNET - Great Lakes Comnet
Last updated · Apr 4, 2026
Country
—
Total prefixes
26
IPv4 prefixes
19
IPv6 prefixes
7
GREAT-LAKES-COMNET - Great Lakes Comnet currently shows 26 prefixes and 53 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.
GREAT-LAKES-COMNET - Great Lakes Comnet 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.
AS46293
AS46293
—
AS36443
AS36443
—
AS22379
AS22379
—
AS19009
AS19009
—
AS46970
AS46970
—
AS54119
AS54119
—
AS36338
AS36338
—
AS26216
AS26216
—
AS396470
AS396470
—
AS398092
AS398092
—
AS29924
AS29924
—
AS32456
AS32456
—
AS398401
AS398401
—
AS46143
AS46143
—
AS394664
AS394664
—
AS36578
AS36578
—
AS14599
AS14599
—
AS398856
AS398856
—
AS22861
AS22861
—
AS396224
AS396224
—
AS17210
AS17210
—
AS53352
AS53352
—
AS46825
AS46825
—
AS21554
AS21554
—
AS393471
AS393471
—
AS14374
AS14374
—
AS393983
AS393983
—
AS40813
AS40813
—
AS14893
AS14893
—
AS19967
AS19967
—
AS395553
AS395553
—
AS395175
AS395175
—
AS399593
AS399593
—
AS397300
AS397300
—
AS46252
AS46252
—
AS14711
AS14711
—
AS14175
AS14175
—
AS22911
AS22911
—
AS35979
AS35979
—
AS54840
AS54840
—
| Prefix | Name | Country |
|---|---|---|
| 12.27.195.0/24 | AS30517 | — |
| 172.87.32.0/22 | AS30517 | — |
| 209.165.240.0/23 | AS30517 | — |
| 209.165.241.0/24 | AS30517 | — |
| 209.165.244.0/22 | AS30517 | — |
| 209.165.245.0/24 | AS30517 | — |
| 209.165.247.0/24 | AS30517 | — |
| 209.165.248.0/21 | AS30517 | — |
| 209.165.248.0/24 | AS30517 | — |
| 216.176.0.0/21 | AS30517 | — |
| 216.176.16.0/20 | AS30517 | — |
| 2604:fe00:1::/48 | AS30517 | — |
| 2604:fe00:2::/48 | AS30517 | — |
| 2604:fe00:4::/48 | AS30517 | — |
| 2604:fe00:5::/48 | AS30517 | — |
| 2604:fe00:7::/48 | AS30517 | — |
| 2604:fe00::/32 | AS30517 | — |
| 2606:9780::/32 | AS30517 | — |
| 35.128.0.0/18 | AS30517 | — |
| 35.128.19.0/24 | AS30517 | — |
| 35.128.58.0/24 | AS30517 | — |
| 35.128.60.0/24 | AS30517 | — |
| 64.85.144.0/20 | AS30517 | — |
| 64.85.160.0/21 | AS30517 | — |
| 72.35.40.0/21 | AS30517 | — |
| 72.35.48.0/20 | AS30517 | — |
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.
AS30517 is an autonomous system number used to identify an independently operated network. The current page associates it with GREAT-LAKES-COMNET - Great Lakes Comnet 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 AS30517. 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 AS30517, 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.