Observed topology

AS3450 UTK

Education ARIN

Upstreams 3 carry this network

Downstreams 3 this network carries

Adjacent (IPv4) 5

Adjacent (IPv6) 2

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS3450: 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
AS11758	IRIS Networks	Unclassified	IPv4	290
AS10490	Georgia Institute of Technology	Education	IPv4	178
AS22909	Comcast Cable Communications, LLC	Unclassified	IPv4	22

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS46512	University of Tennessee Medical Center	Unclassified	IPv4	80
AS11686	Zayo Bandwidth	Education	IPv4	25
AS14209	University of Tennessee at Chattanooga	Unclassified	IPv6	2

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS11758	IRIS Networks	Unclassified	IPv4	355
AS10490	Georgia Institute of Technology	Education	IPv4 IPv6	220
AS46512	University of Tennessee Medical Center	Unclassified	IPv4	80
AS11686	Zayo Bandwidth	Education	IPv4	25
AS22909	Comcast Cable Communications, LLC	Unclassified	IPv4	22
AS14209	University of Tennessee at Chattanooga	Unclassified	IPv6	2

Provenance

Where this comes from

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