asn.dev

Observed topology

AS13524 ARROW-ELECTRONICS - Arrow Electronics

Unclassified APNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS13524: 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
AS3356Level 3 Parent, LLCTransitIPv4467
AS3257GTT Communications Inc.TransitIPv4125
AS1299Arelion Sweden ABTransitIPv489
AS9498BHARTI Airtel Ltd.MobileIPv460
AS33652Comcast Cable Communications, LLCUnclassifiedIPv450
AS15830Equinix (EMEA) Acquisition Enterprises B.V.HostingIPv432
AS7018AT&T Enterprises, LLCResidentialIPv428
AS209CenturyLink Communications, LLCResidentialIPv426
AS46887Crown Castle Fiber LLCUnclassifiedIPv416
AS22773Cox Communications Inc.ResidentialIPv415

Transit

Downstream networks

inferred

Networks for which AS13524 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

observed

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

ASNetworkTypeFamiliesPaths seen
AS3356Level 3 Parent, LLCTransitIPv4467
AS3257GTT Communications Inc.TransitIPv4125
AS1299Arelion Sweden ABTransitIPv489
AS9498BHARTI Airtel Ltd.MobileIPv460
AS33652Comcast Cable Communications, LLCUnclassifiedIPv450
AS15830Equinix (EMEA) Acquisition Enterprises B.V.HostingIPv432
AS7018AT&T Enterprises, LLCResidentialIPv428
AS209CenturyLink Communications, LLCResidentialIPv426
AS46887Crown Castle Fiber LLCUnclassifiedIPv416
AS22773Cox Communications Inc.ResidentialIPv415

Provenance

Where this comes from

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