asn.dev

Observed topology

AS53766 VMWARE-SASE

Unclassified ARIN

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

Transit

Upstream networks

All 47

Networks observed carrying traffic for AS53766: 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
AS1299Arelion Sweden ABTransitIPv4 IPv6851
AS3257GTT Communications Inc.TransitIPv4 IPv6536
AS6939Hurricane Electric LLCTransitIPv4 IPv6513
AS174Cogent Communications, LLCTransitIPv4 IPv6192
AS3491PCCW Global (HK) Ltd.TransitIPv4 IPv6111
AS4637Telstra GlobalUnclassifiedIPv4 IPv6109
AS8220COLT Technology Services Group LimitedHostingIPv4 IPv688
AS6461Zayo BandwidthTransitIPv4 IPv672
AS7473Singapore Telecommunications LtdUnclassifiedIPv4 IPv663
AS55064Arista Networks, Inc.UnclassifiedIPv459

Transit

Downstream networks

inferred

Networks for which AS53766 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 47

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

ASNetworkTypeFamiliesPaths seen
AS1299Arelion Sweden ABTransitIPv4 IPv6851
AS3257GTT Communications Inc.TransitIPv4 IPv6536
AS6939Hurricane Electric LLCTransitIPv4 IPv6513
AS174Cogent Communications, LLCTransitIPv4 IPv6192
AS3491PCCW Global (HK) Ltd.TransitIPv4 IPv6111
AS4637Telstra GlobalUnclassifiedIPv4 IPv6109
AS8220COLT Technology Services Group LimitedHostingIPv4 IPv688
AS6461Zayo BandwidthTransitIPv4 IPv672
AS7473Singapore Telecommunications LtdUnclassifiedIPv4 IPv663
AS55064Arista Networks, Inc.UnclassifiedIPv459

Provenance

Where this comes from

Derived from routing tables collected at 2026-10-19 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.