Observed topology

AS40749 CDELIGHTBAND

Unclassified ARIN

Upstreams 3 carry this network

Downstreams 4 this network carries

Adjacent (IPv4) 7

Adjacent (IPv6) 0

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS40749: 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	963
AS3356	Level 3 Parent, LLC	Transit	IPv4	241
AS14016	Capcon Networks	Unclassified	IPv4	12

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS396956	Meriwether Lewis Electric Cooperative	Unclassified	IPv4	229
AS395640	Austin Peay State University	Unclassified	IPv4	64
AS17313	THE CBE GROUP, INC	Unclassified	IPv4	5
AS13781	Hopkinsville Electric System	Unclassified	IPv4	2

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS11758	IRIS Networks	Unclassified	IPv4	1,257
AS3356	Level 3 Parent, LLC	Transit	IPv4	262
AS396956	Meriwether Lewis Electric Cooperative	Unclassified	IPv4	229
AS395640	Austin Peay State University	Unclassified	IPv4	64
AS14016	Capcon Networks	Unclassified	IPv4	17
AS13781	Hopkinsville Electric System	Unclassified	IPv4	14
AS17313	THE CBE GROUP, INC	Unclassified	IPv4	5

Provenance

Where this comes from

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