asn.dev

Observed topology

AS40528 ICANN-LAX

Unclassified ARIN

Upstreams 2 carry this network
Downstreams 6 this network carries
Adjacent (IPv4) 9
Adjacent (IPv6) 4
Upstream graph Who carries AS40528, and who carries them, drawn as a map up to the transit-free core. 1 exchange Where AS40528 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS40528: 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
AS2914NTT America, Inc.TransitIPv4 IPv6182
AS3257GTT Communications Inc.TransitIPv4 IPv6178

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS26710ICANNUnclassifiedIPv4 IPv6118
AS26711ICANNUnclassifiedIPv4 IPv692
AS52304NIC ChileUnclassifiedIPv47
AS25192CZ.NIC, z.s.p.o.UnclassifiedIPv44
AS10906Nucleo de Inf. e Coord. do Ponto BR - NIC.BRUnclassifiedIPv43
AS48053Foundation of Research and Technology HellasUnclassifiedIPv41

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS2914NTT America, Inc.TransitIPv4 IPv6343
AS3257GTT Communications Inc.TransitIPv4 IPv6250
AS26710ICANNUnclassifiedIPv4 IPv6118
AS26711ICANNUnclassifiedIPv4 IPv692
AS28510Network Information Center MexicoUnclassifiedIPv48
AS52304NIC ChileUnclassifiedIPv47
AS25192CZ.NIC, z.s.p.o.UnclassifiedIPv44
AS10906Nucleo de Inf. e Coord. do Ponto BR - NIC.BRUnclassifiedIPv43
AS48053Foundation of Research and Technology HellasUnclassifiedIPv41

Provenance

Where this comes from

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