Observed topology

AS396450 Internet2

Unclassified ARIN

Upstreams 0 carry this network

Downstreams 7 this network carries

Adjacent (IPv4) 9

Adjacent (IPv6) 0

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

Transit

Upstream networks

inferred

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

No upstream observed. Typical for a tier-1 network that buys transit from nobody.

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS1798	State of Oregon	Unclassified	IPv4	118
AS3479	Board of Regents of the University System of Georgia	Education	IPv4	118
AS19782	Indiana University	Unclassified	IPv4	118
AS6200	University of Illinois Chicago	Education	IPv4	59
AS2152	CENIC	Unclassified	IPv4	55
AS103	Northwestern University	Unclassified	IPv4	5
AS1312	Virginia Polytechnic Institute and State Univ.	Unclassified	IPv4	1

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS198949	Radware Ltd	Unclassified	IPv4	639
AS2152	CENIC	Unclassified	IPv4	165
AS1798	State of Oregon	Unclassified	IPv4	118
AS3479	Board of Regents of the University System of Georgia	Education	IPv4	118
AS19782	Indiana University	Unclassified	IPv4	118
AS6200	University of Illinois Chicago	Education	IPv4	59
AS10490	Georgia Institute of Technology	Education	IPv4	55
AS103	Northwestern University	Unclassified	IPv4	5
AS1312	Virginia Polytechnic Institute and State Univ.	Unclassified	IPv4	1

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.