asn.dev

Observed topology

AS40702 CLEARWAVE-COMMUNICATIONS - 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.

ASNetworkTypeFamiliesPaths seen
AS53610Metro Communications Company, Inc.UnclassifiedIPv44,439
AS3257GTT Communications Inc.TransitIPv4358

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS40755ProTek Communications, LLCUnclassifiedIPv4315
AS394598CROSSLINK LONG DISTANCE, COMPANYUnclassifiedIPv476
AS925SiFibe, LLCUnclassifiedIPv465
AS22668Sparta Community HospitalUnclassifiedIPv464
AS15119Southern Illinois University CarbondaleUnclassifiedIPv434
AS54860Southern Illinois Hospital ServicesUnclassifiedIPv48
AS400656Metro Service CenterUnclassifiedIPv41

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS53610Metro Communications Company, Inc.UnclassifiedIPv44,828
AS3257GTT Communications Inc.TransitIPv4532
AS40755ProTek Communications, LLCUnclassifiedIPv4315
AS394598CROSSLINK LONG DISTANCE, COMPANYUnclassifiedIPv476
AS925SiFibe, LLCUnclassifiedIPv465
AS22668Sparta Community HospitalUnclassifiedIPv464
AS15119Southern Illinois University CarbondaleUnclassifiedIPv434
AS54860Southern Illinois Hospital ServicesUnclassifiedIPv48
AS400656Metro Service CenterUnclassifiedIPv41

Provenance

Where this comes from

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