Observed topology

AS46749 STANFORD-INTERNET-ACCESS - Stanford University

Unclassified ARIN

Upstreams 2 carry this network

Downstreams 3 this network carries

Adjacent (IPv4) 6

Adjacent (IPv6) 3

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS46749: 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	59
AS2152	CENIC	Unclassified	IPv4	8

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS32	Stanford University	Unclassified	IPv4 IPv6	221
AS54531	LUCILE SALTER PACKARD CHILDREN'S HOSPITAL AT STANFORD	Unclassified	IPv4	66
AS3671	SLAC National Accelerator Laboratory	Unclassified	IPv4	2

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS6939	Hurricane Electric LLC	Transit	IPv4 IPv6	252
AS32	Stanford University	Unclassified	IPv4 IPv6	222
AS2152	CENIC	Unclassified	IPv4 IPv6	102
AS54531	LUCILE SALTER PACKARD CHILDREN'S HOSPITAL AT STANFORD	Unclassified	IPv4	66
AS3671	SLAC National Accelerator Laboratory	Unclassified	IPv4	3
AS46750	Stanford University	Unclassified	IPv4	2

Provenance

Where this comes from

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