asn.dev

Observed topology

AS53813 ZSCALER-INC

Business ARIN

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

Transit

Upstream networks

All 28

Networks observed carrying traffic for AS53813: 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
AS9498BHARTI Airtel Ltd.MobileIPv4 IPv65,133
AS2914NTT America, Inc.TransitIPv4 IPv63,479
AS4637Telstra GlobalUnclassifiedIPv4 IPv63,220
AS4826Vocus Connect International BackboneUnclassifiedIPv4 IPv62,085
AS6939Hurricane Electric LLCTransitIPv4 IPv61,760
AS1299Arelion Sweden ABTransitIPv4 IPv61,722
AS55836Reliance Jio Infocomm LimitedMobileIPv4 IPv61,568
AS3356Level 3 Parent, LLCTransitIPv4 IPv6939
AS55410Vodafone Idea LtdMobileIPv4 IPv6677
AS9583Sify LimitedUnclassifiedIPv4 IPv6479

All 28 upstreams →

Transit

Downstream networks

inferred

Networks for which AS53813 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 28

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

ASNetworkTypeFamiliesPaths seen
AS9498BHARTI Airtel Ltd.MobileIPv4 IPv65,133
AS2914NTT America, Inc.TransitIPv4 IPv63,479
AS4637Telstra GlobalUnclassifiedIPv4 IPv63,220
AS4826Vocus Connect International BackboneUnclassifiedIPv4 IPv62,085
AS6939Hurricane Electric LLCTransitIPv4 IPv61,760
AS1299Arelion Sweden ABTransitIPv4 IPv61,722
AS55836Reliance Jio Infocomm LimitedMobileIPv4 IPv61,568
AS3356Level 3 Parent, LLCTransitIPv4 IPv6939
AS55410Vodafone Idea LtdMobileIPv4 IPv6677
AS9583Sify LimitedUnclassifiedIPv4 IPv6479

All 28 adjacent →

Provenance

Where this comes from

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