Observed topology

AS3851 NSHE-NEVADANET

Education ARIN

Upstreams 5 carry this network

Downstreams 2 this network carries

Adjacent (IPv4) 6

Adjacent (IPv6) 6

Upstream graph Who carries AS3851, and who carries them, drawn as a map up to the transit-free core. 0 exchanges Where AS3851 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS3851: 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.

AS	Network	Type	Families	Paths seen
AS6939	Hurricane Electric LLC	Transit	IPv4 IPv6	244
AS6461	Zayo Bandwidth	Transit	IPv4 IPv6	92
AS174	Cogent Communications, LLC	Transit	IPv4 IPv6	34
AS11537	Internet2	Unclassified	IPv4 IPv6	26
AS11164	Internet2	Education	IPv4 IPv6	15

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS15304	Washoe County	Unclassified	IPv4	51
AS395468	University of Nevada, Las Vegas	Unclassified	IPv6	37

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS6939	Hurricane Electric LLC	Transit	IPv4 IPv6	304
AS6461	Zayo Bandwidth	Transit	IPv4 IPv6	107
AS15304	Washoe County	Unclassified	IPv4	51
AS174	Cogent Communications, LLC	Transit	IPv4 IPv6	40
AS395468	University of Nevada, Las Vegas	Unclassified	IPv6	37
AS11537	Internet2	Unclassified	IPv4 IPv6	30
AS11164	Internet2	Education	IPv4 IPv6	18

Provenance

Where this comes from

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