asn.dev

Observed topology

AS30012 ASN-UNIVERSAL-MUSIC-GROUP-INC

Unclassified ARIN

Upstreams 34 carry this network
Downstreams 1 this network carries
Adjacent (IPv4) 35
Adjacent (IPv6) 0
Upstream graph Who carries AS30012, and who carries them, drawn as a map up to the transit-free core. 0 exchanges Where AS30012 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

All 34

Networks observed carrying traffic for AS30012: the AS immediately before it in a routing path. Ranked by how many paths showed the relationship, which reflects how widely it is used, not how much traffic crosses it.

ASNetworkTypeFamiliesPaths seen
AS8220COLT Technology Services Group LimitedHostingIPv4931
AS6461Zayo BandwidthTransitIPv4269
AS46887Crown Castle Fiber LLCUnclassifiedIPv4257
AS3356Level 3 Parent, LLCTransitIPv4210
AS20001Charter Communications IncResidentialIPv4138
AS196773VIAPASS SASUnclassifiedIPv484
AS577Bell CanadaMobileIPv480
AS36866Jamii Telecommunications LimitedUnclassifiedIPv461
AS50261ACE Telecom KftUnclassifiedIPv460
AS5617Orange Polska Spolka AkcyjnaMobileIPv459

Transit

Downstream networks

inferred

Networks for which AS30012 was observed as the last hop before the origin, meaning it appears to provide them transit.

ASNetworkTypeFamiliesPaths seen
AS4230120000AS4230120000UnclassifiedIPv41

Adjacency

Adjacent networks

All 35

Every AS seen directly next to AS30012 in a routing path, in either direction.

ASNetworkTypeFamiliesPaths seen
AS8220COLT Technology Services Group LimitedHostingIPv4931
AS6461Zayo BandwidthTransitIPv4270
AS46887Crown Castle Fiber LLCUnclassifiedIPv4257
AS3356Level 3 Parent, LLCTransitIPv4210
AS20001Charter Communications IncResidentialIPv4138
AS196773VIAPASS SASUnclassifiedIPv484
AS577Bell CanadaMobileIPv480
AS36866Jamii Telecommunications LimitedUnclassifiedIPv461
AS50261ACE Telecom KftUnclassifiedIPv460
AS5617Orange Polska Spolka AkcyjnaMobileIPv459

Provenance

Where this comes from

Derived from routing tables collected at 2026-10-20 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.16M route entries. These are observations from those vantage points, not a complete or authoritative view of the internet.

Inferred from path position, not from any declaration by either party. A network appearing here is carrying these routes; whether that is a paid transit arrangement, a backup, or something else is not something routing data can tell you. Adjacency is not the same as peering. Being next to each other in a path covers paid transit, settlement-free peering and customer connections alike, and routing data cannot distinguish them. Treat this as "these networks exchange routes", nothing more specific.

Cross-check against RIPEstat or BGP.tools, which observe from a different and larger set of vantage points.