Country
—
ASN LANDING PAGE
MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation
Last updated · Apr 4, 2026
Country
—
Total prefixes
764
IPv4 prefixes
764
IPv6 prefixes
0
MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation currently shows 764 prefixes and 7 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.
MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation 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 |
|---|---|---|
| 13.104.80.0/23 | AS8069 | — |
| 13.104.82.0/24 | AS8069 | — |
| 145.190.0.0/23 | AS8069 | — |
| 145.190.133.0/24 | AS8069 | — |
| 145.190.16.0/21 | AS8069 | — |
| 145.190.2.0/24 | AS8069 | — |
| 145.190.24.0/21 | AS8069 | — |
| 145.190.3.0/24 | AS8069 | — |
| 145.190.32.0/22 | AS8069 | — |
| 145.190.36.0/24 | AS8069 | — |
| 145.190.37.0/24 | AS8069 | — |
| 145.190.38.0/23 | AS8069 | — |
| 145.190.4.0/23 | AS8069 | — |
| 145.190.40.0/23 | AS8069 | — |
| 145.190.42.0/24 | AS8069 | — |
| 145.190.43.0/24 | AS8069 | — |
| 145.190.44.0/22 | AS8069 | — |
| 145.190.48.0/22 | AS8069 | — |
| 145.190.52.0/23 | AS8069 | — |
| 145.190.54.0/24 | AS8069 | — |
| 145.190.55.0/24 | AS8069 | — |
| 145.190.56.0/23 | AS8069 | — |
| 145.190.58.0/24 | AS8069 | — |
| 145.190.59.0/24 | AS8069 | — |
| 145.190.6.0/24 | AS8069 | — |
| 145.190.61.0/24 | AS8069 | — |
| 145.190.62.0/24 | AS8069 | — |
| 145.190.66.0/24 | AS8069 | — |
| 145.190.67.0/24 | AS8069 | — |
| 145.190.68.0/24 | AS8069 | — |
| 145.190.69.0/24 | AS8069 | — |
| 145.190.7.0/24 | AS8069 | — |
| 145.190.8.0/21 | AS8069 | — |
| 20.153.0.0/24 | AS8069 | — |
| 20.153.1.0/24 | AS8069 | — |
| 20.153.100.0/24 | AS8069 | — |
| 20.153.103.0/24 | AS8069 | — |
| 20.153.105.0/24 | AS8069 | — |
| 20.153.106.0/24 | AS8069 | — |
| 20.153.107.0/24 | AS8069 | — |
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 deciding whether this ASN behaves more like Azure enterprise cloud or another Microsoft network layer.
Continue from this ASN into cloud-provider, hosting, and VPS ownership analysis.
Useful for deciding whether this ASN looks more like cloud infrastructure or traditional website hosting.
Useful for placing this ASN into datacenter-versus-residential attribution analysis.
Continue from this ASN into the differences between WHOIS ownership and ASN ownership.
Continue from this ASN into route troubleshooting and network analysis.
AS8069 is an autonomous system number used to identify an independently operated network. The current page associates it with MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation 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 AS8069. 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 AS8069, then continue into cloud, WHOIS, or routing topic pages to understand the network in a broader context.
Use ASN, WHOIS, prefixes, and enterprise-cloud context to decide whether an IP looks more like Azure or Microsoft infrastructure.
Determine whether an IP belongs to AWS, Google Cloud, Azure, or another cloud network by combining ASN, WHOIS, prefixes, and organization data.
Compare large cloud and edge networks such as Google, Cloudflare, Microsoft, and Amazon through their ASN landing pages.
Separate cloud-server IPs, traditional web-hosting IPs, shared-hosting IPs, and website-hosting networks through ASN, WHOIS, organization, and deployment signals.