asn.dev

Observed topology

AS402062 AUTOMATION-EXCHANGE - AUTOMATION EXCHANGE INFRASTRUCTURE LLC

Unclassified ARIN

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS402062: 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
AS14016Capcon NetworksUnclassifiedIPv4 IPv6246
AS174Cogent Communications, LLCTransitIPv4 IPv6180
AS6939Hurricane Electric LLCTransitIPv4 IPv626
AS20205Amplex Electric, Inc.ResidentialIPv41

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS400164Ripple Fiber Inc.ResidentialIPv4 IPv61,372
AS31942HyperFiberResidentialIPv4 IPv6600
AS402197Residence FiberUnclassifiedIPv4 IPv6548
AS402739SwellUnclassifiedIPv4 IPv6219
AS401429Prime One Net LLCUnclassifiedIPv4 IPv6213
AS7064West Boylston Municipal Light PlantUnclassifiedIPv460

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS14016Capcon NetworksUnclassifiedIPv4 IPv61,955
AS400164Ripple Fiber Inc.ResidentialIPv4 IPv61,372
AS174Cogent Communications, LLCTransitIPv4 IPv61,174
AS31942HyperFiberResidentialIPv4 IPv6600
AS402197Residence FiberUnclassifiedIPv4 IPv6548
AS6939Hurricane Electric LLCTransitIPv4 IPv6329
AS402739SwellUnclassifiedIPv4 IPv6219
AS401429Prime One Net LLCUnclassifiedIPv4 IPv6213
AS7064West Boylston Municipal Light PlantUnclassifiedIPv460
AS20205Amplex Electric, Inc.ResidentialIPv47

Provenance

Where this comes from

Derived from routing tables collected at 2026-11-12 18:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 74.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.