asn.dev

Observed topology

AS396842 RURALNET

Unclassified ARIN

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS396842: 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 IPv6167

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS400469CLAVERACK COMMUNICATIONS LLCUnclassifiedIPv4 IPv61,257
AS397427Bradford Broadband, LLCUnclassifiedIPv4 IPv6514
AS20364Firefly Network LLCUnclassifiedIPv4 IPv6162
AS395821Penn Wisp, LLCUnclassifiedIPv4114
AS402816BackRoadUnclassifiedIPv465

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4 IPv61,961
AS400469CLAVERACK COMMUNICATIONS LLCUnclassifiedIPv4 IPv61,257
AS397427Bradford Broadband, LLCUnclassifiedIPv4 IPv6514
AS26801Zito Media, L.P.UnclassifiedIPv4 IPv6318
AS20364Firefly Network LLCUnclassifiedIPv4 IPv6162
AS395821Penn Wisp, LLCUnclassifiedIPv4114
AS402816BackRoadUnclassifiedIPv465

Provenance

Where this comes from

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