asn.dev

Observed topology

AS393891 NUTRIEN

Unclassified ARIN Enterprise

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

Transit

Upstream networks

All 11

Networks observed carrying traffic for AS393891: 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 IPv6900
AS852TELUS Communications Inc.ResidentialIPv4 IPv660
AS174Cogent Communications, LLCTransitIPv4 IPv655
AS3356Level 3 Parent, LLCTransitIPv4 IPv649
AS7018AT&T Enterprises, LLCResidentialIPv4 IPv639
AS803Saskatchewan TelecommunicationsResidentialIPv4 IPv637
AS24482SG.GSHostingIPv4 IPv625
AS394256Tech Futures Interactive Inc.UnclassifiedIPv4 IPv625
AS3130RGnet OUUnclassifiedIPv410
AS37721Virtual Technologies & SolutionsResidentialIPv410

Transit

Downstream networks

inferred

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

No downstream observed. This network does not appear to carry transit for anyone.

Adjacency

Adjacent networks

All 11

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4 IPv6900
AS852TELUS Communications Inc.ResidentialIPv4 IPv660
AS174Cogent Communications, LLCTransitIPv4 IPv655
AS3356Level 3 Parent, LLCTransitIPv4 IPv649
AS7018AT&T Enterprises, LLCResidentialIPv4 IPv639
AS803Saskatchewan TelecommunicationsResidentialIPv4 IPv637
AS24482SG.GSHostingIPv4 IPv625
AS394256Tech Futures Interactive Inc.UnclassifiedIPv4 IPv625
AS3130RGnet OUUnclassifiedIPv410
AS37721Virtual Technologies & SolutionsResidentialIPv410

Provenance

Where this comes from

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