Observed topology

AS40702 CLEARWAVE-COMMUNICATIONS

Unclassified ARIN

Upstreams 2 carry this network

Downstreams 7 this network carries

Adjacent (IPv4) 9

Adjacent (IPv6) 0

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS40702: 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
AS53610	Metro Communications Company, Inc.	Unclassified	IPv4	3,351
AS3257	GTT Communications Inc.	Transit	IPv4	890

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS40755	ProTek Communications, LLC	Unclassified	IPv4	223
AS925	SiFibe, LLC	Unclassified	IPv4	58
AS22668	Sparta Community Hospital	Unclassified	IPv4	34
AS394598	CROSSLINK LONG DISTANCE, COMPANY	Unclassified	IPv4	32
AS54860	Southern Illinois Hospital Services	Unclassified	IPv4	8
AS15119	Southern Illinois University Carbondale	Unclassified	IPv4	2
AS400656	Metro Service Center	Unclassified	IPv4	2

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS53610	Metro Communications Company, Inc.	Unclassified	IPv4	3,351
AS3257	GTT Communications Inc.	Transit	IPv4	1,249
AS40755	ProTek Communications, LLC	Unclassified	IPv4	223
AS925	SiFibe, LLC	Unclassified	IPv4	58
AS22668	Sparta Community Hospital	Unclassified	IPv4	34
AS394598	CROSSLINK LONG DISTANCE, COMPANY	Unclassified	IPv4	32
AS54860	Southern Illinois Hospital Services	Unclassified	IPv4	8
AS15119	Southern Illinois University Carbondale	Unclassified	IPv4	2
AS400656	Metro Service Center	Unclassified	IPv4	2

Provenance

Where this comes from

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