asn.dev

Observed topology

AS62044 ZSCALER-EMEA

Business RIPE

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

Transit

Upstream networks

All 65

Networks observed carrying traffic for AS62044: 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 IPv67,480
AS3356Level 3 Parent, LLCTransitIPv4 IPv66,932
AS6939Hurricane Electric LLCTransitIPv4 IPv63,885
AS3257GTT Communications Inc.TransitIPv4 IPv63,691
AS6461Zayo BandwidthTransitIPv4 IPv62,004
AS8966EMIRATES TELECOMMUNICATIONS GROUP COMPANY (ETISALAT GROUP) PJSCMobileIPv4 IPv6799
AS37100SEACOM LimitedUnclassifiedIPv4 IPv6726
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv6672
AS24482SG.GSHostingIPv4 IPv6481
AS4637Telstra GlobalUnclassifiedIPv4 IPv6475

Transit

Downstream networks

inferred

Networks for which AS62044 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 65

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

ASNetworkTypeFamiliesPaths seen
AS1299Arelion Sweden ABTransitIPv4 IPv67,480
AS3356Level 3 Parent, LLCTransitIPv4 IPv66,932
AS6939Hurricane Electric LLCTransitIPv4 IPv63,885
AS3257GTT Communications Inc.TransitIPv4 IPv63,691
AS6461Zayo BandwidthTransitIPv4 IPv62,004
AS8966EMIRATES TELECOMMUNICATIONS GROUP COMPANY (ETISALAT GROUP) PJSCMobileIPv4 IPv6799
AS37100SEACOM LimitedUnclassifiedIPv4 IPv6726
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv6672
AS24482SG.GSHostingIPv4 IPv6481
AS4637Telstra GlobalUnclassifiedIPv4 IPv6475

Provenance

Where this comes from

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