asn.dev

Observed topology

AS30103 ZOOM-VIDEO-COMM-AS - Zoom Video Communications, Inc

Unclassified ARIN NSP

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

Transit

Upstream networks

All 53

Networks observed carrying traffic for AS30103: 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
AS13335Cloudflare, Inc.HostingIPv4 IPv610,583
AS1299Arelion Sweden ABTransitIPv4 IPv61,605
AS8151UNINETMobileIPv4 IPv61,518
AS174Cogent Communications, LLCTransitIPv4 IPv61,028
AS3356Level 3 Parent, LLCTransitIPv4 IPv6931
AS21859Zenlayer IncHostingIPv4 IPv6920
AS6939Hurricane Electric LLCTransitIPv4 IPv6821
AS39386Saudi Telecom Company JSCUnclassifiedIPv4 IPv6596
AS3491PCCW Global (HK) Ltd.TransitIPv4 IPv6499
AS7473Singapore Telecommunications LtdUnclassifiedIPv4 IPv6366

Transit

Downstream networks

inferred

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

No downstream observed. This network does not appear to carry transit for anyone.

Adjacency

Adjacent networks

All 53

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

ASNetworkTypeFamiliesPaths seen
AS13335Cloudflare, Inc.HostingIPv4 IPv610,583
AS1299Arelion Sweden ABTransitIPv4 IPv61,605
AS8151UNINETMobileIPv4 IPv61,518
AS174Cogent Communications, LLCTransitIPv4 IPv61,028
AS3356Level 3 Parent, LLCTransitIPv4 IPv6931
AS21859Zenlayer IncHostingIPv4 IPv6920
AS6939Hurricane Electric LLCTransitIPv4 IPv6821
AS39386Saudi Telecom Company JSCUnclassifiedIPv4 IPv6596
AS3491PCCW Global (HK) Ltd.TransitIPv4 IPv6499
AS7473Singapore Telecommunications LtdUnclassifiedIPv4 IPv6366

Provenance

Where this comes from

Derived from routing tables collected at 2026-11-09 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.03M 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.