Country
—
ASN LANDING PAGE
GOOGLE-2 - Google LLC
Last updated · Apr 4, 2026
Country
—
Total prefixes
138
IPv4 prefixes
65
IPv6 prefixes
73
GOOGLE-2 - Google LLC currently shows 138 prefixes and 5 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.
GOOGLE-2 - Google LLC 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.
Detailed data for this ASN is not available right now.
| Prefix | Name | Country |
|---|---|---|
| 104.134.129.0/24 | AS395973 | — |
| 104.134.131.0/24 | AS395973 | — |
| 104.134.137.0/24 | AS395973 | — |
| 104.134.138.0/24 | AS395973 | — |
| 104.134.139.0/24 | AS395973 | — |
| 104.134.140.0/24 | AS395973 | — |
| 104.134.146.0/24 | AS395973 | — |
| 104.134.147.0/24 | AS395973 | — |
| 104.134.150.0/24 | AS395973 | — |
| 104.134.152.0/24 | AS395973 | — |
| 104.134.153.0/24 | AS395973 | — |
| 104.134.154.0/24 | AS395973 | — |
| 104.134.156.0/24 | AS395973 | — |
| 104.134.157.0/24 | AS395973 | — |
| 104.134.158.0/24 | AS395973 | — |
| 104.134.160.0/23 | AS395973 | — |
| 104.134.162.0/24 | AS395973 | — |
| 104.134.163.0/24 | AS395973 | — |
| 104.134.164.0/24 | AS395973 | — |
| 104.134.167.0/24 | AS395973 | — |
| 104.134.168.0/24 | AS395973 | — |
| 104.134.169.0/24 | AS395973 | — |
| 104.134.170.0/24 | AS395973 | — |
| 104.134.172.0/24 | AS395973 | — |
| 104.134.176.0/24 | AS395973 | — |
| 104.134.177.0/24 | AS395973 | — |
| 104.134.179.0/24 | AS395973 | — |
| 104.134.180.0/24 | AS395973 | — |
| 104.134.182.0/24 | AS395973 | — |
| 104.134.185.0/24 | AS395973 | — |
| 104.134.188.0/24 | AS395973 | — |
| 104.134.189.0/24 | AS395973 | — |
| 104.134.192.0/24 | AS395973 | — |
| 104.134.195.0/24 | AS395973 | — |
| 104.134.196.0/24 | AS395973 | — |
| 104.134.200.0/24 | AS395973 | — |
| 104.134.203.0/24 | AS395973 | — |
| 104.134.206.0/24 | AS395973 | — |
| 104.134.207.0/24 | AS395973 | — |
| 104.134.209.0/24 | AS395973 | — |
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.
Useful for comparing Google Public DNS primary and secondary nodes inside the same ASN footprint.
Useful for deciding whether this ASN behaves more like Google Cloud, Google Public DNS, or another Google-owned network.
Useful for separating Google Public DNS, Google Cloud, and other Google-owned network roles.
Useful for comparing Google Public DNS addresses against other public-resolver networks.
Useful for comparing Google DNS against broader public-resolver patterns.
Useful for comparing Google DNS with local ISP or carrier DNS behavior.
AS395973 is an autonomous system number used to identify an independently operated network. The current page associates it with GOOGLE-2 - Google LLC 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 AS395973. 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 AS395973, then continue into cloud, WHOIS, or routing topic pages to understand the network in a broader context.
Use ASN, WHOIS, prefixes, and service context to decide whether an IP looks more like Google Cloud, Google Public DNS, or another Google-owned network.
Separate Google Public DNS addresses like 8.8.8.8 from Google Cloud and other Google-owned infrastructure roles.
Compare 8.8.8.8 and 8.8.4.4 across ASN ownership, prefixes, Anycast context, and resolver role to understand Google's primary and secondary public DNS nodes.
Compare Google Public DNS with other public-resolver networks to understand what kind of DNS service 8.8.8.8 represents across ASN ownership, Anycast context, deployment, and resolver role.