asn.dev

Observed topology

AS22616 ZSCALER-SJC1

Business ARIN

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

Transit

Upstream networks

All 28

Networks observed carrying traffic for AS22616: 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
AS6461Zayo BandwidthTransitIPv4 IPv68,475
AS1299Arelion Sweden ABTransitIPv4 IPv67,610
AS3356Level 3 Parent, LLCTransitIPv4 IPv67,564
AS3257GTT Communications Inc.TransitIPv4 IPv64,198
AS6939Hurricane Electric LLCTransitIPv4 IPv64,068
AS32098Transtelco IncUnclassifiedIPv4 IPv6585
AS7195EDGEUNO S.A.SUnclassifiedIPv4 IPv6563
AS24482SG.GSHostingIPv4 IPv6418
AS293ESnetUnclassifiedIPv4346
AS6762TELECOM ITALIA SPARKLE S.p.A.TransitIPv4 IPv6317

All 28 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS62907ZSCALER, INC.BusinessIPv44

Adjacency

Adjacent networks

All 29

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

ASNetworkTypeFamiliesPaths seen
AS6461Zayo BandwidthTransitIPv4 IPv68,475
AS1299Arelion Sweden ABTransitIPv4 IPv67,610
AS3356Level 3 Parent, LLCTransitIPv4 IPv67,564
AS3257GTT Communications Inc.TransitIPv4 IPv64,202
AS6939Hurricane Electric LLCTransitIPv4 IPv64,068
AS32098Transtelco IncUnclassifiedIPv4 IPv6585
AS7195EDGEUNO S.A.SUnclassifiedIPv4 IPv6563
AS24482SG.GSHostingIPv4 IPv6418
AS293ESnetUnclassifiedIPv4346
AS6762TELECOM ITALIA SPARKLE S.p.A.TransitIPv4 IPv6317

All 29 adjacent →

Provenance

Where this comes from

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