asn.dev

Observed topology

AS18474 AENEAS

Unclassified ARIN Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS18474: 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
AS6939Hurricane Electric LLCTransitIPv4 IPv6619
AS174Cogent Communications, LLCTransitIPv4 IPv6392
AS3257GTT Communications Inc.TransitIPv4 IPv647

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS395712Milan Public Utilities AuthorityUnclassifiedIPv4 IPv6290
AS32852Lexington Electric SystemUnclassifiedIPv4 IPv6235
AS398765TEPA Connect LLCUnclassifiedIPv4 IPv6100

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4 IPv61,102
AS174Cogent Communications, LLCTransitIPv4 IPv6485
AS395712Milan Public Utilities AuthorityUnclassifiedIPv4 IPv6290
AS32852Lexington Electric SystemUnclassifiedIPv4 IPv6235
AS398765TEPA Connect LLCUnclassifiedIPv4 IPv6100
AS3257GTT Communications Inc.TransitIPv4 IPv696

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.