Observed topology

AS54240 SN-2006

Unclassified ARIN

Upstreams 2 carry this network

Downstreams 4 this network carries

Adjacent (IPv4) 7

Adjacent (IPv6) 0

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS54240: 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
AS3356	Level 3 Parent, LLC	Transit	IPv4	455
AS174	Cogent Communications, LLC	Transit	IPv4	428

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS10563	Rochelle Municipal Utilities	Residential	IPv4	174
AS394057	Batavia Public School District 101	Unclassified	IPv4	50
AS11417	Northern Illinois University	Education	IPv4	15
AS10730	Syndeo Networks, Inc	Unclassified	IPv4	12

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS174	Cogent Communications, LLC	Transit	IPv4	662
AS3356	Level 3 Parent, LLC	Transit	IPv4	491
AS10563	Rochelle Municipal Utilities	Residential	IPv4	174
AS394057	Batavia Public School District 101	Unclassified	IPv4	50
AS11417	Northern Illinois University	Education	IPv4	17
AS16609	The Aero Group, Inc.	Unclassified	IPv4	17
AS10730	Syndeo Networks, Inc	Unclassified	IPv4	12

Provenance

Where this comes from

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