asn.dev

Observed topology

AS16717 CRAWKANINTERNET - Craw-Kan Telephone Cooperative Inc.

Unclassified ARIN Cable/DSL/ISP

Upstreams 4 carry this network
Downstreams 2 this network carries
Adjacent (IPv4) 6
Adjacent (IPv6) 3
Upstream graph Who carries AS16717, and who carries them, drawn as a map up to the transit-free core. 0 exchanges Where AS16717 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS16717: 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
AS55140Sho Me Technologies, LLCResidentialIPv4549
AS13329Kansas Fiber Network, LLCUnclassifiedIPv4 IPv6224
AS7018AT&T Enterprises, LLCResidentialIPv4 IPv6133
AS22773Cox Communications Inc.ResidentialIPv4 IPv66

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS396326Watco Companies, LLC.UnclassifiedIPv4109
AS19048PEERLESS PRODUCTS, INC.UnclassifiedIPv441

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS55140Sho Me Technologies, LLCResidentialIPv4601
AS13329Kansas Fiber Network, LLCUnclassifiedIPv4 IPv6311
AS7018AT&T Enterprises, LLCResidentialIPv4 IPv6142
AS396326Watco Companies, LLC.UnclassifiedIPv4109
AS19048PEERLESS PRODUCTS, INC.UnclassifiedIPv441
AS22773Cox Communications Inc.ResidentialIPv4 IPv68

Provenance

Where this comes from

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