asn.dev

Observed topology

AS393238 IMONC

Residential ARIN

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS393238: 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 IPv61,131
AS174Cogent Communications, LLCTransitIPv4 IPv6241
AS24482SG.GSHostingIPv4 IPv622

Transit

Downstream networks

All 15

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

ASNetworkTypeFamiliesPaths seen
AS46552RSMUnclassifiedIPv4301
AS21896Alliant EnergyUnclassifiedIPv4204
AS393308City of Iowa CityUnclassifiedIPv4 IPv6135
AS27304Loras CollegeUnclassifiedIPv4130
AS22339University of DubuqueUnclassifiedIPv6108
AS397741City Of DubuqueUnclassifiedIPv470
AS23538Johnson County IowaUnclassifiedIPv465
AS397185Corda Credit UnionUnclassifiedIPv464
AS400530Dubuque Community SchoolsUnclassifiedIPv462
AS397051Medical Associates Clinic, P.C.UnclassifiedIPv450

All 15 downstreams →

Adjacency

Adjacent networks

All 18

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4 IPv63,196
AS14230ARK Data Centers LLCUnclassifiedIPv41,020
AS174Cogent Communications, LLCTransitIPv4 IPv6487
AS46552RSMUnclassifiedIPv4301
AS21896Alliant EnergyUnclassifiedIPv4204
AS393308City of Iowa CityUnclassifiedIPv4 IPv6135
AS27304Loras CollegeUnclassifiedIPv4130
AS22339University of DubuqueUnclassifiedIPv6108
AS397741City Of DubuqueUnclassifiedIPv470
AS23538Johnson County IowaUnclassifiedIPv465

All 18 adjacent →

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.