asn.dev

Observed topology

AS397097 IMA-MODERN-AS - Infrastructure Management Associates, Inc.

Unclassified ARIN

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS397097: 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 IPv699
AS19364Sebago Fiber & Wifi, LLCUnclassifiedIPv41

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS18467Axiom Technologies LLCResidentialIPv4 IPv61,221
AS400639Outer Reach Broadband LLCUnclassifiedIPv4191
AS399613Smestad Tech LLCUnclassifiedIPv4 IPv6134
AS401756Swanroe Internet Cooperative LLCUnclassifiedIPv4 IPv6100
AS402809GummipantzenUnclassifiedIPv4 IPv699

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4 IPv61,823
AS18467Axiom Technologies LLCResidentialIPv4 IPv61,221
AS400639Outer Reach Broadband LLCUnclassifiedIPv4191
AS399613Smestad Tech LLCUnclassifiedIPv4 IPv6134
AS401756Swanroe Internet Cooperative LLCUnclassifiedIPv4 IPv6100
AS402809GummipantzenUnclassifiedIPv4 IPv699
AS19364Sebago Fiber & Wifi, LLCUnclassifiedIPv4 IPv622

Provenance

Where this comes from

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