Country
—
ASN LANDING PAGE
ASN-UNIVERSAL-MUSIC-GROUP-INC - Universal Music Group
Last updated · Apr 4, 2026
Country
—
Total prefixes
49
IPv4 prefixes
49
IPv6 prefixes
0
ASN-UNIVERSAL-MUSIC-GROUP-INC - Universal Music Group currently shows 49 prefixes and 37 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.
ASN-UNIVERSAL-MUSIC-GROUP-INC - Universal Music Group 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.
AS8220
AS8220
—
AS6461
AS6461
—
AS46887
AS46887
—
AS20001
AS20001
—
AS196773
AS196773
—
AS3356
AS3356
—
AS45458
AS45458
—
AS400317
AS400317
—
AS577
AS577
—
AS4826
AS4826
—
AS3329
AS3329
—
AS3257
AS3257
—
AS36866
AS36866
—
AS55836
AS55836
—
AS5617
AS5617
—
AS52468
AS52468
—
AS50261
AS50261
—
AS9318
AS9318
—
AS5555
AS5555
—
AS21949
AS21949
—
AS12552
AS12552
—
AS1267
AS1267
—
AS12271
AS12271
—
AS35332
AS35332
—
AS1273
AS1273
—
AS8412
AS8412
—
AS2914
AS2914
—
AS15290
AS15290
—
AS4766
AS4766
—
AS11014
AS11014
—
AS11776
AS11776
—
AS28666
AS28666
—
AS7474
AS7474
—
AS17762
AS17762
—
AS286
AS286
—
| Prefix | Name | Country |
|---|---|---|
| 103.119.127.0/24 | AS30012 | — |
| 167.167.1.0/24 | AS30012 | — |
| 167.167.10.0/24 | AS30012 | — |
| 167.167.107.0/24 | AS30012 | — |
| 167.167.11.0/24 | AS30012 | — |
| 167.167.12.0/22 | AS30012 | — |
| 167.167.128.0/22 | AS30012 | — |
| 167.167.132.0/24 | AS30012 | — |
| 167.167.138.0/24 | AS30012 | — |
| 167.167.144.0/23 | AS30012 | — |
| 167.167.148.0/24 | AS30012 | — |
| 167.167.152.0/24 | AS30012 | — |
| 167.167.154.0/24 | AS30012 | — |
| 167.167.155.0/24 | AS30012 | — |
| 167.167.156.0/24 | AS30012 | — |
| 167.167.159.0/24 | AS30012 | — |
| 167.167.16.0/23 | AS30012 | — |
| 167.167.161.0/24 | AS30012 | — |
| 167.167.162.0/24 | AS30012 | — |
| 167.167.163.0/24 | AS30012 | — |
| 167.167.167.0/24 | AS30012 | — |
| 167.167.170.0/24 | AS30012 | — |
| 167.167.175.0/24 | AS30012 | — |
| 167.167.183.0/24 | AS30012 | — |
| 167.167.185.0/24 | AS30012 | — |
| 167.167.193.0/24 | AS30012 | — |
| 167.167.20.0/24 | AS30012 | — |
| 167.167.21.0/24 | AS30012 | — |
| 167.167.228.0/24 | AS30012 | — |
| 167.167.232.0/21 | AS30012 | — |
| 167.167.240.0/24 | AS30012 | — |
| 167.167.244.0/24 | AS30012 | — |
| 167.167.248.0/23 | AS30012 | — |
| 167.167.3.0/24 | AS30012 | — |
| 167.167.37.0/24 | AS30012 | — |
| 167.167.4.0/24 | AS30012 | — |
| 167.167.40.0/23 | AS30012 | — |
| 167.167.46.0/24 | AS30012 | — |
| 167.167.48.0/24 | AS30012 | — |
| 167.167.5.0/24 | AS30012 | — |
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.
AS30012 is an autonomous system number used to identify an independently operated network. The current page associates it with ASN-UNIVERSAL-MUSIC-GROUP-INC - Universal Music Group 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 AS30012. 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 AS30012, 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.