asn.dev

Observed topology

AS396216 -Reserved AS-

Unclassified ARIN

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS396216: 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 IPv6218
AS1299Arelion Sweden ABTransitIPv4 IPv645
AS34927iFog GmbHHostingIPv62

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS395582Grand River Mutual Telephone CorporationUnclassifiedIPv4 IPv65,494
AS33616Co-Mo Comm IncResidentialIPv4 IPv65,209
AS394778Northeast Missouri Rural Telephone Co.UnclassifiedIPv4 IPv62,613
AS395040Green Hills Telephone CorporationUnclassifiedIPv4752

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4 IPv611,259
AS395582Grand River Mutual Telephone CorporationUnclassifiedIPv4 IPv65,494
AS33616Co-Mo Comm IncResidentialIPv4 IPv65,247
AS1299Arelion Sweden ABTransitIPv4 IPv62,937
AS394778Northeast Missouri Rural Telephone Co.UnclassifiedIPv4 IPv62,613
AS395040Green Hills Telephone CorporationUnclassifiedIPv4770
AS54579Chariton Valley Telephone CorporationResidentialIPv4186
AS34927iFog GmbHHostingIPv4 IPv66
AS52025ParadoxNetworks LimitedUnclassifiedIPv41

Provenance

Where this comes from

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